RE: Certificate email addresses

> -----Original Message-----
> From: [email protected] 
> [mailto:[email protected]] On Behalf Of 
> Paul Hoffman / IMC
> Sent: Wednesday, April 02, 2003 3:10 PM
> To: Blake Ramsdell; 'ietf-smime-examples'
> Subject: RE: Certificate email addresses
> 
> At 3:01 PM -0800 4/2/03, Blake Ramsdell wrote:
> >Then there's a lot more certificates that need to be regenerated ;)
> >Like all of them.
> >
> >Blake
> 
> Yaaarg, you're right. Never mind.
> 
> In the future, we are supposed to use "example.com", as specified in 
> BCP 32. No big deal, though.

OK, I'm going to do the following:

1. Regenerate the certificates I specified using "examples.com" for
consistency's sake.

2. If 1 goes OK, I will regenerate all of them with "example.com".  I
don't have a Diffie-Hellman implementation, but that shouldn't be
relevant -- the public key is opaque for the purpose of generating the
certificate, so it is unlikely that I will mess it up.

The only risk with 2 is that I break something in the re-encoding
process (possible).  Let me see how carefully I can tinker with their
brains ;).

Blake