From: Andi Kleen <andi@firstfloor.org>
To: Mark Smith <lnx-netdev@95022607b6285f9c5d5ea31ea9d8a7ac.nosense.org>
Cc: netdev@vger.kernel.org
Subject: Re: [RFC, PATCH 2.6.29.2] Ethernet V2.0 Configuration Testing Protocol, revision 20090428
Date: Mon, 04 May 2009 11:29:55 +0200 [thread overview]
Message-ID: <87tz41gqr0.fsf@basil.nowhere.org> (raw)
In-Reply-To: <20090428220143.31395c24.lnx-netdev@95022607b6285f9c5d5ea31ea9d8a7ac.nosense.org> (Mark Smith's message of "Tue, 28 Apr 2009 22:01:43 +0930")
Mark Smith <lnx-netdev@95022607b6285f9c5d5ea31ea9d8a7ac.nosense.org> writes:
> +
> +4. Security
> +
> +ECTP was designed in the early 1980s, when protocol security was less of
> +a concern than it is now. Consequently, there are some features of the
> +protocol which could be abused for nefarious purposes. By default, this
> +implementation attempts to avoid participating in them. These features
> +could be useful for some test cases thought, so they can be enabled if
> +required.
I think security would need quite a bit more discussion. Opening new
DOS this way sounds quite worrying, especially since this is a
extremly obscure protocol that likely most admins don't know much
about.
Is this suspencible to ping to broadcast flood replication for example?
Safest would probably be default to off.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
next prev parent reply other threads:[~2009-05-04 9:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-28 12:31 [RFC, PATCH 2.6.29.2] Ethernet V2.0 Configuration Testing Protocol, revision 20090428 Mark Smith
2009-04-28 23:15 ` Stephen Hemminger
2009-04-29 11:34 ` Mark Smith
2009-04-29 18:57 ` Stephen Hemminger
2009-04-29 21:29 ` Mark Smith
2009-04-29 21:35 ` David Miller
2009-04-30 9:36 ` Mark Smith
2009-04-30 9:42 ` David Miller
2009-04-30 10:39 ` Mark Smith
2009-04-30 11:03 ` David Miller
2009-05-04 9:29 ` Andi Kleen [this message]
2009-05-05 7:51 ` Mark Smith
-- strict thread matches above, loose matches on Subject: below --
2009-04-30 11:16 Mark ZZZ Smith
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=87tz41gqr0.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=lnx-netdev@95022607b6285f9c5d5ea31ea9d8a7ac.nosense.org \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).