full-disclosure - Re: Solaris telnet vulnerability

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20070213205328.8BFD811065@kris.7deadly.org>
Date: Tue, 13 Feb 2007 15:53:28 -0500
From: Graham Reed <greed@...ox.com>
To: full-disclosure@...ts.grok.org.uk
Subject: Re: Solaris telnet vulnerability - how many on
 your network?

Brad_Powell@...t.com writes:
> Of course disabling in.telnetd in /etc/inetd.conf (and doing a pkill -HUP 
> inetd) if possible is a safe bet,

Or, going with Solaris 10's 'SMF' thing: 

% svcadm disable svc:/network/telnet 

And, while you're at it, 

% svcadm disable svc:/network/shell:default
% svcadm disable svc:/network/login:rlogin 

(See man pages for in.telnetd, in.rshd, and in.rlogind.) 

At least one machine I run doesn't have the usual /etc/inetd.conf. 

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/