-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On Jun 6, 2011, at 5:49 AM, IOhannes m zmoelnig wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2011-06-02 02:37, Hans-Christoph Steiner wrote:
however, note that: the puredata.info certificates are signed by cacert.org [1], so
trusting the cacert.org authority would help establish a web of trust
(similar to gpg) for free server certificates.And here's a signed text version:
puredata.info
Not Valid Before: April 18, 2011 6:59:44 AM EDT Not Valid After: April 17, 2013 6:59:44 AM EDT
SHA1 03:DB:DC:0B:AD:48:73:AF:2D:52:BE:75:3B:D7:F4:0F:18:B8:BA:A7 MD5 97:09:4F:C7:6F:61:72:CB:E2:E0:08:38:FA:2F:F0:52
this is indeed true, and the reason for the mismatch is, that i was generating completely nonsense fingerprints (just running "md5sum"
resp. "sha1sum" on the certificate...oops, seems i was tired...)so here go the correct fingerprints as generated from: $ openssl x509 -noout -fingerprint -sha1 -in /path/to/pd.cert SHA1 Fingerprint=03:DB:DC:0B:AD:48:73:AF:2D:52:BE:75:3B:D7:F4:0F: 18:B8:BA:A7 $ openssl x509 -noout -fingerprint -md5 -in /path/to/pd.cert MD5 Fingerprint=97:09:4F:C7:6F:61:72:CB:E2:E0:08:38:FA:2F:F0:52
now these seem to be more correct :-) sorry for the confusion in such a delicate matter.
Yup, looks like everything matches, thanks.
.hc
Looking at things from a more basic level, you can come up with a more
direct solution... It may sound small in theory, but it in practice,
it can change entire economies. - Amy Smith