-----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
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
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
-
grarpamp -
Karsten Loesing