Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Security-Basics
[Top] [All Lists]

Re: Leaving a door open?

Subject: Re: Leaving a door open?
Date: Fri, 27 May 2005 22:40:03 +0200
Hello,

On 5/27/05, Emmanuel Goldstein <goldstein101@gmail.com> wrote:
Hi!
[..]
Is this secure??? Note that my admin password is really hard to guess,
so im not concerned about bruteforce attacks.

Well, ssh is widely used for secure connections and bruteforce attacks
won't work on strong passwords. Anyway, logguing as root is a bad
idea, so you better log in as a normal user then, su to root.
Disabling ssh root login gives you more protection.
You can also limit the IP range that can connect to your ssh server in
your configuration firewall. You can limit the number of connexion
retries if your firewall has that featrure (iptable does).

I think that a big security hole in ssh will lead to a very big mess
on the planet ;)

Should I map ports so instead of opening 22 I access through (eg) 'ssh
-p 7623'. That way is not that obvious i have an open ssh port is, it?

well you can hide things, but there are fingerprinting techniques (try
nmap -sV -p 7623 on your localhost) that reveals the services + their
version etc..
 
Is it better to just set up an ftp server?

No, ssh is much better. Ftp is a clear text protocol !!

-- 
/boot

<Prev in Thread] Current Thread [Next in Thread>