Video Screencast Help

PGP Netshare

Created: 28 Mar 2011 | 1 comment
We have been licensing PGP 9.6.3 (and 9.6.2) Netshare  on Windows XP PRO SP3 Machines for a number of years to access several file shares running on a Windows 2008 Server. All folders on these shares were encrypted using the PGP software and public keys from three users.   This installation has been working flawlessly, without any regard to  file types.  The source libraries and compiled modules for our SAS application include ~100,000 lines of code across hundreds of files. Virtually every style of Microsoft Office File is represented within the thousands of other files on these shares. PGP Netshare has handled day to day access to these file shares within virtually no problems since its installation.
This has changed, however, when we upgraded to a client workstation running Windows 7 Pro.  After establishing that this system was incompatible with PGP Netshare/Desktop ver 9.6.3, we upgraded directly to Version 10.1.1.  Unfortunately, we now have problems with decryption of bitmap files (BMP & JPG) and the behavior is inconsistent.  We have reloaded all key rings, but this problem remains.  A simple file open of 300k bitmap stored and encrypted on a file share using PGP Netshare is unsuccessful 10%-50% of the time using this machine.  On another machine running ver 9.6.3, the same exact file decrypts without incident.  We have also tried decrypting the file and re-encrypting using the Windows 7 machine. But the problem remains the same. Other types of files seem to work under 10.1.1 and Window with no problems.  The error message that we get is " Windows photo viewer can't open this picture because the file appears to be damaged, corrupted, or is too large".  

Comments 1 CommentJump to latest comment

UlrichW's picture


Do you have the ability to reproduce this problem in a way that you can share the pieces with us?

What I'd ideally like to see are the following:

- The key that's being used to encrypt the file

- The key that's being used to decrypt the file

- The unencrypted version of the file

- The encrypted version of the file (that can't be successfully decrypted)

Since this would require you to share keys with us, you would need to create brand-new keys to reproduce this issue.

A separate question on the occurence of this issue - I wasn't clear if this problem happens consistently on a given file or if it happens intermittently.

Also, what kind of server are these files stored on?


-- Ulrich