From: Michael Sierchio (kudzu@tenebras.com)
Date: Mon Jun 05 2006 - 12:28:34 EDT
shane@aplv.com wrote:
> I agree with Morning Wood 100% .... Running sshd on port 22 anymore in
> this day
> and age is really not a smart decision, ...
I beg to differ with you -- running a standard service on a non-standard
port is a bid for security through obscurity.
Things that might be useful:
Use auth methods that are sufficiently strong (pubkey only,
PAMified OPIE or S/Key, etc.)
Authenticated firewall traversal for protected services
Tarpit connections from bad actors
------------------------------------------------------------------------------
This List Sponsored by: Cenzic
Concerned about Web Application Security?
Why not go with the #1 solution - Cenzic, the only one to win the Analyst's
Choice Award from eWeek. As attacks through web applications continue to rise,
you need to proactively protect your applications from hackers. Cenzic has the
most comprehensive solutions to meet your application security penetration
testing and vulnerability management needs. You have an option to go with a
managed service (Cenzic ClickToSecure) or an enterprise software
(Cenzic Hailstorm). Download FREE whitepaper on how a managed service can
help you: http://www.cenzic.com/news_events/wpappsec.php
And, now for a limited time we can do a FREE audit for you to confirm your
results from other product. Contact us at request@cenzic.com for details.
------------------------------------------------------------------------------
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:56:02 EDT