#26431: Document a threat model for stem.client ----------------------------+-------------------------- Reporter: dmr | Owner: dmr Type: task | Status: assigned Priority: Medium | Milestone: Component: Core Tor/Stem | Version: Severity: Normal | Resolution: Keywords: client website | Actual Points: Parent ID: | Points: Reviewer: | Sponsor: ----------------------------+-------------------------- Changes (by dmr):
* owner: atagar => dmr * status: needs_information => assigned Comment: Replying to [comment:3 atagar]: > Hi Dave, do we still need this ticket? I think the original questions prompted by the ticket have been [comment:2 answered by teor]. However, I'd like to keep the ticket open - I think it should be documented to make sure this is readily apparent to stem.client consumers. I view this as something to be done at the time that a user-facing API is described. Assigning to self - I can take of this. Replying to [comment:2 teor]: > When we have a draft guide for embedding Tor in other browsers (like Firefox, Brave, or Cliqz), it might contain some useful information about threat models for alternative implementations. teor, do you know where this info will live? I would be great to link to (at least, eventually). -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/26431#comment:4> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online
_______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs