S/MIME examples

Paul Hoffman / IMC | 3 Apr 2003 01:10

RE: Certificate email addresses


At 3:01 PM -0800 4/2/03, Blake Ramsdell wrote:
>  > -----Original Message-----
>>  From: Paul Hoffman / IMC [mailto:phoffman <at> imc.org]
>>  Sent: Wednesday, April 02, 2003 2:09 PM
>>  To: Blake Ramsdell; 'ietf-smime-examples'
>>  Subject: RE: Certificate email addresses
>>
>>
>>  At 2:05 PM -0800 4/2/03, Blake Ramsdell wrote:
>>  >AliceRSASignByCarl         aliceRsa <at> examples.com
>>  >BobRSASignByCarl           bobRsa <at> examples.com
>>  >DianeRSASignEncryptByCarl  dianeRsa <at> examples.com
>>
>>  That's *example*, not *examples*.
>
>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.

--Paul Hoffman, Director
--Internet Mail Consortium

(Continue reading)

headers

Blake Ramsdell | 3 Apr 2003 01:24

RE: Certificate email addresses

> -----Original Message-----
> From: owner-ietf-smime-examples <at> mail.imc.org 
> [mailto:owner-ietf-smime-examples <at> mail.imc.org] 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.

(Continue reading)