public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alexander Skwar <listen@alexander.skwar.name>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Protecting my server against an individual
Date: Wed, 05 Jul 2006 13:02:50 +0200	[thread overview]
Message-ID: <44AB9C5A.9020504@mid.message-center.info> (raw)
In-Reply-To: <9b1675090607050223p2b5089bdx7f0abdc5dcaf28ac@mail.gmail.com>

Trenton Adams wrote:
> I would move ssh to a very high port number of your choice.  Most ssh
> port scanners do not bother checking anything other than port 22, as
> it is too time consuming.  I have not had any weird hits on my ssh
> port in years.  It was hammered daily, even with attempted logins and
> such, with it running on port 22.  Now, pretty much nothing.  Why not
> use something like 65350 or some random high port like that?

ACK. Good idea. One more thing though: I'd not use a "strange" port
like 65350, but rather a port, which might be legitimately open.
Suppose you've got a web server and DON'T use ssl. In this case,
https (443) would be available. Or if you don't have a usenet server,
you could use 119.

Reason: It's "normal" that such ports are open. If I were a
script kiddie, I wouldn't bother looking at normally open
ports. But if there's something strange like 65350, I *would*
look.

> And yes, you probably shouldn't be asking these questions if you have
> an important linux computer on the internet.  Because if it is
> important, you should know what you are doing before you put it on the
> internet.
> 
> If on the other hand, you're just getting to know linux, and the
> computer is not all that important, then you should be asking these
> questions.

Yes, he *CERTAINLY* should be asking those questions - but he
shouldn't have a server on the internet. Reason: It might be
so, that the system is less secure than it ought to be and thus
might be already part of a botnet or somesuch. And if it were
part of a botnet, it might be used to attack other systems or
to simply relay spams.

Because of that, I find it somewhat irresponsible or at the
very least questionable, when users with not so much knowledge
operate servers. And it doesn't matter if all, if the system
is important to the OP - it matters only, if it might be used
to do things, which the OP doesn't want.


Alexander Skwar
-- 
The more laws and order are made prominent, the more thieves and
robbers there will be.
		-- Lao Tsu
-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2006-07-05 11:18 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-04 22:56 [gentoo-user] Protecting my server against an individual Grant
2006-07-04 23:54 ` [gentoo-user] " James
2006-07-05  0:38   ` Grant
2006-07-05  0:51     ` Dale
2006-07-05  2:17     ` Thomas Cort
2006-07-05  3:37     ` James
2006-07-05  7:35     ` Alexander Skwar
2006-07-05  1:57 ` [gentoo-user] " Ryan Tandy
2006-07-05  7:38   ` Alexander Skwar
2006-07-05  9:23     ` Trenton Adams
2006-07-05 11:02       ` Alexander Skwar [this message]
2006-07-05 12:03         ` jarry
2006-07-05 16:38         ` Daniel da Veiga
2006-07-05 10:49     ` jarry
2006-07-05 12:45       ` W.Kenworthy
2006-07-05 16:40     ` Ryan Tandy
2006-07-05 23:31       ` Lord Sauron
2006-07-05 23:58         ` Ryan Tandy
2006-07-06  0:30           ` Steven Susbauer
2006-07-06  0:36             ` Ryan Tandy
2006-07-06  7:07               ` Lord Sauron
2006-07-06 14:39                 ` Daniel da Veiga
2006-07-07 16:46                   ` Devon Miller
2006-07-06  6:11         ` Alexander Skwar
2006-07-06  7:12           ` Lord Sauron
2006-07-06  9:12             ` Alexander Skwar
2006-07-11  7:40               ` Daevid Vincent
2006-07-05  2:35 ` Thomas Cort
2006-07-05 10:22 ` Daniel
2006-07-05 13:36 ` [gentoo-user] " dnlt0hn5ntzhbqkv51

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=44AB9C5A.9020504@mid.message-center.info \
    --to=listen@alexander.skwar.name \
    --cc=gentoo-user@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