What you use for Compat depends entirely on what program your colleague is using to decrypt. The OpenPGP standard allows for a comment in the first line, which is generally used to store information about the program that generated it, but Crypt::OpenPGP doesn't appear to save this information. It would be difficult to extract meaningful data from it, anyway.
The best option is to get everyone on a program that can understand the same block cipher. 3DES is a good choice; it's old and slow, but it's supported by just about everyone, and it's been pounded on for 20+ years and brute force is still the most efficent known way to break it.
----
I wanted to explore how Perl's closures can be manipulated, and ended up creating an object system by accident.
-- Schemer
: () { :|:& };:
Note: All code is untested, unless otherwise stated
| [reply]
[d/l]
[select] |
Ah, the intention is to produce something rather more general-purpose than that, which I can point at an arbitrary public key block.
I notice that my colleague (who's using PGP Freeware 7.0.3 for Mac) can select any of his imported keys and get information about ID, Type, Keysize, Creation date, Expiry date and Cipher; amongst the keys he has imported are ones specifying CAST, AES-256, AES-128 or IDEA as the cipher.
If it comes to it, I can always ask users to select a cipher from a list of those available, but I'm hoping to be able to provide the same auto-detect support that PGP Freeware is doing.
Hugo
| [reply] |