From: Roy Badami <roy@gnomon•org.uk>
To: Gavin Andresen <gavinandresen@gmail•com>
Cc: bitcoin list <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Secure download
Date: Tue, 5 Mar 2013 12:37:50 +0000 [thread overview]
Message-ID: <20130305123750.GB68379@giles.gnomon.org.uk> (raw)
In-Reply-To: <20130303185446.GU68379@giles.gnomon.org.uk>
> Would be nice to have a secure page at bitcoin.org, though, rathar
> than having to go to github - certs from somewhere like Namecheap
> should cost you next to nothing.
And Namecheap now accept Bitcoin :-)
(Complete coincidence - I didn't know that when I posted)
roy
prev parent reply other threads:[~2013-03-05 12:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-02 19:39 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
2013-03-05 12:37 ` Roy Badami [this message]
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=20130305123750.GB68379@giles.gnomon.org.uk \
--to=roy@gnomon$(echo .)org.uk \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=gavinandresen@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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