public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: James <wireless@tampabay.rr.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user]  Re: Protecting my server against an individual
Date: Wed, 5 Jul 2006 03:37:45 +0000 (UTC)	[thread overview]
Message-ID: <loom.20060705T053505-613@post.gmane.org> (raw)
In-Reply-To: 49bf44f10607041738w2ce28c5bq9d569ffc47d44848@mail.gmail.com

Grant <emailgrant <at> gmail.com> writes:

> 
> > > 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?
> >
> > I assuming your server is a web host and it only is using port 80 (http)
traffic.
> 
> I do log in via ssh (port 22 I think) and it's also a mail server.
> How can I check which ports are open?  Does shorewall handle that?


You may want to try a tool I just found:


kmyfirewall:

et-firewall/kmyfirewall
     Available versions:  0.9.6.2-r1 ~1.0-r2 ~1.0.1
     Installed:           0.9.6.2-r1
     Homepage:            http://kmyfirewall.sourceforge.net/
     Description:         Graphical KDE iptables configuration tool

I just installed it, so I'm going to play around with it. In the handbook you 
can use the advanced features to config a firewall
for a remote system.....

ymmv,


James




I 

-- 
gentoo-user@gentoo.org mailing list



  parent reply	other threads:[~2006-07-05  4:05 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 [this message]
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 ` [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=loom.20060705T053505-613@post.gmane.org \
    --to=wireless@tampabay.rr.com \
    --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