Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add bridge search support #8

Open
hellais opened this issue Feb 19, 2012 · 2 comments
Open

Add bridge search support #8

hellais opened this issue Feb 19, 2012 · 2 comments
Labels
feature

Comments

Assignees
No one assigned
Labels
feature
Projects
None yet
Milestone
No milestone
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
@kloesing @hellais
@hellais
Copy link
Owner

@hellais hellais commented Feb 19, 2012

Currently Tor Status only supports searches for relays. It should also support searching bridges.
@hellais hellais mentioned this issue Feb 19, 2012
Open
@kloesing
Copy link
Contributor

@kloesing kloesing commented Mar 12, 2012

See https://trac.torproject.org/projects/tor/ticket/5368 for an issue with Onionoo that should be solved before adding bridge search support.

@kloesing
Copy link
Contributor

@kloesing kloesing commented Mar 19, 2012

The aforementioned issue with Onionoo is now solved.

In short, Atlas should always run 40-character fingerprints through SHA1. That is, convert hex to binary, apply SHA1, convert back to hex. This works for relays and for bridges. This is really important in order to protect bridge fingerprints on the wire.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment