Date: Mon, 03 Mar 2008 12:42:10 -0600 From: Tim Daneliuk <tundra@tundraware.com> To: "Grammas, August" <AG7554@att.com>, FreeBSD Mailing List <freebsd-questions@freebsd.org> Subject: Re: telnet and rlogin problems Message-ID: <47CC4682.1050806@tundraware.com> In-Reply-To: <25F153F3B4E60D448208CFCD0DDC288701A15F6E@WWDCEXCH20.US.Cingular.Net> References: <25F153F3B4E60D448208CFCD0DDC288701A15F6E@WWDCEXCH20.US.Cingular.Net>
next in thread | previous in thread | raw e-mail | index | archive | help
Grammas, August wrote: > > > Rel: FreeBSD 6.2 > > > > Summary: I am unable to get either > > telnet or rlogin to function > > > > Details: To several of my PCs, that had been running 4.11, > > I have installed release 6.2. > > > > To the rc.conf, which was used for 4.11, I added: > > > > rcpbind_enable="YES" > > rpc_lockd_enable="YES" > > rpc_statd_enable="YES" > > nfs_server_enable="YES" > > nfs_client_enable="YES" > > mountd_enable="YES" > > ftpd_enable="YES Don't believe any of these are relevant to your stated problem. > > > > To hosts.allow, I added: > > > > rpcbind | ALL | allow Again, I don't think this is relevant to your stated problem. try adding: telnetd: whatever : ALLOW Note the use of ':' - I have no idea whether the wrappers will allow you to use '|'. As a general matter, service: ALL : ALLOW is very bad if your machine is connected to the internet. You really do want your allow statements to be in the form: service: exact list of machines or networks that should be allowed :ALLOW Now then ... one last thing: DON'T USE TELENT AND RLOGIN - get out of the habit of using them even on local networks. They are painfully bad security holes. Learn to use ssh instead. HTH, -- ---------------------------------------------------------------------------- Tim Daneliuk tundra@tundraware.com PGP Key: http://www.tundraware.com/PGP/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?47CC4682.1050806>