PGP Encryption/Decryption

[Former Member]

Hello,

We have purchase AEADAPTIVE and uses their PGP modules for sending the files to third party.

For an encryption scenario, the third party has given their public key to us.

Please clarify me my understanding.

I assume we use their public key to encrypt the file and send it to them.

The third party will use their private key to decrypt the data sent by us.

In this, do we need to send our public key to the third party ?

I am a bit confused.

Regards

Anandh

[Former Member · Accepted solution]

Hi Anand,

Got it. You didn't use the module two times. Here is the approach. In the module list, use the encryption module 2 times.

1) localejbs/PGPEncryption, encryptAES

2) localejbs/PGPEncryption, encryptBlowFish

In the Module Configuration

encryptAES, encryptionAlgo = AES_256

encryptBlowFish, encryptionAlgo = BLOWFISH

This should work as expected. I would request you to try this appraoch in your test landsacpe by generating 2 different dummy key pairs. Link : http://wiki.sdn.sap.com/wiki/display/XI/Generating+ASCII+Armored+PGP+Key+Pairs

Thanks,

Siva

[Former Member · Accepted solution]

Hi Siva,

Apologize for not updating the case scenario. The vendor has agreed with us to encrypt the file either with blowfish or aes. Hence, I have updated the module BLOWFISH only.

I just want to make sure whether the module parameters used is correct.   I have used pgp keymanager where initiall i generated the public keyring and added the vendor certificate into it and signed it.

I am not sure whether it is mandatory to sign it or not.

Regards

Anandh.B

[Former Member · Accepted solution]

Hi Siva,

The one another confusing thing is assuming the partner has forwarded his public certificate.

Is it mandatory for us to add it in our public keyring and use it or can i directly refer the .asc in the module.

What is the difference between those?  I can see in your document that you have referred the partners public key directly as .asc.

Regards

Anandh.B

[Former Member · Accepted solution]

Hi Anandh,

• Signing is optional
• If you are encrypting the data, you need partner's public key in the key rings
• .asc is a ASCII Armored format of the key ring (and it's an optional)
• For the correctness of the module parameters, you have to verify against the product documentation.

A simple question again, Are you using SAP's PGP module (or) AEADAPTIVE's PGP module?

Thanks,

Siva

[Former Member · Accepted solution]

Hello Siva,

Thanks!  I am using PGP module provided by AEDAPTIVE and has checked the product documentation as well.

The file is getting encrypted without any issues as i checked the logs in adapter module.

Just want to reassure the basic concepts on this.

For AEDAPTIVE, providing the encryption algorithm is mandatory whereas for sap it is not.  I assume adding the partners public key into our key ring is same across all PGP vendor modules.

Regards

Anandh.B

[Former Member · Accepted solution]

You are correct. For SAP, if you didn't provide it will use 'CAST5' as a default

Thanks,

Siva