> proposal, I guess, by having documents signed with Ed25519 and
> RSA1024... but one of the signatures is much better than the other:
> 255-bit ECC groups will be secure long after RSA1024 has fallen.
I think the reference I saw was referring not to extended effective key
length [1] but to offset
On Tue, Aug 13, 2013 at 4:19 PM, grarpamp wrote:
> Thought I'd note seeing some projects xor different
> encryption types together, usually for stream encryption,
> so as to not rest all on one. That's not to suggest such
> ideas might of use within Tor, just something seen when
> balancing what t
On Tue, Aug 13, 2013 at 4:25 PM, Maxim Kammerer wrote:
> On Tue, Aug 13, 2013 at 4:13 AM, Nick Mathewson
> wrote:
>>
>>Ed25519 (specifically, Ed25519-SHA-512 as described and specified at
>>http://ed25519.cr.yp.to/) is a desirable choice here: it's secure,
>>fast, has small keys and s
On Tue, Aug 13, 2013 at 2:54 PM, Sebastian G.
wrote:
[...]
> Did you plan to use a closing bracket or is something missing?
Thanks! I've filled in these gaps in the version in the torspec Git repository.
(These unfinished sentences are a side-effect of my writing style. I
get an idea for the
On Tue, Aug 13, 2013 at 4:13 AM, Nick Mathewson wrote:
>Ed25519 (specifically, Ed25519-SHA-512 as described and specified at
>http://ed25519.cr.yp.to/) is a desirable choice here: it's secure,
>fast, has small keys and small signatures, is bulletproof in several
>important ways, an
Thought I'd note seeing some projects xor different
encryption types together, usually for stream encryption,
so as to not rest all on one. That's not to suggest such
ideas might of use within Tor, just something seen when
balancing what to use arises.
__
13.08.2013 Nick Mathewson:
> 6. Naming nodes in the interface
>
>Anywhere in the interface that takes an $identity should be able to
>take an ECC identity too. ECC identities are case-sensitive base64
>encodings of Ed25519 identity keys. You can use $ to indicate them as
>well; we
13.08.2013, Nick Mathewson:
> 2.3.1. Checking descriptor signatures.
>
>Current versions of Tor will handle these new formats by ignoring the
>new fields, and not checking any ed25519 information.
>
>New version of Tor will have a flag that tells them whether to check
>ed25519 inf
Here's a proposal I wrote about node key migration. I hope it meshes
well with the authority identity migration proposal that Jake and
Linus are doing. There are probably holes and mistakes here: let's
fix them.
Filename: 220-ecc-id-keys.txt
Title: Migrate server identity keys to Ed25519
Author
