Custom Query (25389 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (124 - 126 of 25389)

Ticket Resolution Summary Owner Reporter
#33026 duplicate Problem using obfs4 on Android arm64: executable's TLS segment is underaligned tbb-team uhdv
Description

Hi,

I can't connect with latest Android Tor Browser

Without hidden relay it's like that :

- updating settings in Tor service
- updating torrc custom configuration...
- success.
- checking binary version: 0.4.1.5-rc-openssl1.0.2p
- Orbot is starting…
- Connecting to control port: 37805
- SUCCESS connected to Tor control port.
- SUCCESS - authenticated tor control port.
- Took ownership of tor control port.
- adding control port event handler
- SUCCESS added control port event handler
- NOTICE: Opening Socks listener on 127.0.0.1:9150 
- NOTICE: Opened Socks listener on 127.0.0.1:9150 
- NOTICE: Opening DNS listener on 127.0.0.1:5400 
- NOTICE: Opened DNS listener on 127.0.0.1:5400 
- NOTICE: Opening Transparent pf/netfilter listener on 127.0.0.1:9140 
- NOTICE: Opened Transparent pf/netfilter listener on 127.0.0.1:9140 
- NOTICE: Opening HTTP tunnel listener on 127.0.0.1:8218 
- NOTICE: Opened HTTP tunnel listener on 127.0.0.1:8218 
- NOTICE: Bootstrapped 5% (conn): Connecting to a relay 
- Starting Tor client… complete.
- NOTICE: Bootstrapped 10% (conn_done): Connected to a relay 

And with obfs4 hidden relay it's like that :

- TorService is shutting down
- Using control port to shutdown Tor
- NOTICE: Closing no-longer-configured HTTP tunnel listener on 127.0.0.1:8218 
- NOTICE: Closing no-longer-configured Socks listener on 127.0.0.1:9150 
- NOTICE: Closing no-longer-configured DNS listener on 127.0.0.1:5400 
- NOTICE: Closing no-longer-configured Transparent pf/netfilter listener on 127.0.0.1:9140 
- NOTICE: DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 
- NOTICE: Delaying directory fetches: DisableNetwork is set. 
- sending HALT signal to Tor process
- Orbot is deactivated
- updating settings in Tor service
- updating torrc custom configuration...
- success.
- checking binary version: 0.4.1.5-rc-openssl1.0.2p
- Orbot is starting…
- Connecting to control port: 42415
- SUCCESS connected to Tor control port.
- SUCCESS - authenticated tor control port.
- Took ownership of tor control port.
- adding control port event handler
- SUCCESS added control port event handler
- NOTICE: Opening Socks listener on 127.0.0.1:9150 
- NOTICE: Opened Socks listener on 127.0.0.1:9150 
- NOTICE: Opening DNS listener on 127.0.0.1:5400 
- NOTICE: Opened DNS listener on 127.0.0.1:5400 
- NOTICE: Opening Transparent pf/netfilter listener on 127.0.0.1:9140 
- NOTICE: Opened Transparent pf/netfilter listener on 127.0.0.1:9140 
- NOTICE: Opening HTTP tunnel listener on 127.0.0.1:8218 
- NOTICE: Opened HTTP tunnel listener on 127.0.0.1:8218 
- Starting Tor client… complete.
- WARN: Managed proxy at '/data/app/org.torproject.torbrowser-muJdMAge2O52aHgePxNzIw==/lib/arm64/libObfs4proxy.so' reported: error: "/data/app/org.torproject.torbrowser-muJdMAge2O52aHgePxNzIw==/lib/arm64/libObfs4proxy.so": executable's TLS segment is underaligned: alignment is 8, needs to be at least 64 for ARM64 Bionic 
- WARN: Pluggable Transport process terminated with status code 6 
- No network connectivity. Putting Tor to sleep…
- NOTICE: Closing no-longer-configured HTTP tunnel listener on 127.0.0.1:8218 
- NOTICE: Closing no-longer-configured Socks listener on 127.0.0.1:9150 
- NOTICE: Closing no-longer-configured DNS listener on 127.0.0.1:5400 
- NOTICE: Closing no-longer-configured Transparent pf/netfilter listener on 127.0.0.1:9140 
- NOTICE: DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 
- Network connectivity is good. Waking Tor up…
- NOTICE: Opening Socks listener on 127.0.0.1:9150 
- NOTICE: Opened Socks listener on 127.0.0.1:9150 
- NOTICE: Opening DNS listener on 127.0.0.1:5400 
- NOTICE: Opened DNS listener on 127.0.0.1:5400 
- NOTICE: Opening Transparent pf/netfilter listener on 127.0.0.1:9140 
- NOTICE: Opened Transparent pf/netfilter listener on 127.0.0.1:9140 
- NOTICE: Opening HTTP tunnel listener on 127.0.0.1:8218 
- NOTICE: Opened HTTP tunnel listener on 127.0.0.1:8218 
- WARN: Managed proxy at '/data/app/org.torproject.torbrowser-muJdMAge2O52aHgePxNzIw==/lib/arm64/libObfs4proxy.so' reported: error: "/data/app/org.torproject.torbrowser-muJdMAge2O52aHgePxNzIw==/lib/arm64/libObfs4proxy.so": executable's TLS segment is underaligned: alignment is 8, needs to be at least 64 for ARM64 Bionic  
- WARN: Pluggable Transport process terminated with status code 6 
#33025 invalid Link error on the documentation page Hosebarero
Description

https://2019.www.torproject.org/docs/documentation.html.en

read the list of warnings > https://2019.www.torproject.org/download/download.html.en#Warning

This link does not lead to the help page, but to the software download.

#33023 fixed Chutney 'bootstrap-network.sh' starts a different default network flavor than listed in the usage comments opara
Description

Small documentation problem in Chutney's bootstrap-network.sh.

The usage comment says the following:

# Usage:
#    tools/bootstrap-network.sh [network-flavour]
#    network-flavour: one of the files in the networks directory,
#                     (default: 'basic')

but the actual code says the following:

# Set the variables for the chutney network flavour
export NETWORK_FLAVOUR=${NETWORK_FLAVOUR:-"bridges+hs-v2"}
[ -n "$1" ] && { NETWORK_FLAVOUR=$1; shift; }
export CHUTNEY_NETWORK="$CHUTNEY_PATH/networks/$NETWORK_FLAVOUR"

As you can see, the comments say that the default network is 'basic', but the code actually starts 'bridges+hs-v2'. Reference: https://github.com/torproject/chutney/blob/5a9271104fec6c5b9bb23d2574596dc9d7c0a2c4/tools/bootstrap-network.sh

Note: See TracQuery for help on using queries.