From: Mike Hearn <mike@plan99•net>
To: Gregory Maxwell <gmaxwell@gmail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>,
bitcoin-list@lists•sourceforge.net
Subject: Re: [Bitcoin-development] BitMail - p2p Email 0.1. beta
Date: Tue, 30 Jul 2013 10:40:45 +0200 [thread overview]
Message-ID: <CANEZrP2+jOTHsEv+qXpqLKJS3UATB_so2ZwQdL+AyJTd2zti4A@mail.gmail.com> (raw)
In-Reply-To: <CAAS2fgS=5ju1BFFDkjoRW65qdtojm3rYBHZcSMtUmHhyaTxMhA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2686 bytes --]
For people who are interested in such technologies, I recommend looking at
Pond:
https://pond.imperialviolet.org/
It is written by Adam Langley, so it comes with some serious credentials
behind it. It provides asynchronous email-like messaging that's forward
secure, resistant to traffic analysis and the whole thing runs over Tor.
Messages are stored for a week and are strictly limited in size. There's no
spam because nobody has an address - instead you have to grant someone the
ability to message you by giving them a small file. So, not really intended
as an email competitor convenience wise, but it has many interesting ideas
and a reasonable GUI.
As a testament to the seriousness with which Pond takes forward security,
it can use the NVRAM in a TPM chip to reliably destroy keys for data that
an SSD device might have otherwise made un-erasable.
The main downside - it's written in Go :)
On Tue, Jul 30, 2013 at 8:50 AM, Gregory Maxwell <gmaxwell@gmail•com> wrote:
> On Mon, Jul 29, 2013 at 10:01 PM, Randolph D. <rdohm321@gmail•com> wrote:
> > Secure P2P Email from Friend to Friend without relying on a central
> server.
> > Key- / Repleo-Exchange.
> > Full decentral Email-Network using the Echo Protocol.
> > Store Email for Offline-Friends in the P2P Network.
> > Chat and Instant Messaging is build in. Define & Add your friends.
> > Strong e2e Multi-Encryption (PGP-kind/AES over SSL: using libgcrypt).
> > Libspoton Integration.
> > Additional Security Layer with the GB-Feature for Emails.
> > Preventing Data Retention (VDS). WoT-less.
> > HTTP & HTTPS Connections.
> > Open Source. BSD License.
> >
> > anyone with a Server? Key?
>
> Keep safe everyone:
>
> A number of apparent sock accounts has been posting about what appears
> to be the same software under the name "goldbug" for a couple days
> now:
>
> e.g.
> https://lists.torproject.org/pipermail/tor-talk/2013-July/029107.html
> https://lists.torproject.org/pipermail/tor-talk/2013-July/029125.html
> http://lists.gnupg.org/pipermail/gnupg-users/2013-July/047137.html
>
>
> ------------------------------------------------------------------------------
> Get your SQL database under version control now!
> Version control is standard for application code, but databases havent
> caught up. So what steps can you take to put your SQL databases under
> version control? Why should you start doing it? Read more to find out.
> http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
[-- Attachment #2: Type: text/html, Size: 3981 bytes --]
next prev parent reply other threads:[~2013-07-30 8:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-30 5:01 Randolph D.
2013-07-30 6:50 ` Gregory Maxwell
2013-07-30 8:40 ` Mike Hearn [this message]
2013-07-30 11:27 ` Wendell
2013-07-30 12:12 ` Mike Hearn
[not found] ` <CAD2Ti29=Lzcun+0Jz7zn2Dt9G2a06f-0V8KEBUMHJTGxhHQV0A@mail.gmail.com>
2013-07-30 22:17 ` [Bitcoin-development] [bitcoin-list] " Mike Hearn
[not found] ` <CAD2Ti29zbac5YrW6+oMvb=8t7b1A31XckyC-mH7_qixLCRnFaQ@mail.gmail.com>
[not found] ` <51F886F6.1090108@gmail.com>
2013-07-31 9:08 ` Mike Hearn
[not found] ` <20130731133104.GW29404@leitl.org>
[not found] ` <CANEZrP3J1+ATYSRcAcJgGtwcJE+XXKjFrdkP-bYQS7VbxKfV-g@mail.gmail.com>
2013-07-31 15:54 ` Mike Hearn
2013-07-31 16:11 ` [Bitcoin-development] " Randolph D.
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=CANEZrP2+jOTHsEv+qXpqLKJS3UATB_so2ZwQdL+AyJTd2zti4A@mail.gmail.com \
--to=mike@plan99$(echo .)net \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=bitcoin-list@lists$(echo .)sourceforge.net \
--cc=gmaxwell@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