Pixie, [P] wrote: P> I'd like to stick with the internal implementations of either unless P> there is some flaw with that thinking..
From the S/MIME perspective, there seems to be a problem with full cross compatibility with the MS CryptoAPI system and the internal one. Signatures generated using one system, verify as bad when checking the signature using the other. I personally use PGP and prefer it since I don't have the above compatibility issue to worry about. I generate my own keys and don't need the services of a certificate authority. Using the internal PGP implementation would amount to using a v2 of PGP. As a result, you'll not be able to import and handle DH/DSS key types. Nowadays, most PGP users use that type of PGP key. So unless you and those you use PGP with are using only RSA type keys then, I'd advise not to use the internal version. I suggest using GnuPG or PGPv6.5.8ckt. For a crash course on how to get up and going, take a look at this page: http://www.landscreek.net/gpg_pgp_tb.html -- -= allie_M =- | List Moderator PGPKeys: http://www.ac-martin.com/pgpkeys.html _
pgp00000.pgp
Description: PGP signature
________________________________________________ Current version is 1.62r | "Using TBUDL" information: http://www.silverstones.com/thebat/TBUDLInfo.html
