View Issue Details

IDProjectCategoryView StatusLast Update
0000676Main CAcert Websitecertificate issuingpublic2009-02-18 08:07
Reportergalphanet Assigned To 
PrioritynormalSeverityfeatureReproducibilityN/A
Status newResolutionopen 
Summary0000676: Request to add an e-mail address on every certificates issued.
DescriptionAdd Issuer's E-Mail address on every certificates.

So in case of problems/questions regarding the certificat, the end-user can contact the sysadmin and it would add some "security" for the end-user.

We discussed with Philipp Gühring about which e-mail address must appear, you will find parts of our conversation in "Additional Information".
Additional InformationHere is some part of our e-mail conversation with Philipp Gühring:

> It would be great if the email address of the issuer is written on the
> server certificate.
> So in case of problems/questions regarding the certificat, the
> end-user can contact the sysadmin and it would add some "security" for
> the end-user.
Hmm, yes, the idea makes some sense, yes.

> The email address which will appear on the certificate must be
> the one used to validate the domain's property (for example
> webmaster@example.com <mailto:webmaster@example.com> or postmaster@..)
> or the one used on CACert.org website ?
It must be one of the validated email addresses in the same account, I
would say.


> But the email address which will appear on the certificate must be
> the one used to validate the domain's property (for example
> webmaster@example.com <mailto:webmaster@example.com> or postmaster@..)
> or the one used on CACert.org website ?
>
> For me, it must be the one used to validate the domain's property
> but...what do you think ?
Good question, yes.
Hmm, true. Perhaps we should even demand that.
But until now, it didn't matter, which email address you chose to verify
a domain. With this change, it will matter which one you choose.
What if you want different certificates for different subdomains, and
different email addresses in each of them?
Something for our cacert-policy mailinglist ...
TagsNo tags attached.
Reviewed by
Test Instructions

Activities

galphanet

2009-02-18 08:07

reporter   ~0001277

Had some problems with the email conversation, sorry..

Issue History

Date Modified Username Field Change
2009-02-18 08:06 galphanet New Issue
2009-02-18 08:07 galphanet Note Added: 0001277