Hi,
> tjr:
> [...]
> * Other: I am considering writing a tbb-dev proposal to increase the
> max content processes from 4 to 999. This would increase memory
> consumption, especially for users with a lot of tabs. It would provide
> some small level of tab isolation at the process level, but only for new
> tabs opened, not tabs reused. The security gain contains a lot of "Well
> if the user does this, things are kinda better, but if they do this
> they're no better." So not sure if it's useful, the main draw is that
> it's a 4 character patch, so easy to do, just difficult to decide one.
FWIW, in Tails we had to decrease dom.ipc.processCount to 2 on systems
with less than 3GB of RAM:
https://bugzilla.mozilla.org/show_bug.cgi?id=1066789#c5
Hi all!
We thought about meeting at 1900 UTC next Wed (November 7) to hammer out
the last issues for our security control redesign. Place is, as usual,
the OFTC IRC network in the #tor-meeting channel.
Please join us if you can!
The current proposal[1] and a summary of where we are and what still
needs to be done[2] are good starting points to get up to speed in case
you missed previous discussions.
See you there,
Georg
[1]
https://gitweb.torproject.org/tor-browser-spec.git/tree/proposals/101-secur…
[2] https://trac.torproject.org/projects/tor/ticket/25658#comment:45
Hi all!
Summer time is about to end (and ended in Europe already), so we move
our meeting time accordingly to 1900 UTC starting from next week on
Monday (Nov 5). The location stays the same, though: OFTC IRC network in
#tor-meeting.
Georg
Hi!
Below comes the link to our tentative roadmap:
https://pad.riseup.net/p/tbb-roadmap-2018-19
I still need to talk to the network-team to make sure we are on the same
page with respect to items they have on their radar and which we need.
In brackets are potential sponsors for work we want to do (some of this
is currently under submission).
I assigned folks to work on particular items but that's not finalized
yet. Please speak up if you'd like to have different assignments.
The work for Q1 in 2019 is not as detailed yet to give us more
flexibility and pick up more important stuff in case it emerges.
I hope we can finalize the roadmap this week and think we should talk
about it in our meeting later today.
Georg
Kevin Gallagher posted his et al.'s paper on Tor Browser UX on the ux
list.
https://lists.torproject.org/pipermail/ux/2018-September/000427.html
Some user quotations you may appreciate:
Several participants perceived using the Tor Browser as a
learning experience. For instance, some Tor Browser warnings
made them aware of threats to anonymity they had not previously
considered, such as HTML5 canvas data, window maximization, etc.
“I really enjoyed that when you resize the Tor window, it
notifies you that, while you may choose to do so, it actually
makes your device more vulnerable. I had no idea that this was
an issue and was very pleased that Tor let me know this.”
– (P11, F, unspecified age, write-up)
Similarly, participants found it illuminating to consult the
circuit information, which many felt was well-presented and
useful.
“One really cool tool that Tor offers is the map of where the IP
address is being rerouted — seeing that the circuit is being
bounced around back and forth to other countries.”
– (P1, M, 22, write-up)
“I loved that I was able to see the circuit that the browsing
session was being routed through and how it bounced around
different countries.” – (P5, F, 19, write-up)
Hi all!
Some of you asked me about a more formal process to reason about
implementing complex features, possibly with different teams involved.
Or just documenting new and untested ideas more formally, easier
accessible for everyone.
I added a proposals dir[1] for that, borrowing heavily from the Tor
proposal process. 001-process.txt explains what this is all about and
the first two proposals made it already in.
I think that's a good start, but we probably can fine-tune this whole
idea and process to fit more into our workflow and to our needs.
Let me know what you think and which changes we should make.
Georg
[1] https://gitweb.torproject.org/tor-browser-spec.git/tree/proposals
Hi!
Just a reminder that we won't have our weekly Tor Browser meeting on
Monday 9/24. We'll have enough meetings that week and the one after it
that we skip this one.
See you all in Mexico,
Georg
Hi everyone,
I have been discussing options for mitigating viewport-dimension
fingerprinting with the Mozilla uplift team and I came up with a
proposal for a non-letterboxing approach that might have some
advantages over letterboxing:
https://docs.google.com/document/d/1Pww4_gY59SPIK5dMxJchpevPs-MeeY5_mkxAKZd…
Maybe this is something we can discuss in Mexico City. I'd be
interested to hear your thoughts.
Thanks,
Arthur
Hi!
I created a pad where we can share ideas for the State of the Onion
talks during our dev meeting:
https://pad.riseup.net/p/G6ToSghBgWhG
I added an idea and some steps how to get there. I am happy if we want
to focus on something else instead.
Georg