I noticed TBB-2.3.25-1 is using 'cached-microdescs' which removes the
end-user's ability to choose exitnodes based on each server's exit
policy.
example of informations in obsolete 'cached-descriptors':
router name and IP address
platform
uptime
bandwidth
reject *:25
reject *:119
reject *:135-13
On 12/12/12 3:23 PM, basmati kasaar wrote:
> I noticed TBB-2.3.25-1 is using 'cached-microdescs' which removes the
> end-user's ability to choose exitnodes based on each server's exit
> policy.
>
> example of informations in obsolete 'cached-descriptors':
>
> router name and IP address
> platform
>- Original Message -
>From: Karsten Loesing
>To: basmati kasaar
>Cc: tor-talk@lists.torproject.org
>Sent: Wed, 12 Dec 2012 20:22:43 +0530 (IST)
>Subject: Re: [tor-talk] 'cached-descriptors' replaced with 'cached-microdescs'
>
>
>
>Yes, see https://atlas.torproject.org/
>
>Best,
>Karsten
On 12/12/12 7:09 PM, basmati kasaar wrote:
> 'atlas.torproject.org' appears to contain very, very little useful
> informations and no informations on specific exit port availability
> per router.
Actually, it does have full exit policies of all relays. Try typing a
relay nickname or fingerprint i
On Wed, Dec 12, 2012 at 4:23 PM, basmati kasaar wrote:
> Is this informations still available somewhere else? Maybe a torproject.org
> URL?
UseMicrodescriptors 0?
--
Maxim Kammerer
Liberté Linux: http://dee.su/liberte
___
tor-talk mailing list
tor-ta
On Wed, 12 Dec 2012 23:39:38 +0530 (IST)
basmati kasaar wrote:
> 'atlas.torproject.org' appears to contain very, very little useful
> informations and no informations on specific exit port availability
> per router.
The full exit policy is on atlas, here's a current exit relay:
https://atlas.to
If you use the cached-consensus then why not just set
'FetchUselessDescriptors 1' in your torrc?
___
tor-talk mailing list
tor-talk@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk
Good evening torrizens,
I have been looking through the relay descriptors for signs of
malicious exit policy configurations and have found that the Tor network
appears to be infested by a sniffer plague.
No worries, though, a friendly Torrorist is here to help.
Thanks to the attached mineral