-----BEGIN PRIVACY-ENHANCED MESSAGE-----
Proc-Type: 4,MIC-CLEAR
Content-Domain: RFC822
Originator-ID-Asymmetric: MFMxCzAJBgNVBAYTAlVTMQswCQYDVQQIEwJNRDE
kMCIGA1UEChMbVHJ1c3RlZCBJbmZvcm1hdGlvbiBTeXN0ZW1zMREwDwYDVQQLEwh
HbGVud29vZA==,06
MIC-Info: RSA-MD5,RSA,AKFXUWw7qdKhVzplRApR4z33jp+gn9iCQGiFjaMSqye
YNpJCI0nhAMfT/Xl7e6Jo/V1f2fCtzDlBVoYXeH4ky1hxB6wX+2gp2BDbczlshMF
uQCk4uPHAoYcMXlR/oWE2
Before I go and beat up on the code significantly, does anybody have
patches for PEM to make it work with MH 6.8 as per the latest PEM-MIME
RFC's? I hate re-inventing the wheel - I'll settle for "mostly done
needs work" code.
Hi, Valdis. An awfully large distribution for that question (pem-dev
is the mailing list for all PEM developers and other interested
parties). Feel free to use tispem-support or tispem-users if you want
to narrow your audience.
Beating up on poor, defenseless TIS/PEM 6.1 to make if follow the new
standard probably isn't worth your time. We are working on a new,
considerably changed version that will follow the new MIME-PEM
integration standard and integrate with MH6.8 with only one source
file changed (mhn.c).
The new version is much more modular, with individual programs to
create signatures, add encryption, generate certificate/CRL chains,
verify signatures, remove encryption, and save certificate/CRL chains.
This should make it much easier to integrate TIS/PEM with other user
agents with little more than a bit of shell script glue.
We will be beta-testing the new version as soon as we have all the
necessary functionality. Shouldn't be too long. If anyone is
interested in more info, beta-testing, or anything else
TIS/PEM-related, send your mail to tispem-info(_at_)tis(_dot_)com(_dot_)
Mark
-----END PRIVACY-ENHANCED MESSAGE-----