> On 26 Jan 2017, at 10:19, teor <teor2345@xxxxxxxxx> wrote: > >>> onion_address = base32(pubkey || checksum || version) > > Is the order in which the address is encoded once the checksum is > calculated. checksum represents (the first two bytes of) the result of > the SHA3 hash. > > We put pubkey first so that humans can distinguish addresses. > (We could put checksum first, but that's non-standard.) I just talked with some people who run a large onion site. They asked if we can put the checksum at the front of the encoded address. This makes phishing with different bit(s) in the tail of the address much harder. (That is, searching for a matching prefix for an existing address is much harder if the checksum changes the first two characters unpredictably. People ignore the checksum if it's at the end.) T -- Tim Wilson-Brown (teor) teor2345 at gmail dot com PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n xmpp: teor at torproject dot org ------------------------------------------------------------------------
Attachment:
signature.asc
Description: Message signed with OpenPGP
_______________________________________________ tor-dev mailing list tor-dev@xxxxxxxxxxxxxxxxxxxx https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev