public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Ron <rdwnj@yahoo•com>
To: "bitcoin-development@lists•sourceforge.net"
	<bitcoin-development@lists•sourceforge.net>
Subject: [Bitcoin-development] Dual elliptic curve algorithms
Date: Sun, 22 Dec 2013 13:37:41 -0800 (PST)	[thread overview]
Message-ID: <1387748261.7326.YahooMailNeo@web124504.mail.ne1.yahoo.com> (raw)
In-Reply-To: <mailman.384736.1387560790.12996.bitcoin-development@lists.sourceforge.net>

[-- Attachment #1: Type: text/plain, Size: 1209 bytes --]





________________________________
 From: "bitcoin-development-request@lists•sourceforge.net" <bitcoin-development-request@lists•sourceforge.net>
To: bitcoin-development@lists•sourceforge.net 
Sent: Friday, December 20, 2013 12:33 PM
Subject: Bitcoin-development Digest, Vol 31, Issue 37
 

Send Bitcoin-development mailing list submissions to
    bitcoin-development@lists•sourceforge.net

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Bitcoin-development digest..."

Hello all,

Is the dual elliptic curve algorithm mentioned in 
http://www.theguardian.com/world/2013/dec/20/nsa-internet-security-rsa-secret-10m-encryption 
from 2 days ago, of any concern to Bitcoin? I only ask, since I don't follow the field closely, but I see 
http://en.wikipedia.org/wiki/Elliptic_Curve_DSA 

Is this a concern for Bitcoin, or is this all "old news"?

Ron
_____________________________________
Bitcoin-development mailing list
Bitcoin-development@lists•sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-development


End of Bitcoin-development Digest, Vol 31, Issue 37
***************************************************

[-- Attachment #2: Type: text/html, Size: 2333 bytes --]

       reply	other threads:[~2013-12-22 21:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.384736.1387560790.12996.bitcoin-development@lists.sourceforge.net>
2013-12-22 21:37 ` Ron [this message]
2013-12-22 22:46   ` Mike Hearn

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=1387748261.7326.YahooMailNeo@web124504.mail.ne1.yahoo.com \
    --to=rdwnj@yahoo$(echo .)com \
    --cc=bitcoin-development@lists$(echo .)sourceforge.net \
    /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