Any opinions?
Hm. Every time we've displayed Ed25519 fingerprints so far, we've
used base64. I'm not sure that changing it will actually save more
confusion than it causes.
thanks for the prompt reply.
Hm, ok I guess then we have already reached the point of no return
where it is too late
On Sun, Oct 10, 2021 at 5:13 PM nusenu wrote:
>
> > On Tue, Aug 4, 2020 at 6:41 PM nusenu wrote:
> >>
> >> nusenu:
> >>> I'll wait until you (Tor developers) decided on the final naming and
> >>> format
> >>
> >> Is there any interest to move this topic forward to come to some decision
> >> in
On Tue, Aug 4, 2020 at 6:41 PM nusenu wrote:
nusenu:
I'll wait until you (Tor developers) decided on the final naming and format
Is there any interest to move this topic forward to come to some decision
in the near future? (before the end of the month)
I don't think that'd be too hard.
Hi,
since Neel is working on unix socket support [1] for MetricsPort
I'm preparing to add support for it to relayor.
I don't like to add additional attack surface to a relay but since
tor does not support TLS and basic auth on the MetricsPort I'll likely
install nginx that takes care of TLS and
nusenu:
cut -b 33- ed25519_master_id_public_key |base64
hint: don't use this
Since cut is line based it will only read until the end of the line
but the input file is not a text file - so it will stop reading at random
offsets.
--
https://nusenu.github.io
Hi,
has this proposal any implications wrt to making the MiddleOnly
feature available to clients (without requiring DA actions)?
With ExcludeExitNodes/ExitNodes + ExcludeGuardNodes [1]
tor clients basically can get the "MiddleOnly" feature without DA actions,
but ExcludeGuardNodes [1] is not
Yes, there is!
First you verify that the file is really 64 bytes long, and that the
first 32 bytes of the file are really "== ed25519v1-public: type0
==\0\0\0".
Having done that, you base64-encode the second 32 bytes of the file,
with no "=" padding.
thank you for this description, so I can
On Sun, Oct 10, 2021 at 8:44 AM nusenu wrote:
>
> Hi,
>
> given a relay's ed25519_master_id_public_key
> file, is there a simple way to generate the
> 43 chars long ed25519 identity string (also found in fingerprint-ed25519)?
>
Yes, there is!
First you verify that the file is really 64 bytes
Hi,
given a relay's ed25519_master_id_public_key
file, is there a simple way to generate the
43 chars long ed25519 identity string (also found in fingerprint-ed25519)?
thanks,
nusenu
--
https://nusenu.github.io
___
tor-dev mailing list
