Allow port 113? / IRC question
Hello Should I allow packets coming into my port 113? auth113/tcp authentication tap ident When doing ftp and also irc, I get packets onto that port. So, should I allow them to enter or is it unsafe to do so? Or is the better solution to REJECT those packets explicitly? (I currently DENY all by default.) Bitchx / IRC doesn't seem to function without auth working properly...? What - ports, etc. - do I need to enable for me to be able to do irc with 'bitchx'? I've not used bitchx before, so I'm a newbie in that respect. Any other things I should know? Regards Sven -- The best way to escape from a problem is to solve it.
Re: Allow port 113? / IRC question
Should I allow packets coming into my port 113? there was a big discussion about this about half a year ago. maybe you want to look at the archives. i reject these packets and it works. if some server denies you access because of this, you may run some fake ident server - i don't know, if there is something like that around. regards -- Hi! I'm a .signature virus! Copy me into your ~/.signature, please! -- Real programmers don't comment their code. It was hard to write, it should be hard to understand. -- Become part of the world's biggest computer cluster - join http://www.distributed.net/
Re: Allow port 113? / IRC question
On 23-Sep-2000 Oswald Buddenhagen wrote: Should I allow packets coming into my port 113? there was a big discussion about this about half a year ago. maybe you want to look at the archives. i reject these packets and it works. if some server denies you access because of this, you may run some fake ident server - i don't know, if there is something like that around. There is oidentd: Description: Replacement ident daemon An ident (rfc1413) daemon for Linux. Oidentd supports most features of pidentd as well as a number of features absent in pidentd. Most notably, oidentd allows users, given the proper permission, to specify the identd response that the server will output when a successful lookup is completed. Oidentd also allows for pseudo-random strings (either a prefix, such as user, followed by a number between 0 and 9, or 10 pseudo-random characters of the set 0-9A-Za-z) to be returned upon the completion of a successful lookup instead of a username or a UID. . Oidentd now supports IP masqueraded connections, including netfilter.
