Currently tor traffic uses an TLS handshake hostname like the following:
$ sudo tcpdump -An "tcp" | grep "www"
listening on pktap, link-type PKTAP (Apple DLT_PKTAP), capture size 262144 bytes
.".
...www.odezz26nvv7jeqz1xghzs.com..#.!...www.bxbko3qi7vacgwyk4ggulh.com
Highlights
- Tor 0.3.4.8 / OpenSSL 1.0.2p with dirauth module disabled (not used
for client devices)
- Updated Obfs4/Meek pluggable transport support and built-in bridges
- Simplified (less memory, network & battery intensive) notification
with "New Identity" button
APKs up here:
https://github.c
Hello all,
I have some confusion regarding the characterization of Tor traffic using
DPI.
I was following the link (
https://trac.torproject.org/projects/tor/wiki/org/projects/Tor/TLSHistory )
and understood that Tor did TLS renogotiation at some point and then
discontinued doing it.
As an improve
Rusty Bird:
> Georg Koppen:
>> FYI: the proposal is now the first Tor Browser proposal:
>> https://gitweb.torproject.org/tor-browser-spec.git/tree/proposals/100-onion-location-header.txt
>
> Sounds great. One nit:
>
> | Website operators should be aware that tools like tordnsel have
> | false pos