Upcoming Onionoo version 3.0 will support searches by space-separated fingerprint
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Onionoo client developers, the upcoming Onionoo version 3.0 will support searches by space-separated fingerprint. To give you an example, the following two searches will both return moria1 as result, using the new version 3.0: "9695DFC35FFEB861329B9F1AB04C46397020CE31" "9695 DFC3 5FFE B861 329B 9F1A B04C 4639 7020 CE31" (In the current version 2.6 that second search wouldn't return anything, because it would look for a fingerprint starting with 9695 *and* starting with DFC3 *and* starting with...) You can try out the new behavior by using the Onionoo/Atlas/Globe mirrors run on thecthulhu.com: https://atlas.thecthulhu.com/#details/9695DFC35FFEB861329B9F1AB04C46397020CE... https://atlas.thecthulhu.com/#search/9695%20DFC3%205FFE%20B861%20329B%209F1A... The corresponding service instances run on torproject.org have not been updated yet, so that only the first search will return a result: https://atlas.torproject.org/#details/9695DFC35FFEB861329B9F1AB04C46397020CE... https://atlas.torproject.org/#search/9695%20DFC3%205FFE%20B861%20329B%209F1A... (not expected to return anything until November 15, 2015!) The torproject.org instances will be updated in a month from now to give you the chance to update your clients. After all, your client might rely on the current behavior of the search parameter. (That's why this is a major protocol change, not because it's a major step towards world domination.) Please tell me if the new behavior doesn't work for you and you need me to make any changes/extensions. More details on the ticket: https://trac.torproject.org/projects/tor/ticket/17115 All the best, Karsten -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: GPGTools - http://gpgtools.org iQEcBAEBAgAGBQJWHjKCAAoJEJD5dJfVqbCr+o0H/3Q37+YVS1d2enBa+Z/aEZkx b21/vvIUHMjBWCh41MAEJrQNzczfrjhusjkSpY1amypE6R81mST8mizFvtKK5zVh P4QlB9L40tKRrASwK1Tz+qSRmx7A6fm4YSieAALuvcD8LeNfwzNlKRqNSoipwDWl 7NjITYhOeRmExbUjfqDbfs5woodsabHaXIrAOUeQvtljc36bj1OGtq15UroaqLdv MKjn7GgP3qR5NrPAZKYlAVW7Qxg6KIsPC9DXam7xh4CIyWja01WsKrUab80fUT0K N7wvq4oV7PZ84BomVG/Fte2Vk5hz2e53deshsxwjVB2BonHKpq+hzHsLX+pkCSU= =0cnD -----END PGP SIGNATURE-----
On Wed, Oct 14, 2015 at 6:46 AM, Karsten Loesing <karsten@torproject.org> wrote:
the upcoming Onionoo version 3.0 will support searches by space-separated fingerprint.
"9695DFC35FFEB861329B9F1AB04C46397020CE31"
"9695 DFC3 5FFE B861 329B 9F1A B04C 4639 7020 CE31"
Instead of continuing to backport and further embed useless legacy formats, will someone please write the proposal to get rid of the damn spaces. I've covered the reasons why at least twice before. Thanks.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 15/10/15 23:59, grarpamp wrote:
On Wed, Oct 14, 2015 at 6:46 AM, Karsten Loesing <karsten@torproject.org> wrote:
the upcoming Onionoo version 3.0 will support searches by space-separated fingerprint.
"9695DFC35FFEB861329B9F1AB04C46397020CE31"
"9695 DFC3 5FFE B861 329B 9F1A B04C 4639 7020 CE31"
Instead of continuing to backport and further embed useless legacy formats, will someone please write the proposal to get rid of the damn spaces. I've covered the reasons why at least twice before. Thanks.
It seems that the introduction of ed25519 identities will allow us to find a format that doesn't suffer from shortcomings like this one. Be sure to watch that process and raise your concerns while they can still be considered. At the same time this makes it less likely that somebody will touch the current RSA identities. All the best, Karsten -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: GPGTools - http://gpgtools.org iQEcBAEBAgAGBQJWIJIJAAoJEJD5dJfVqbCr1PUH/16dYoTH3lFkLqSfhmWDNLDQ yNYUBGB/3ro/Gn39l/1tc0+ZqgXcgtv5jvirdZ9wBrGNEzaOeEiiDcNXZpUrQ9g9 8QuPe+ERQmu/Hk20TmV0XtMh/nRpKVTWQrHBCOnIeXjhlVpyeAKUFRkUTXL5OQ3I fLYkGAli8jG8M49N9KYxiv9y4lizQFraiDqetrat1vzgngLtd5gBSXLmb6dQNHbv 7pQ1U3K9RoQ6Ra/J09CT1Ms+xIwuOHzw2TIbaBxHvmV/TkqarjMNxiRCChq1xk9Y NbaTgmaXtiPgMIR2AsM46vfmhVuGdzXCc7CtS9/yK/Udxa2lfVyTSJm57vneR2I= =jOw3 -----END PGP SIGNATURE-----
On Fri, Oct 16, 2015 at 1:58 AM, Karsten Loesing <karsten@torproject.org> wrote:
It seems that the introduction of ed25519 identities will allow us to find a format that doesn't suffer from shortcomings like this one. Be sure to watch that process and raise your concerns while they can still be considered.
Wherever that process is housed, someone can amend this to it... # fingerprints - descriptor Space removal, case normalization https://trac.torproject.org/projects/tor/ticket/12799
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 14/10/15 12:46, Karsten Loesing wrote:
Hello Onionoo client developers,
the upcoming Onionoo version 3.0 will support searches by space-separated fingerprint.
To give you an example, the following two searches will both return moria1 as result, using the new version 3.0:
"9695DFC35FFEB861329B9F1AB04C46397020CE31"
"9695 DFC3 5FFE B861 329B 9F1A B04C 4639 7020 CE31"
(In the current version 2.6 that second search wouldn't return anything, because it would look for a fingerprint starting with 9695 *and* starting with DFC3 *and* starting with...)
You can try out the new behavior by using the Onionoo/Atlas/Globe mirrors run on thecthulhu.com:
https://atlas.thecthulhu.com/#details/9695DFC35FFEB861329B9F1AB04C46397020CE...
https://atlas.thecthulhu.com/#search/9695%20DFC3%205FFE%20B861%20329B%209F1A...
The corresponding service instances run on torproject.org have not been updated yet, so that only the first search will return a result:
https://atlas.torproject.org/#details/9695DFC35FFEB861329B9F1AB04C46397020CE...
https://atlas.torproject.org/#search/9695%20DFC3%205FFE%20B861%20329B%209F1A...
(not expected to return anything until November 15, 2015!) I just deployed version 3.0 on onionoo.torproject.org, so that the URL above should now work. All the best, Karsten
The torproject.org instances will be updated in a month from now to give you the chance to update your clients. After all, your client might rely on the current behavior of the search parameter. (That's why this is a major protocol change, not because it's a major step towards world domination.) Please tell me if the new behavior doesn't work for you and you need me to make any changes/extensions.
More details on the ticket:
https://trac.torproject.org/projects/tor/ticket/17115
All the best, Karsten
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: GPGTools - http://gpgtools.org iQEcBAEBAgAGBQJWSN9PAAoJEJD5dJfVqbCrBEAH/1VlxoT7ck0jV2BsXtziXIns DIZM9gMEG+ns98DjJhLdxYgbrH3ItCR3NGNWGa8QM0thZca23b12jFkC+Xgu052g yeM37gqvsyENSWENK+QxkUfJrqYnaQvSi9g27rxpQw8GQi103KS06VH1Rp+hHNbm AwDLN83pdrKUSTdqOV1Xw8KQI7BKxGgMCQXDCch1KxjDCKpAg//JQeTdfSxc6TE0 K5Ic9iX/DOAYC/9uyD/XfHjtOUUG11Xz5uw7zHimq5UNvy8ue1rT+/c8T4/FMfGF 1Lpmbn/de1+lx/eXb8Iz1rw50U2Lx+pVBQhMxjxEmrNMuDwgAT78AtN2IOgozoc= =NHD5 -----END PGP SIGNATURE-----
participants (2)
-
grarpamp -
Karsten Loesing