From: Christopher Faylor <me@cgf.cx>
To: overseers@sourceware.org
Subject: [Klaus@Ethgen.de: Invalid TLSA certificate]
Date: Wed, 17 Feb 2016 15:40:00 -0000 [thread overview]
Message-ID: <20160217154032.GA724@ednor.casa.cgf.cx> (raw)
WFM. Anyone else seeing this?
cgf
----- Forwarded message from Klaus Ethgen <Klaus@Ethgen.de> -----
From: Klaus Ethgen <Klaus@Ethgen.de>
To: postmaster@sourceware.org, webmaster@sourceware.org,
info@sourceware.org
Subject: Invalid TLSA certificate
Date: Wed, 17 Feb 2016 14:43:06 +0100
OpenPGP: id=79D0B06F4E20AF1C;
url=http://www.ethgen.ch/~klaus/79D0B06F4E20AF1C.txt; preference=signencrypt
Hello,
today I found my way to https://sourceware.org/ but my browser stopped
delivering of the page as your TLSA key does not match the https key!
I suspect that you have a big problem with an man in the middle here.
Maybe your hoster intercept your traffic. As your domain is secured with
DNSSEC, that scenario is very likely!
Regards
Klaus Ethgen
--
Klaus Ethgen http://www.ethgen.ch/
pub 4096R/4E20AF1C 2011-05-16 Klaus Ethgen <Klaus@Ethgen.ch>
Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C
----- End forwarded message -----
reply other threads:[~2016-02-17 15:40 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=20160217154032.GA724@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).