[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

ExitNodes for encrypted connects only are not possible. Why?

To: or-talk@xxxxxxxxxxxxx
Subject: ExitNodes for encrypted connects only are not possible. Why?
From: Gitano <ran6oony7r9deku5@xxxxxxxxxxxxxx>
Date: Sat, 09 May 2009 11:19:04 +0200
Delivered-to: archiver@xxxxxxxx
Delivered-to: or-talk-outgoing@xxxxxxxx
Delivered-to: or-talk@xxxxxxxx
Delivery-date: Sat, 09 May 2009 05:19:08 -0400
Organization: Private
Reply-to: or-talk@xxxxxxxxxxxxx
Sender: owner-or-talk@xxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.21 (X11/20090318)

In 'git.torproject.org/checkout/tor/master/doc/spec/dir-spec.txt'
ExitNodes are defined as:

   "Exit" -- A router is called an 'Exit' iff it allows exits to at
    least two of the ports 80, 443, and 6667 and allows exits to at
    least one /8 address space.

I would like to setup my ExitNode for ports 443, 465, 563, 993, 995
(https, ssmtp, nntps, imaps, pop3s) only, but this is not possible.

What's the reason behind this? Is there any chance to loose this
restriction in one of the next releases?

Follow-Ups:
- Re: ExitNodes for encrypted connects only are not possible. Why?
  - From: Karsten Loesing

Prev by Author: Re: Privoxy change?
Next by Author: Re: ExitNodes for encrypted connects only are not possible. Why?
Previous by thread: New mirror
Next by thread: Re: ExitNodes for encrypted connects only are not possible. Why?
Index(es):
- Author
- Thread