public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Gregory Maxwell <gmaxwell@gmail.com>
To: bitcoin-development@lists.sourceforge.net,
	 bitcoin-list@lists.sourceforge.net
Subject: Re: [Bitcoin-development] BitMail - p2p Email 0.1. beta
Date: Mon, 29 Jul 2013 23:50:12 -0700	[thread overview]
Message-ID: <CAAS2fgS=5ju1BFFDkjoRW65qdtojm3rYBHZcSMtUmHhyaTxMhA@mail.gmail.com> (raw)
In-Reply-To: <CAEvNM8=yQn8sE4Lrf5+xedfm4RomBkBVhVWOdFFXxPEk7wZYDw@mail.gmail.com>

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



  reply	other threads:[~2013-07-30  6:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-30  5:01 [Bitcoin-development] BitMail - p2p Email 0.1. beta Randolph D.
2013-07-30  6:50 ` Gregory Maxwell [this message]
2013-07-30  8:40   ` Mike Hearn
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='CAAS2fgS=5ju1BFFDkjoRW65qdtojm3rYBHZcSMtUmHhyaTxMhA@mail.gmail.com' \
    --to=gmaxwell@gmail.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=bitcoin-list@lists.sourceforge.net \
    /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