From: Roy Badami <roy@gnomon.org.uk>
To: Gregory Maxwell <gmaxwell@gmail.com>
Cc: g@gnomon.org.uk,
bitcoin list <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Secure download
Date: Sun, 3 Mar 2013 20:25:16 +0000 [thread overview]
Message-ID: <20130303202516.GW68379@giles.gnomon.org.uk> (raw)
In-Reply-To: <CAAS2fgSRYcC4e0E5UiXnLUYZHOkRkvgVdRnmOBWfqcXEKdkgFQ@mail.gmail.com>
> (The reason for this is that (many? most? all?) CAs verify authority
> by having you place a file at some HTTP path on the domain in
> question.
IME most CAs verify by emailing hostmaster/webaster@ or one of the
contacts in the WHOIS. But you're right, still subject to a MitM.
Still better than nothing though.
I would have suggested an EV cert, but that's more expensive (and
still far from foolproof)
> Basically only helps with the evil hotspot/tor_exit problem.
Also helps protect against DNS spoofing attacks, but yes, you're
right. I should be checking GPG sigs but I'm lazy :-)
roy
next prev parent reply other threads:[~2013-03-03 20:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-02 19:39 [Bitcoin-development] Secure download webmaster
2013-03-02 21:09 ` Gavin Andresen
2013-03-03 18:55 ` Roy Badami
2013-03-03 20:02 ` Gregory Maxwell
2013-03-03 20:25 ` Roy Badami [this message]
2013-03-05 12:37 ` Roy Badami
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=20130303202516.GW68379@giles.gnomon.org.uk \
--to=roy@gnomon.org.uk \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=g@gnomon.org.uk \
--cc=gmaxwell@gmail.com \
/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