Newsgroup: it.comp.aiuto
Titolo: Problemi con TOR (android)

Ho scaricato, sul mio tablet android,TOR ultima versione ma da problemi, 
posto il log nella speranza che qualcuno sia in grado di aiutarmi.
 
[CODE]
- Set background service to FOREGROUND
- aggiornamento impostazioni nel servizio Tor
- updating torrc custom configuration...
- success.
- checking binary version: 0.3.5.8-rc-openssl1.0.2p
- Orbot è in esecuzione...
- Connecting to control port: 36440
- 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%: Connecting to directory server
- Avvio client Tor... completa.
- NOTICE: Bootstrapped 10%: Finishing handshake with directory server
- NOTICE: Bootstrapped 15%: Establishing an encrypted directory connection
- NOTICE: Bootstrapped 20%: Asking for networkstatus consensus
- Circuit (1) BUILT: C37BC191AC389179674578C3E6944E925FE186C2
- NOTICE: Bootstrapped 25%: Loading networkstatus consensus
- NOTICE: I learned some more directory information, but not enough to 
build a circuit: We have no usable consensus.
- NOTICE: Bootstrapped 40%: Loading authority key certs
- WARN: Our clock is 5 hours, 28 minutes behind the time published in 
the consensus network status document (2019-09-15 15:00:00 UTC). Tor 
needs an accurate clock to work correctly. Please check your time and 
date settings!
- WARN: Received microdesc flavor consensus with skewed time 
(CONSENSUS): It seems that our clock is behind by 5 hours, 28 minutes, 
or that theirs is ahead. Tor requires an accurate clock to work: please 
check your time, timezone, and date settings.
- WARN: Problem bootstrapping. Stuck at 40%: Loading authority key 
certs. (Clock skew -19700 in microdesc flavor consensus from CONSENSUS; 
CLOCK_SKEW; count 1; recommendation warn; host ? at ?)
- NOTICE: I learned some more directory information, but not enough to 
build a circuit: We have no recent usable consensus.
- Circuit (2) BUILT: niftypedetidae
- NOTICE: I learned some more directory information, but not enough to 
build a circuit: We have no recent usable consensus.
- NOTICE: Application request when we haven't used client functionality 
lately. Optimistically trying directory fetches again.
- NOTICE: Application request when we haven't used client functionality 
lately. Optimistically trying directory fetches again.
- NOTICE: Application request when we haven't used client functionality 
lately. Optimistically trying directory fetches again.
- NOTICE: Application request when we haven't used client functionality 
lately. Optimistically trying directory fetches again.
- NOTICE: Application request when we haven't used client functionality 
lately. Optimistically trying directory fetches again.
- WARN: Received NETINFO cell with skewed time (OR:
128.31.0.34:9101
): It 
seems that our clock is behind by 6 hours, 0 minutes, or that theirs is 
ahead. Tor requires an accurate clock to work: please check your time, 
timezone, and date settings.
- WARN: Problem bootstrapping. Stuck at 40%: Loading authority key 
certs. (Clock skew -21618 in NETINFO cell from OR; CLOCK_SKEW; count 3; 
recommendation warn; host 9695DFC35FFEB861329B9F1AB04C46397020CE31 at 
128.31.0.34:9101
)
- WARN: 1 connections have failed:
- WARN: 1 connections died in state handshaking (Tor, v3 handshake) with 
SSL state SSL negotiation finished successfully in OPEN
- Circuit (4) BUILT: moria1
- WARN: Received directory with skewed time (DIRSERV:
128.31.0.34:9101
): 
It seems that our clock is behind by 6 hours, 0 minutes, or that theirs 
is ahead. Tor requires an accurate clock to work: please check your 
time, timezone, and date settings.
- WARN: Problem bootstrapping. Stuck at 40%: Loading authority key 
certs. (Clock skew -21618 in directory from DIRSERV; CLOCK_SKEW; count 
4; recommendation warn; host ? at 
128.31.0.34:9101
)
- WARN: 1 connections have failed:
- WARN: 1 connections died in state handshaking (Tor, v3 handshake) with 
SSL state SSL negotiation finished successfully in OPEN
- Circuit (1) CLOSED: xzdsb
- WARN: Received NETINFO cell with skewed time (OR:
86.59.21.38:443
): It 
seems that our clock is behind by 6 hours, 0 minutes, or that theirs is 
ahead. Tor requires an accurate clock to work: please check your time, 
timezone, and date settings.
- WARN: Problem bootstrapping. Stuck at 40%: Loading authority key 
certs. (Clock skew -21617 in NETINFO cell from OR; CLOCK_SKEW; count 6; 
recommendation warn; host 847B1F850344D7876491A54892F904934E4EB85D at 
86.59.21.38:443
)
- WARN: 2 connections have failed:
- WARN: 1 connections died in state handshaking (Tor, v3 handshake) with 
SSL state SSL negotiation finished successfully in OPEN
- WARN: 1 connections died in state connect()ing with SSL state (No SSL 
object)
- Circuit (7) BUILT: tor26
- WARN: Received directory with skewed time (DIRSERV:
86.59.21.38:443
): 
It seems that our clock is behind by 6 hours, 0 minutes, or that theirs 
is ahead. Tor requires an accurate clock to work: please check your 
time, timezone, and date settings.
- WARN: Problem bootstrapping. Stuck at 40%: Loading authority key 
certs. (Clock skew -21617 in directory from DIRSERV; CLOCK_SKEW; count 
7; recommendation warn; host ? at 
86.59.21.38:443
)
- WARN: 2 connections have failed:
- WARN: 1 connections died in state handshaking (Tor, v3 handshake) with 
SSL state SSL negotiation finished successfully in OPEN
- WARN: 1 connections died in state connect()ing with SSL state (No SSL 
object)
- Circuit (6) BUILT: BeastieJoy60
- Circuit (8) BUILT: Aerodynamik01
- Circuit (2) CLOSED: niftypedetidae
- WARN: Received NETINFO cell with skewed time (OR:
131.188.40.189:443
): 
It seems that our clock is behind by 6 hours, 0 minutes, or that theirs 
is ahead. Tor requires an accurate clock to work: please check your 
time, timezone, and date settings.
- WARN: Problem bootstrapping. Stuck at 40%: Loading authority key 
certs. (Clock skew -21618 in NETINFO cell from OR; CLOCK_SKEW; count 9; 
recommendation warn; host F2044413DAC2E02E3D6BCF4735A19BCA1DE97281 at 
131.188.40.189:443
)
- WARN: 3 connections have failed:
- WARN: 2 connections died in state connect()ing with SSL state (No SSL 
object)
- WARN: 1 connections died in state handshaking (Tor, v3 handshake) with 
SSL state SSL negotiation finished successfully in OPEN
- Circuit (10) BUILT: gabelmoo
- WARN: Received directory with skewed time 
(DIRSERV:
131.188.40.189:443
): It seems that our clock is behind by 6 
hours, 0 minutes, or that theirs is ahead. Tor requires an accurate 
clock to work: please check your time, timezone, and date settings.
- WARN: Problem bootstrapping. Stuck at 40%: Loading authority key 
certs. (Clock skew -21618 in directory from DIRSERV; CLOCK_SKEW; count 
10; recommendation warn; host ? at 
131.188.40.189:443
)
- WARN: 3 connections have failed:
- WARN: 2 connections died in state connect()ing with SSL state (No SSL 
object)
- WARN: 1 connections died in state handshaking (Tor, v3 handshake) with 
SSL state SSL negotiation finished successfully in OPEN
[/CODE]
 
In caso dove chiedere aiuto? Grazie.

posto il log nella speranza che qualcuno sia in grado di aiutarmi.
 
Dice che hai l'orologio sballato ma non so se sia la causa.