Can someone see any security problems at http://64.192.99.49 if so what can I do about them? Thanks, Brandon Caudle -------------- 15yr Old Avid Unix User (HP-UX,FreeBSD,Linux) Larkhaven Golf Course Charlotte, NC "There cannot be a crisis next week. My schedule is already full." -- Henry Kissinger
Can someone see any security problems at http://64.192.99.49 if so what can I do about them? Thanks, Brandon Caudle -------------- 15yr Old Avid Unix User (HP-UX,FreeBSD,Linux) Larkhaven Golf Course Charlotte, NC ---- Here's what I got using nmap -sT 21/tcp open ftp 22/tcp open ssh 23/tcp open telnet 25/tcp open smtp 37/tcp open time 53/tcp open domain 79/tcp open finger 80/tcp open http 110/tcp open pop-3 111/tcp open sunrpc 113/tcp open auth 139/tcp open netbios-ssn 143/tcp open imap2 513/tcp open login 631/tcp open unknown 636/tcp open ldapssl 901/tcp open samba-swat 2401/tcp open cvspserver 3306/tcp open mysql 5800/tcp open vnc 6000/tcp open X11 ---- I don't know what this really means, but I would guess that there are ample places to start poking around. in /etc/inetd.conf you can shutter up at least telnet and finger.
On Thu, Sep 06, 2001 at 05:45:55AM -0400, Brandon Caudle wrote:
Can someone see any security problems at http://64.192.99.49 if so what can I do about them?
A nmap scan reveals that you have several ports open. You might want to consider setting up a firewall. Second, go into /etc/inetd.conf and turn off all unneeded services. Odds are good that you can turn of most if not all of them.
Brandon Caudle --------------
-v -- Victor R. Cardona 5:21pm up 13 days, 23:52, 2 users, load average: 1.14, 1.13, 1.12 Powered by SuSE Linux 7.1 (i386) 2.4.5-64GB-SMP
participants (3)
-
Brandon Caudle
-
Daniel Woodard
-
Victor R. Cardona