[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #17248 [Applications/Tor Browser]: Investigate new WebExtensions API requirements for our extensions
#17248: Investigate new WebExtensions API requirements for our extensions
--------------------------------------+--------------------------
Reporter: gk | Owner: tbb-team
Type: task | Status: closed
Priority: High | Milestone:
Component: Applications/Tor Browser | Version:
Severity: Normal | Resolution: fixed
Keywords: TorBrowserTeam201512 | Actual Points:
Parent ID: | Points:
Reviewer: | Sponsor:
--------------------------------------+--------------------------
Changes (by tom):
* cc: tom (added)
Comment:
Replying to [comment:2 brade]:
> NS10: TCP communication to the Tor control port
> Current Solution: nsISocketTransportService.createTransport()
> Notes: Tor Launcher uses non-blocking sockets as well as
nsIInputStream.asyncWait(). Also, in the future we want to be able to use
UNIX domain sockets.
I think that https://developer.mozilla.org/en-US/Add-
ons/WebExtensions/API/Runtime/connectNative might be a workable solution
to this one. Obviously it would require the other side (Tor's control
port) to change.
UNfortunetly, the only currently defined type for the communication is
using standard input/output, so it'd require Tor's control port to change
quite drastically....
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/17248#comment:12>
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