<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Quest on Remko's Blog</title><link>https://remkoweijnen.nl/blog/tags/quest/</link><description>Recent content in Quest on Remko's Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 08 Apr 2013 11:53:32 +0000</lastBuildDate><atom:link href="https://remkoweijnen.nl/blog/tags/quest/index.xml" rel="self" type="application/rss+xml"/><item><title>Decrypting Dell vWorkspace .pit files</title><link>https://remkoweijnen.nl/blog/2013/04/08/decrypting-dell-vworkspace-pit-files/</link><pubDate>Mon, 08 Apr 2013 11:53:32 +0000</pubDate><guid>https://remkoweijnen.nl/blog/2013/04/08/decrypting-dell-vworkspace-pit-files/</guid><description>&lt;p&gt;The Dell vWorkspace (previously Quest vWorkspace) Client can save a connection to a .pit file which is very similar to an .rdp file with one big difference: it is encrypted!&lt;/p&gt; &lt;p&gt;I am not sure why Dell/Quest have chosen to encrypt their files but a while ago I needed to know what was in a particular pit file so I could troubleshoot an issue.&lt;/p&gt; &lt;p&gt;I first created a test .pit file with the client (pntsc.exe version 7.6.305.791).&lt;/p&gt; &lt;p&gt;&lt;a class="glightbox thickbox" href="https://remkoweijnen.nl/blog/wp-content/uploads/2013/03/SNAGHTML6c0786d.webp" data-type="image" data-gallery="post-3171"&gt;&lt;img loading="lazy" decoding="async" style="display: inline" title="SNAGHTML6c0786d" alt="SNAGHTML6c0786d" src="https://remkoweijnen.nl/blog/wp-content/uploads/2013/03/SNAGHTML6c0786d_thumb.webp" width="200" height="240" /&gt;&lt;/a&gt;&lt;/p&gt;</description></item></channel></rss>