Hi,

Currently i am working on a custom pipeline component to PGP encrypt and sign the outgoing message from Biztalk 2013 with public and private keys.

I am referring the content mentioned in the below posts

https://code.msdn.microsoft.com/windowsdesktop/BizTalk-Sample-PGP-ebcbc8b2

http://bajwork.blogspot.co.nz/2007/08/pgp-pipeline-component.html

But we have a requirement to use PGP version 6.5.8 and i could not find what PGP versions the above components supports.

Any one has any idea about Biztalk and PGP version 6.5.8 for encryption and signing?

The code is provided in the links you're referencing. It should be a fairly straight-forward method to identify the PGP API used and verify its support in the version you're wanting to use. If the currently used API is deprecated then you should be able to use the new API, rebuild the components and use them.

Regards.

Have you tried to contact the article author?

There are many components available online. Refer TechNet Article: BizTalk: List of Custom Pipeline Components

PGP Encode Component

You can also create your Custom pipeline component for PGP encryption using GNUPG software.

Rachit

The source code tells the version of API and not the version of PGP algorithm.  These pipelines components referred a third party crypto.dll from Bouncycastle project and i tried to find the PGP version that bouncy castle implemented but could not found it.

• Edited by Janardhan Bikka Wednesday, January 28, 2015 7:13 AM

The source code tells the version of API and not the version of PGP algorithm.  These pipelines components referred a third party crypto.dll from Bouncycastle project and i tried to find the PGP version that bouncy castle implemented but could not found it.

• Edited by Janardhan Bikka Wednesday, January 28, 2015 7:13 AM

The source code tells the version of API and not the version of PGP algorithm.  These pipelines components referred a third party crypto.dll from Bouncycastle project and i tried to find the PGP version that bouncy castle implemented but could not found it.

• Edited by Janardhan Bikka Wednesday, January 28, 2015 7:13 AM

Hi,

Have you checked the release notes, you can find them here.

It is my understanding that the API has to be provided by your PGP Client. So check if the PGP Client that you use supports the appropriate version. If it does and you use the API of this client then your pipeline component would be version compatible.

The missing dll could be of the PGP client and would be available if/when you install it on your system.

Regards.

It is my understanding that the API has to be provided by your PGP Client. So check if the PGP Client that you use supports the appropriate version. If it does and you use the API of this client then your pipeline component would be version compatible.

The missing dll could be of the PGP client and would be available if/when you install it on your system.

Regards.

• Marked as answer by Angie xuMicrosoft contingent staff, Moderator 9 hours 12 minutes ago

It is my understanding that the API has to be provided by your PGP Client. So check if the PGP Client that you use supports the appropriate version. If it does and you use the API of this client then your pipeline component would be version compatible.

The missing dll could be of the PGP client and would be available if/when you install it on your system.

Regards.

• Marked as answer by Angie xuMicrosoft contingent staff, Moderator Tuesday, February 03, 2015 2:14 AM

It is my understanding that the API has to be provided by your PGP Client. So check if the PGP Client that you use supports the appropriate version. If it does and you use the API of this client then your pipeline component would be version compatible.

The missing dll could be of the PGP client and would be available if/when you install it on your system.

Regards.

• Marked as answer by Angie xuMicrosoft contingent staff, Moderator Tuesday, February 03, 2015 2:14 AM

It is my understanding that the API has to be provided by your PGP Client. So check if the PGP Client that you use supports the appropriate version. If it does and you use the API of this client then your pipeline component would be version compatible.

The missing dll could be of the PGP client and would be available if/when you install it on your system.

Regards.

• Marked as answer by Angie xuMicrosoft contingent staff, Moderator Tuesday, February 03, 2015 2:14 AM

PGP has different versions and 6.5.8 is older one. If just download the Bouncy castle pgp dll, its not going to use the 6.5.8 version of PGP.

http://www.pgpi.org/products/pgp/versions/freeware/win32/6.5.8/

With latest Bouncy castle pgp dll, there are few issues encountered by the user you tried to use PGP version 6.5.8, especially around signature validation. Following are the discussion on the issues faced..

http://stackoverflow.com/questions/7193323/encrypt-with-bc-and-decrypt-with-pgp-6-5-8

http://bouncy-castle.1462172.n4.nabble.com/ERROR-encrypted-session-key-is-bad-when-trying-to-decrypt-td1466221.html

http://bouncy-castle.1462172.n4.nabble.com/Compatibility-Issue-with-PGP-6-5-8-td1467170.html

 People have manage to get it working with few changes to the PGP code (which you can get it here http://www.bouncycastle.org/csharp/index.html )

This forum is not the right place to raise question about finding the Bouncy castle pgp dll version compactable with v6.5.8. try to post this question here

http://bouncy-castle.1462172.n4.nabble.com/

Once you have their dll compactable with v 6.5.8, then you can use it in BizTalk suggested by the links referenced by you.

I agree with Shankycheil, the API [requirements] should be provided by client. "we have a requirement to use PGP version 6.5.8", that means your client use some libraries on its side or, at last, has an idea what library should be used.

So you can use this sample as a start point and replace Bounty Castle library with new one.