All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Demenshin <aldem-nf@nospam.aldem.net>
To: netfilter@lists.netfilter.org
Subject: Re: strange log
Date: Sun, 4 May 2003 02:35:31 +0200	[thread overview]
Message-ID: <20030504023531.A22082@base.aldem.net> (raw)
In-Reply-To: <1052007023.25877.40.camel@elendil.intranet.cartel-securite.net>; from blancher@cartel-securite.fr on Sun, May 04, 2003 at 02:10:24AM +0200

On Sun, May 04, 2003 at 02:10:24AM +0200, Cedric Blancher wrote:

> DHCP is a very weak system from security point of vue, that can easily
> lead to DoS and traffic redirection.

  When you have few hundreths servers, there is no better way to
  assign/change IPs. And even without DHCP, there are a lot of ways
  for traffic redirection (ARP poisoning and so on).

> A customer server compromise could be a serious threat for other servers...

  When server is not managed, or when attacker is inside of hosting segment
  - perhaps. But when attacker is outside - there is no way to compromise
  the host through DHCP. If it is compromised by other means - DHCP is not the
  cause, so? :)
  
  Even MAC filtering is weak - modern NICs may have any MAC, it is configurable.
  
  No system is secure - unless it is plugged off and burned out. And even then...
  but this is another story :)

Regards,
/Al


  reply	other threads:[~2003-05-04  0:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-02  9:47 strange log Keith Tin
2003-05-03 23:29 ` Cedric Blancher
2003-05-03 23:45   ` Alexander Demenshin
2003-05-04  0:10     ` Cedric Blancher
2003-05-04  0:35       ` Alexander Demenshin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-04-22  6:50 Emilio Casbas

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=20030504023531.A22082@base.aldem.net \
    --to=aldem-nf@nospam.aldem.net \
    --cc=aldem-nf@aldem.net \
    --cc=netfilter@lists.netfilter.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.