[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: RFD: authentication/access control



On Fri, Jun 12, 1998 at 12:07:15PM -0400, Christophe Kalt wrote:
>I've been thinking about this for a while, and need some
>feedback on it before I think more about it.
>
>currently, ircd supports
>
>o 2 methods for authentication: DNS (for the hostname) and
>  identd (for the username).
>o 2 methods for access control: K (very flexible, but works
>  based on user@host only), and R lines (better, but
>  blocking!).
>
>I'm interested in hearing from people who would need other
>authentication mechanisms (what is it? public?  homebrewed?
>..) In particular, I'd like to hear from people currently
>using R lines.

I know webbernet uses R lines to check for open SOCKS servers on connecting
clients. (at least, i know they check for that. i got an attempt to access
port 1080 on my box, and checked out what they do with SOCKS).
This seems a more-or-less nice idea, but i guess it does alot of trouble
if it blocks the server (especially with firewalls who block access to port
1080 in dropping the packet).
	-forcer

-- 
/* Linux: the operating system with a CLUE. Command Line User Environment */
/* email: forcer@xxxxxxxxxxxxxxxxx -><- www: http://webserver.de/forcer/  */
/* IRC: forcer (#StarWars@IRCnet)  -><- PlonkCount: 3                     */