Following up on inconsistency of spoofed TBB screen sizes, shown on test
sites:
I did more testing / checking. Then posted comments on Trac
https://trac.torproject.org/projects/tor/ticket/7256#comment:10 &
comment #11.
For me, with each browser fully maximized, there's a *fundamental
differe
On 3/6/2014 1:59 AM, Georg Koppen wrote:
Joe Btfsplk:
But, EVEN WHEN I reset my system to 96 DPI, reboot - TBB still shows a
weird value - like 1920 x *933* (just an example).
NO one has a screen size w/ those odd numbers. That's the issue.
Yes, they should be a multiple of 200 x 100. Resizin
corridor[0], a Tor traffic whitelisting gateway, usually subscribes to
NEWCONSENSUS events in a Tor control connection and converts each new
networkstatus consensus into a Linux ipset.
ipset entries can be be associated with a timeout value to make them
disappear from the set after some number of
* on the Thu, Mar 06, 2014 at 02:02:50AM -0600, Cypher wrote:
> I run the public XMPP server at chat.cpunk.us and I'd like to make the
> service also available as a hidden service. I have a few questions:
>
> 1. Let's say my hidden service is xxxcf.onion. What would the users
> final JID be?
Joe Btfsplk:
> But, EVEN WHEN I reset my system to 96 DPI, reboot - TBB still shows a
> weird value - like 1920 x *933* (just an example).
> NO one has a screen size w/ those odd numbers. That's the issue.
Yes, they should be a multiple of 200 x 100. Resizing the browser window
does currently no
I run the public XMPP server at chat.cpunk.us and I'd like to make the
service also available as a hidden service. I have a few questions:
1. Let's say my hidden service is xxxcf.onion. What would the users
final JID be? Would they still be u...@chat.cpunk.us or would the
onion address come
