Not compatible with PGP 3-5-8??

38 views
Skip to first unread message

Murali V

unread,
Feb 7, 2013, 1:43:25 PM2/7/13
to didisof...@googlegroups.com
Hello,
I have a client that i send files to that are encrypted and decrypted using Didisoft. Here is the problem. I am able to decrypt files that the client send me. Thought he is not able to decrypt files that are sent by me which are encrypted using didisoft. He is using PGP 3.5.8. He gets a error that stats session key is bad. I have attached a snapshot of the error.
Is this a known issue? Kindly advice

Thanks

Murali


err.png

didisoft

unread,
Feb 7, 2013, 1:58:08 PM2/7/13
to didisof...@googlegroups.com
Hi Murali,

Is it possible for you to check for sure is the PGP software they use version 3.5.6 ?
(or can it be 6.5.8...) 

Kind Regards,
Peter Kalef

didisoft

unread,
Feb 7, 2013, 2:19:00 PM2/7/13
to didisof...@googlegroups.com
Hi Murali,

Can you also tell me do you set the integrity protection parameter to true (this is usually the last parameter of the EncryptFile method) or you are using an overloaded version without such parameter?

Cheers,
Peter Kalef

Murali V

unread,
Feb 7, 2013, 3:07:29 PM2/7/13
to didisof...@googlegroups.com
Peter,
Thanks for the reply. The PGP version is 6.5.8.  And For the encryption I use the IntegrityCheck Parameter to be true
This is my syntax (file,key,true,true)

Thanks

Murali

didisoft

unread,
Feb 7, 2013, 3:25:02 PM2/7/13
to didisof...@googlegroups.com
Hi Murali,

Can you try to send them an encrypted file with the integrity check parameter (the last one) set to false,
and tell me is there any difference.

Regards,
Peter Kalef

Murali V

unread,
Feb 7, 2013, 4:26:13 PM2/7/13
to didisof...@googlegroups.com
That did the trick. Can you tell me what exactly does it do for the integrity check?
Thanks though

Murali

PS: that was very quick from your side.

didisoft

unread,
Feb 8, 2013, 4:58:04 AM2/8/13
to didisof...@googlegroups.com
Hi Murali,

The message integrity check protection is a feature not supported by PGP 6.x and older
and this is why it failed to decipher it.

Kind Regards,
Peter
Reply all
Reply to author
Forward
0 new messages