From: Christopher Dale <chrisd@ucmd.zapto.org>
To: gentoo-server@lists.gentoo.org
Subject: Re: [gentoo-server] how to stop tracing
Date: Wed, 16 Jan 2008 15:26:12 -0600 [thread overview]
Message-ID: <478E7674.4020401@ucmd.zapto.org> (raw)
In-Reply-To: <cb9528810801160436i24a516e8ke29ec1cdb8bfbf86@mail.gmail.com>
widyachacra wrote:
> Dear List friends,
>
> When i scan my own domain from an out side host using 'nmap' tool it shows
> following results. How do i block this kind of tracing using linux. Please
> help me.
>
> nmap tracing result,
>
> PORT STATE SERVICE VERSION
> 25/tcp open smtp netqmail smtpd 1.04
> 53/tcp open domain
> 80/tcp open http Apache httpd 2.2.6 ((Gentoo))
> 110/tcp open pop3 Courier pop3d
> 119/tcp open ssh OpenSSH 4.7 (protocol 2.0)
> 209/tcp open tam?
> 443/tcp open http Apache httpd 2.2.6 ((Gentoo))
> 628/tcp open tcpwrapped
> 993/tcp open ssl/imap Courier Imapd (released 2005)
> 995/tcp open ssl/pop3 Courier pop3d
>
>
>
Hi Widyachacra,
Great question and one that I have had in the past also. In a previous
post to the gentoo mailing list, someone suggested that port knocking be
used as a means of securing through obscurity. After looking at it
(http://www.portknocking.org), I've found that it's a wonderful means to
a personal server's security when exposed to the world wide web.
All the best in your attempts to obfuscate your server's open ports! :)
Chrelad
--
gentoo-server@lists.gentoo.org mailing list
next prev parent reply other threads:[~2008-01-16 21:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-16 12:36 [gentoo-server] how to stop tracing widyachacra
2008-01-16 12:44 ` Andrew Gaffney
2008-01-16 18:41 ` Lindsay Haisley
2008-01-16 21:26 ` Christopher Dale [this message]
2008-01-16 21:52 ` Andrew Gaffney
2008-01-16 22:00 ` Mark Rudholm
2008-01-16 22:04 ` RijilV
2008-01-17 21:48 ` A. Khattri
-- strict thread matches above, loose matches on Subject: below --
2008-01-16 20:05 Tom Grace
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=478E7674.4020401@ucmd.zapto.org \
--to=chrisd@ucmd.zapto.org \
--cc=gentoo-server@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox