[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] Re: What ports shouldnt be closed
- Subject: Re: [cobalt-users] Re: What ports shouldnt be closed
- From: "E.B. Dreger" <eddy+public+spam@xxxxxxxxxxxxxxxxx>
- Date: Thu Feb 6 10:30:31 2003
- List-id: Mailing list for users to share thoughts on Sun Cobalt products. <cobalt-users.list.cobalt.com>
BT> Date: Thu, 6 Feb 2003 09:34:09 -0800
BT> From: Bruce Timberlake
BT> ssh = 22 (should be used instead of telnet if at all possible)
Definitely. However, upgrading SSH becomes an issue... one must
re-enable telnet (ick) or run SSH on another port (what I
recommend). If using the latter, select a port that isn't
commonly used; i.e., if the machine is compromised, you don't
want it listening on the "standard" botnet ports.
FTP presents another set of problems that I'll detail in a
separate message.
Eddy
--
Brotsman & Dreger, Inc. - EverQuick Internet Division
Bandwidth, consulting, e-commerce, hosting, and network building
Phone: +1 (785) 865-5885 Lawrence and [inter]national
Phone: +1 (316) 794-8922 Wichita
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Date: Mon, 21 May 2001 11:23:58 +0000 (GMT)
From: A Trap <blacklist@xxxxxxxxx>
To: blacklist@xxxxxxxxx
Subject: Please ignore this portion of my mail signature.
These last few lines are a trap for address-harvesting spambots.
Do NOT send mail to <blacklist@xxxxxxxxx>, or you are likely to
be blocked.