Skip to Content.
Sympa Menu

cacert-policy - AW: CCA - blue changes for Root Distribution License - call for vote!

Subject: Policy-Discussion

List archive

AW: CCA - blue changes for Root Distribution License - call for vote!


Chronological Thread 
  • From: <ulrich AT cacert.org>
  • To: <cacert-policy AT lists.cacert.org>
  • Subject: AW: CCA - blue changes for Root Distribution License - call for vote!
  • Date: Mon, 18 Oct 2010 16:30:11 +0200
  • Authentication-results: lists.cacert.org; dkim=pass (1024-bit key) header.i= AT cacert.org; dkim-asp=none
  • Importance: Normal

Hi Morten,

> openssl x509 -noout -in root.crt -md5 -fingerprint
> MD5 Fingerprint=A6:1B:37:5E:39:0D:9C:36:54:EE:BD:20:31:46:1F:6B
> openssl x509 -noout -in root.crt -sha1 -fingerprint
> SHA1
Fingerprint=13:5C:EC:36:F4:9C:B8:E9:3B:1A:B2:70:CD:80:88:46:76:CE:8F:33



> If possible I'd like to create my own cap form, which has this:
> md5  sha  sha1  sha224  sha256  sha384  sha512

> in Huge Fonts. Is that Legal?

Arbitration ruling on a20090303.1
https://wiki.cacert.org/Arbitrations/a20090303.1
states in short: There is NO "official" CAP form.

in detail:
# There is currently no requirement for an APPROVED form.
# There is no apparatus defined for APPROVING the form, nor is here a
custom in use.
# Any form that includes the elements listed in AP should be treated as
valid.
  Or more precisely, an assurance should not be challenged merely on the
basis
  that the paperwork is not of an APPROVED form





> A6:1B:37:5E:39:0D:9C:36:54:EE:BD:20:31:46:1F:6B


regards, uli   ;-)

Attachment: smime.p7s
Description: S/MIME cryptographic signature




Archive powered by MHonArc 2.6.16.

Top of Page