From: "Randolph D." <rdohm321@gmail.com>
To: drwho@virtadpt.net
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] BitMail.sf.net - encrypted p2p email
Date: Tue, 13 Aug 2013 22:46:38 +0200 [thread overview]
Message-ID: <CAEvNM8mY=0+rgC0psoNkVVC0ktwCnwARA9GNe8D7FibCBUHt1g@mail.gmail.com> (raw)
In-Reply-To: <520A93DE.8080409@virtadpt.net>
[-- Attachment #1: Type: text/plain, Size: 1858 bytes --]
you mixed up BitMail with BitMessage, this is different:
http://bitmail.sf.net
2013/8/13 The Doctor <drwho@virtadpt.net>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 08/09/2013 03:01 PM, Randolph D. wrote:
> > anyone tested the secure encrypted p2p email:
> > http://bitmail.sf.net
>
> Not lately. It's pretty CPU and network intensive, which may or may
> not be detrimental to your use case.
>
> I keep meaning to read through these security analyses of Bitmessage
> but I'm a little short on compute cycles at the moment:
>
> https://bitmessage.org/forum/index.php?topic=1666.0
>
>
> http://www.reddit.com/r/bitmessage/comments/1fwyx7/a_security_analysis_of_bitmessage/
>
> - --
> The Doctor [412/724/301/703] [ZS]
> Developer, Project Byzantium: http://project-byzantium.org/
>
> PGP: 0x807B17C1 / 7960 1CDC 85C9 0B63 8D9F DD89 3BD8 FF2B 807B 17C1
> WWW: https://drwho.virtadpt.net/
>
> If at first you don't succeed, call for an airstrike.
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.20 (GNU/Linux)
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iEYEARECAAYFAlIKk94ACgkQO9j/K4B7F8FMsgCgkuM56fI4hVT9H1ueZSFwl9Kk
> qRoAoJkKZf4afKgVQKtDO6zRd/Auc/RV
> =zwmX
> -----END PGP SIGNATURE-----
>
>
> ------------------------------------------------------------------------------
> Get 100% visibility into Java/.NET code with AppDynamics Lite!
> It's a free troubleshooting tool designed for production.
> Get down to code-level detail for bottlenecks, with <2% overhead.
> Download for free and get started troubleshooting in minutes.
> http://pubads.g.doubleclick.net/gampad/clk?id=48897031&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: 3086 bytes --]
next prev parent reply other threads:[~2013-08-13 20:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-09 19:01 [Bitcoin-development] BitMail.sf.net - encrypted p2p email Randolph D.
2013-08-09 21:23 ` Wendell
2013-08-13 20:15 ` The Doctor
2013-08-13 20:46 ` Randolph D. [this message]
2013-08-14 17:02 ` The Doctor
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='CAEvNM8mY=0+rgC0psoNkVVC0ktwCnwARA9GNe8D7FibCBUHt1g@mail.gmail.com' \
--to=rdohm321@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=drwho@virtadpt.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