Ø 1.3.6.1.4.1.22232.15.0: Curve25519 (That's out of my arc)
I’ve been in touch with Dan, who sent me to Werner Koch, who said that GPG is
using
{ Curve25519, 1.3.6.1.4.1.3029.1.5.1 }, -- Peter Gutmann's arc
So we should use that
I’m gonna post an I-D today or tomorrow, and ask the TLS-WG
1.3.6.1.4.1.22232.15.0: Curve25519 (That's out of my arc)
X coordinate is an OCTET STRING.
Y coordinate is a 0-byte OCTET STRING (since it's not defined as optional
in ASN.1, it must be present -- but how can you compress what doesn't
exist?)
When does the Point Compression patent expire,
On Thu, Jan 02, 2014, Salz, Rich wrote:
So Curve25519 needs a standard OID and some notes on the format to use for
ASN.1. Does such a thing exist?
I don't think so. Perhaps the TLS list is the place to discuss this? Should
we (I?) start a thread there on a proposal to fit Curve25519
On 02/01/2014 01:44, Kyle Hamilton wrote:
djb has a fixed-clock-cycle algorithm he wrote in GNU assembly for Athlon.
I am unhappy with his insistence that nobody should try to implement it for
other platforms, as though Athlon is the only platform anyone would ever
need. I agree that a
On Thu, Jan 02, 2014, Daniel Kahn Gillmor wrote:
On 01/02/2014 08:50 AM, Salz, Rich wrote:
[Dr. Stephen Henson wrote:]
So Curve25519 needs a standard OID and some notes on the format to use for
ASN.1. Does such a thing exist?
I don't think so.
yes, i mentioned it up-thread:
On 01/02/2014 12:35 PM, Dr. Stephen Henson wrote:
That's just TLS. To add more complete support to OpenSSL including storing
private keys in PEM files and public keys in case we ever use it in ECDH
certificates it needs an OID and some details on how the keys are encoded.
But ECDHE doesn't
On Thu, Jan 02, 2014 at 12:59:39PM -0500, Daniel Kahn Gillmor wrote:
On 01/02/2014 12:35 PM, Dr. Stephen Henson wrote:
That's just TLS. To add more complete support to OpenSSL including storing
private keys in PEM files and public keys in case we ever use it in ECDH
certificates it needs an
Hi,
I recently ran into this:
http://safecurves.cr.yp.to/
It seems that openssl doesn't support any of the curves that are
listed there as safe.
At least the curve 25519 is popular and has a draft for using it
in TLS. Would it be possible to add at least support for that
curve?
Kurt
On 01/01/2014 03:45 PM, Kurt Roeckx wrote:
Hi,
I recently ran into this:
http://safecurves.cr.yp.to/
It seems that openssl doesn't support any of the curves that are
listed there as safe.
At least the curve 25519 is popular and has a draft for using it
in TLS. Would it be possible to
Curve25519 public keys are 32-byte strings of digits. Private keys are
32-byte strings of digits. The agreement algorithm doesn't use the Y
coordinate at all.
djb has a fixed-clock-cycle algorithm he wrote in GNU assembly for Athlon.
I am unhappy with his insistence that nobody should try to
10 matches
Mail list logo
