From: dnlt0hn5ntzhbqkv51 <dnlt0hn5ntzhbqkv51@safe-mail.net>
To: gentoo-user <gentoo-user@lists.gentoo.org>
Subject: [gentoo-user] Re: Protecting my server against an individual
Date: Wed, 05 Jul 2006 09:36:02 -0400 [thread overview]
Message-ID: <op.tb7xec06lbd8ez@you.and.your.horse> (raw)
In-Reply-To: 49bf44f10607041556w3db1b64et625c088ba8c56541@mail.gmail.com
On Tue, 04 Jul 2006 18:56:02 -0400, Grant <emailgrant@gmail.com> wrote:
> It has come to my attention that a particular person I know may be
> intent on attacking my server/website in any way possible. He doesn't
> know much about Linux but does know Windows. What kind of things
> should I lock down to protect my remote hosted server? I don't have
> time to get too crazy with security right now, but what kinds of
> simple tricks might this fellow learn by asking around on forums, etc?
A Windows guy has all of the techniques/tools that a 'nix guy has - he'll
figure out what servers you have, which ports, which software, what
vulnerabilities ...... all of it. He'll even use some of the same tools
(e.g. nmap).
If your server is misconfigured (e.g allows root logon); if passwords are
trivial; if software is out-of-date with known vulnerabilities; he could
break in and deface the site; erase the OS; install a root kit and hide a
key logger.............................
Suggest that you shut this thing down 'til you have a security plan that
you understand, and with which you are comfortable.
If that is not possible, then implement the items mentioned earlier, and
additionally assure:
1. that your passwords are at least 15 characters long with capitals and
numerics. A repeated password is fine (e.g. gentoo becomes
gEnt0*gEnt0*gEnt0*)
2. that you can easily and confidently restore your backups (you do have
backups!?)
3. that you can tell if you've been hacked (e.g. samhain, tripwire).
4. And that your software is up to date.
After that, you can look into IDS, Trojan scanning, chroot jails,
hardening, and other things that servers under attack might consider.
--
gentoo-user@gentoo.org mailing list
prev parent reply other threads:[~2006-07-05 13:57 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
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 ` dnlt0hn5ntzhbqkv51 [this message]
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=op.tb7xec06lbd8ez@you.and.your.horse \
--to=dnlt0hn5ntzhbqkv51@safe-mail.net \
--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