From: Paul Klos <gentoo@klos2day.nl>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] pam_get_uid: no such user
Date: Thu, 14 Feb 2013 17:51:05 +0100 [thread overview]
Message-ID: <2982193.qFHaFKoIpo@apollo> (raw)
In-Reply-To: <E84EC1E4-A610-4387-A1CD-8CA7CECA369E@stellar.eclipse.co.uk>
Op donderdag 14 februari 2013 04:56:53 schreef Stroller:
>
> On 14 February 2013, at 04:13, Daniel Frey wrote:
> > ...
> > I've poked into this a bit more, and every 60 seconds 5 attempts at
> > logon are being made… This weekend I'll reformat & reinstall.
>
> Excuse me if this is a dumb question, but does this machine have any ports open to the internet?
>
> This thread reminds me of how we sometimes hear of logfiles full of many ssh attempts made by script kiddies and botnets.
>
> Stroller.
>
>
Same here, I've seen multitudes of messages like this, with different user names, in log files on servers with open ports 22. As long as you don't allow interactive logins you shoud be fine, right?
I think there might also be some advanced iptables hacking that might help you block too many requests from the same source IP. This is still on my list of stuff to look at 'some time'.
One thing I have used with apparent succes is access a different port on the outside, and redirect that to 22 on the inside. It's security through obscurity, I know, but it seemed quite effective nonetheless.
Cheers,
Paul
next prev parent reply other threads:[~2013-02-14 16:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-13 19:29 [gentoo-user] pam_get_uid: no such user Daniel Frey
2013-02-13 22:51 ` [gentoo-user] " walt
2013-02-14 3:25 ` Daniel Frey
2013-02-14 4:13 ` Daniel Frey
2013-02-14 4:56 ` [gentoo-user] " Stroller
2013-02-14 16:51 ` Paul Klos [this message]
2013-02-14 17:27 ` Alan McKinnon
2013-02-14 19:54 ` Daniel Frey
2013-02-15 0:15 ` Adam Carter
2013-02-15 6:44 ` Daniel Frey
2013-02-15 16:46 ` Daniel Frey
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=2982193.qFHaFKoIpo@apollo \
--to=gentoo@klos2day.nl \
--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