-----BEGIN PRIVACY-ENHANCED MESSAGE-----
Proc-Type: 4,MIC-CLEAR
Content-Domain: RFC822
Originator-ID-Asymmetric:
ME0xCzAJBgNVBAYTAlVTMSAwHgYDVQQKExdSU0EgRGF0YSBTZWN1cml0eSwgSW5j
LjEcMBoGA1UECxMTUGVyc29uYSBDZXJ0aWZpY2F0ZQ==,12
MIC-Info: RSA-MD5,RSA,
O7HHAVx5U3n3/6mwYT9erNdG2nI7NKTCu43ROghKxkUlvGs6SIHaSORuWqe/MCdn
eaNzAuywk3LdAA6cjE0fgOomn7aGYqf5vKpyBlqQ7b5mt0Q6YIAfrbFsu1eqlfUb
In the case where
"Originator-ID-Asymmetric" Field is provided, there is no protected name
of the originator, thus there is no origin to protect.
When Originator-ID-Asymmetric is used, it points to a specific certificate
and presumes that the recipient already has or is able to obtain that
certificate. (Or you can follow up with a msg. to the purported
originator asking for his certificates...)
Thus, it's substitutable for a certificate.
For example, in a previous msg., I had included a certificate so if you had
ran that msg. through a PEM implementation, it would've cached the certificate.
Thus, you can verify that this msg. was signed by the same certificate.
If you didn't care to run my previous msg. through PEM and have since disposed
of it, you can always ask me to send you my certificates. Or, if the RSA
Persona CA provided retrieval services, which it doesn't, you may be able
to send it a request for the certificate identified in this msg.
-Ray
-----END PRIVACY-ENHANCED MESSAGE-----
Created with RIPEM Mac.