I honestly don't know how to answer this question in academic terms, but in 
layman terms, if THEY use commonly available PGP tools to generate a public 
and private key pair, and shares their public key with me, I am looking to 
load that key from disk (most likely in ASCII armored form which I naively 
presume being Base64, with whatever hearder and footer PGP puts in during 
the export), and be able to encrypt files so that THEY could decrypt them 
with the above mentioned PGP tools, be it Gnu PG, GPG4Win or anything else 
available. And in reverse, I am looking to be able to generate my own key 
pair, share the public key with them so that they would be able to load it 
into a key manager like Kleopatra and encrypt with it files which I should 
be able to decrypt on my end.

People do not think much of these things in real world: they just use the 
commonly available tool, specify key bitness at best, and go with the flow. 
For me that all sounds like fully supporting PGP. If this is already 
roughed in, a few code samples would be immensely helpful. As far as I 
know, PGP uses RSA keys and Triple DES encryption, but I may be talking out 
of my rear end. Also I know that keys shorter than 4096 bits are no longer 
considered secure with PGP. Here my knowledge ends.

I was able to support the above principles with Bouncy Castle relatively 
easily without having to know much about cryptography, but .NET is very 
onerous for this sort of development, as it does not allow to overwrite 
memory securely without enormous performance hit and has other nasty 
limitations. And this is the main reason I started looking towards a purely 
C++ solution with CryptoPP being the obvious champion.

Regards
Mahon

On Thursday, April 5, 2018 at 4:29:16 AM UTC-4, Jeffrey Walton wrote:
>
>
>
> On Wednesday, April 4, 2018 at 10:25:09 AM UTC-4, mahon...@gmail.com 
> wrote:
>>
>> Jeff,
>>
>> There is no mention of PGP in the roadmap on the Wiki (which is also 1 
>> version behind vs 6.2 mentioned in this group). Are there concrete plans 
>> for including the PGP scheme?
>>
>
> No, not at the moment.
>  
>
>> I am also very much interested in PGP support due to horrible memory 
>> management bestowed on Bouncy Castle by .NET and its mediocre performance. 
>> Crypto++ with its tiny memory footprint and portability is miles ahead of 
>> BC, and if it supported PGP OOB it would be a BC killer. And OpenGPG is a 
>> joke.
>>
>
> Well, to lay tentative plans we would need to know use cases. In 
> particular, what algorithms you need.
>
> It could be the case you have what you need and you only need to glue it 
> together.
>
> Jeff
>
>  
>

-- 
You received this message because you are subscribed to "Crypto++ Users". More 
information about Crypto++ and this group is available at 
http://www.cryptopp.com and 
http://groups.google.com/forum/#!forum/cryptopp-users.
--- 
You received this message because you are subscribed to the Google Groups 
"Crypto++ Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cryptopp-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to