Custom Query (25390 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (106 - 108 of 25390)

Ticket Resolution Summary Owner Reporter
#33079 not a bug Disable dom.battery.enabled and dom.event.clipboardevents.enabled in about:config tbb-team morar
Description

In about:config of TorBrowser 9.0.4

dom.battery.enabled = true
dom.event.clipboardevents.enabled = true

To avoid fingerprinting (and for privacy), why not disable them?

dom.battery.enabled = false
dom.event.clipboardevents.enabled = false
#33075 fixed Travis: Remove stem from the list of allow_failure jobs teor teor
Description

It looks like make test-stem is working now. So let's make sure we see any failures.

#33074 not a bug tor opens multiple ports if `ExtORPort auto` is used multiple times; only uses one of them dcf
Description

Create a file logenv and make it executable:

#!/bin/sh
env >> env.txt

Run tor with this torrc:

SocksPort 0
ORPort auto
BridgeRelay 1
PublishServerDescriptor 0

ServerTransportPlugin logenv exec ./logenv

ExtORPort auto
ExtORPort auto
ExtORPort auto
ExtORPort auto
ExtORPort auto

The 5 instances of ExtORPort auto cause tor to open 5 separate ports:

Jan 28 02:13:57.497 [notice] Opening Extended OR listener on 127.0.0.1:0
Jan 28 02:13:57.497 [notice] Extended OR listener listening on port 45725.
Jan 28 02:13:57.497 [notice] Opened Extended OR listener on 127.0.0.1:0
Jan 28 02:13:57.497 [notice] Opening Extended OR listener on 127.0.0.1:0
Jan 28 02:13:57.497 [notice] Extended OR listener listening on port 38173.
Jan 28 02:13:57.497 [notice] Opened Extended OR listener on 127.0.0.1:0
Jan 28 02:13:57.497 [notice] Opening Extended OR listener on 127.0.0.1:0
Jan 28 02:13:57.497 [notice] Extended OR listener listening on port 34313.
Jan 28 02:13:57.497 [notice] Opened Extended OR listener on 127.0.0.1:0
Jan 28 02:13:57.497 [notice] Opening Extended OR listener on 127.0.0.1:0
Jan 28 02:13:57.498 [notice] Extended OR listener listening on port 44593.
Jan 28 02:13:57.498 [notice] Opened Extended OR listener on 127.0.0.1:0
Jan 28 02:13:57.498 [notice] Opening Extended OR listener on 127.0.0.1:0
Jan 28 02:13:57.498 [notice] Extended OR listener listening on port 40255.
Jan 28 02:13:57.498 [notice] Opened Extended OR listener on 127.0.0.1:0

Only one of them (the first one logged) is actually given to the pluggable transport:

$ grep ^TOR_PT_EXTENDED_SERVER_PORT env.txt 
TOR_PT_EXTENDED_SERVER_PORT=127.0.0.1:45725

I expected that tor would report an error if ExtORPort were used more than once, or perhaps deduplicate multiple identical ExtORPort lines.

Note: See TracQuery for help on using queries.