-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
Things look good in ed25519_keygen - git-018082ef88b688e2.
I can confirm the last defect was fixed (now it saves to disk
ed25519_master_id_public_key if it only has ed25519_signing_cert -
valid and ed25519_signing_secret_key).
Log messages are
On Thu, Aug 6, 2015 at 6:26 PM, s7r wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> I am also sending the steps I imagine Tor should take when started as
> a relay. Apologies if I am missing something obvious.
>
> They are expressed as simple as possible, Tor's interpretation is way
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I am also sending the steps I imagine Tor should take when started as
a relay. Apologies if I am missing something obvious.
They are expressed as simple as possible, Tor's interpretation is way
more complex than this, but I think/hope this might hel
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
>> Thanks; this is incredibly helpful!
>
>> I've started a branch to do a test case to demonstrate all these
>> bugs ; it's called "ed25519_keygen" in my public repository. It
>> also adds a couple more features to '--keygen'. It does cases
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
That is great.
One thing which could help identifying the bugs faster: Tor gives too
much importance to ed25519_master_id_public_key (if it doesn't see
this file, it will generate a new unrequested identity regardless if
it has a valid signing_cert
On Tue, Aug 4, 2015 at 8:24 PM, s7r wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On 8/4/2015 5:42 PM, Nick Mathewson wrote:
>> Hi, s7r!
>>
>> This is an impressive writeup; thanks!
>>
>> One thing that makes it hard for me to follow this document is
>> that I'm not sure which par
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 8/4/2015 5:42 PM, Nick Mathewson wrote:
> Hi, s7r!
>
> This is an impressive writeup; thanks!
>
> One thing that makes it hard for me to follow this document is
> that I'm not sure which parts are describing how things work _now_,
> and which pa
On Mon, Aug 3, 2015 at 6:55 PM, s7r wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Hi,
>
> Tor 0.2.7.x will support Ed25519 router identities along with the
> traditional 1024-bit RSA ones which will be used simultaneously for
> some time, until we will completely deprecate RSA rou
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
Tor 0.2.7.x will support Ed25519 router identities along with the
traditional 1024-bit RSA ones which will be used simultaneously for
some time, until we will completely deprecate RSA router identities.
I would like to document what Tor needs t
