From: Christopher Faylor <me@cgf.cx>
To: overseers@sourceware.org
Subject: [Ondrej.Caletka@cesnet.cz: [sourceware root] Broken TLSA record for sourceware.org]
Date: Wed, 17 Feb 2016 16:18:00 -0000 [thread overview]
Message-ID: <20160217161803.GB724@ednor.casa.cgf.cx> (raw)
----- Forwarded message from Ondřej Caletka <Ondrej.Caletka@cesnet.cz> -----
From: Ondřej Caletka <Ondrej.Caletka@cesnet.cz>
To: root@sourceware.org
Subject: [sourceware root] Broken TLSA record for sourceware.org
Date: Wed, 17 Feb 2016 14:30:43 +0100
Hello,
I've just spotted that the TLSA DNS record does not match the TLS
certificate offered by your server:
$ python2 ./swede verify sourceware.org
Received the following record for name _443._tcp.sourceware.org.:
Usage: 3 (End-Entity)
Selector: 0 (Certificate)
Matching Type: 1 (SHA-256)
Certificate for Association:
2a6f3a07349657f6b7f3575c12b7137b7e29e5494f9601b65775d0045a951ead
This record is valid (well-formed).
Attempting to verify the record with the TLS service...
Got the following IP: 209.132.180.131
FAIL (Usage 3): The certificate offered by the server does not match the
TLSA record
--
Best regards,
Ondřej Caletka
CESNET z.s.p.o.
----- End forwarded message -----
reply other threads:[~2016-02-17 16:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160217161803.GB724@ednor.casa.cgf.cx \
--to=me@cgf.cx \
--cc=overseers@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).