[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #3589 [Tor Bridge]: Advertise bridge pluggable transports using extra-info lines
#3589: Advertise bridge pluggable transports using extra-info lines
-------------------------+--------------------------------------------------
Reporter: asn | Owner:
Type: enhancement | Status: new
Priority: normal | Milestone: Tor: 0.2.4.x-final
Component: Tor Bridge | Version:
Keywords: | Parent: #3591
Points: | Actualpoints:
-------------------------+--------------------------------------------------
Comment(by karsten):
Replying to [comment:6 nickm]:
> At this point, I'm thinking that the information might actually need to
go in both places: stuff that only the authority/bridgedb should know
about needs to go in extrainfo; stuff that the client needs to know about
*might* belong in the descriptor. Though I can imagine exceptions there.
It might be that knowing one transport to reach a bridge doesn't entitle
you to know all of them, for instance.
Oh, I hadn't thought of the client not knowing a bridge's extra-info
descriptor as a security property.
Are we sure there's no way for a client to learn a bridge's extra-info
descriptor? (I didn't find one, but I may have missed something.)
By the way, a client can easily look up a bridge's sanitized extra-info
descriptor, and we're
[https://metrics.torproject.org/formats.html#bridgedesc not sanitizing
much of those]. Is that problematic for existing extra-info descriptor
contents? We might want to discuss sanitizing pluggable transport lines
in extra-info descriptors in the future. (Right now, unknown lines are
simply dropped in the sanitizing process.)
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/3589#comment:7>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs