[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #24774 [Core Tor/Tor]: Edit prop279 to support alternative name representations and non-English languages
#24774: Edit prop279 to support alternative name representations and non-English
languages
------------------------------------------------+--------------------------
Reporter: nullius | Owner: (none)
Type: enhancement | Status:
| needs_revision
Priority: Medium | Milestone: Tor:
| 0.3.3.x-final
Component: Core Tor/Tor | Version:
Severity: Normal | Resolution:
Keywords: prop279, review-group-28, tor-spec | Actual Points:
Parent ID: #10747 | Points:
Reviewer: | Sponsor:
------------------------------------------------+--------------------------
Changes (by nickm):
* status: needs_review => needs_revision
Comment:
+1 on using RFC3492 if we want unicode support.
As for the other changes:
* I like the idea of explicitly saying "This address is definitively
non-mapped; no other plugin should be allowed to map it.
* I am unconvinced that we need a * wildcard; the motivating examples
seems like something that could just as well be done within a separate
domain.
* I'm not sure that the sandboxing section is necessary. We should say
that _all_ plugins should only access the network over Tor, unless they
are using some comparably strong anonymity mechanism. And for filesystem
access, if we _do_ allow * wildcards, there's no reason to suppose that
they don't need caching as much as anything else.
I think that having separate patches for the different issues here might
make them easier to discuss.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/24774#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