public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Daniel da Veiga" <danieldaveiga@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Protecting my server against an individual
Date: Thu, 6 Jul 2006 11:39:21 -0300	[thread overview]
Message-ID: <342e1090607060739k731d9e5flce698b52cc0b9e9a@mail.gmail.com> (raw)
In-Reply-To: <e5a3e9ac0607060007n683fc7afg8f77a73e79db09a6@mail.gmail.com>

On 7/6/06, Lord Sauron <lordsauronthegreat@gmail.com> wrote:
> On 7/5/06, Ryan Tandy <tarpman@gmail.com> wrote:
> > Steven Susbauer wrote:
> > >
> > > On Wed, 5 Jul 2006, Ryan Tandy wrote:
> > >
> > >> Lord Sauron wrote:
> > >>> If you can, what I'd do is try and get the guy's MAC Address or
> > >>> something and then totally block that off.  That's send him away right
> > >>> quickly.  I don't know enough to know if that'd be totally possible,
> > >>> but if the guy isn't terribly intelligent, that'll send him packing.
> > >> net-analyzer/macchanger ;)
> > >>
> > >
> > > What's this? Portage on Windows?
> >
> > More just to mention that there is such a thing out there.  And if it
> > exists for us, chances are he has a similar tool available.
>
> However, if you block his mac without an error message, then he can't
> know how you're identifying him to block him.  He probably won't know
> what to do, and just might give up then.  Worth a try, if nothing
> else.
>

Yeah, that's pretty much true. For a LAN. Doying it at the Internet
would most probably blacklist a entire subnet that's routed to you
with that MAC. So, not worth a try, it would be something more to
configure, and get you no benefit at all, while risking making your
machine invisible for people who could use the services you are trying
to securely provide.

-- 
Daniel da Veiga
Computer Operator - RS - Brazil
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GCM/IT/P/O d-? s:- a? C++$ UBLA++ P+ L++ E--- W+++$ N o+ K- w O M- V-
PS PE Y PGP- t+ 5 X+++ R+* tv b+ DI+++ D+ G+ e h+ r+ y++
------END GEEK CODE BLOCK------
-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2006-07-06 14:46 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 [this message]
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=342e1090607060739k731d9e5flce698b52cc0b9e9a@mail.gmail.com \
    --to=danieldaveiga@gmail.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