[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #10614 [Tor]: pt-spec.txt describes using `keyid=fingerprint` in torrc `Bridge` lines
#10614: pt-spec.txt describes using `keyid=fingerprint` in torrc `Bridge` lines
------------------------+----------------------------------
Reporter: isis | Owner: isis
Type: defect | Status: needs_review
Priority: minor | Milestone:
Component: Tor | Version:
Resolution: | Keywords: easy,tor-spec,tor-pt
Actual Points: | Parent ID:
Points: |
------------------------+----------------------------------
Comment (by dcf):
Replying to [comment:4 asn]:
> Replying to [comment:3 nickm]:
> > Since this is an 0.2.5 change, we might as well just add the missing
syntax and document that it was missing before the proper version, right?
> >
> > There's a patch to add the missing feature as bug10614 in my public
repository. How does that look?
>
> First we should figure out whether we actually want this `keyid`
syntactic sugar. As far as I can see, it's not needed for parsing the
line, and it also complicates the format (`keyid=` is a `k=v` value but
with different semantics than the `k=v` values that follow it). Do you
know what was the original purpose of it?
I agree. It seems to me there is no reason for the `keyid=`, and it
promotes confusion with the `k=v` pairs that may follow. (For instance, a
bridge may legitimately have a keyâvalue pair with a key called `keyid`,
and that would be really confusing.)
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/10614#comment:5>
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