From: David Miller <davem@davemloft.net>
To: shemminger@vyatta.com
Cc: ben@decadent.org.uk, gregkh@suse.de, netdev@vger.kernel.org,
devel@driverdev.osuosl.org, debian-kernel@lists.debian.org
Subject: Re: [PATCH 1/3] decnet: Move to staging
Date: Mon, 22 Nov 2010 21:19:23 -0800 (PST) [thread overview]
Message-ID: <20101122.211923.193717252.davem@davemloft.net> (raw)
In-Reply-To: <20101122203131.7cbd604b@nehalam>
From: Stephen Hemminger <shemminger@vyatta.com>
Date: Mon, 22 Nov 2010 20:31:31 -0800
> On Tue, 23 Nov 2010 03:51:53 +0000
> Ben Hutchings <ben@decadent.org.uk> wrote:
>
>> Recent review has revealed several bugs in obscure protocol
>> implementations that can be exploited by local users for denial of
>> service or privilege escalation.
>>
>> The decnet protocol (PF_DECnet) is unmaintained. Since 2.6.12-rc2 the
>> only changes appear to be adjustments for net API changes and fixes
>> for bugs found by inspection.
>>
>> This protocol generally should not be enabled by distributions, since
>> the cost of a security flaw affecting all installed systems presumably
>> outweighs the benefit to the few (if any) legitimate users.
>>
>> Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
>
> NAK there are still users and stuff does get fixed.
> If you don't like it then disable it from config.
Seriously, I can't even remember a bonifides security flaw in decnet
being found recently and in fact the decnet stack is very well written
code.
prev parent reply other threads:[~2010-11-23 5:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-23 3:51 [PATCH 1/3] decnet: Move to staging Ben Hutchings
2010-11-23 4:31 ` Stephen Hemminger
2010-11-23 5:19 ` David Miller [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=20101122.211923.193717252.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ben@decadent.org.uk \
--cc=debian-kernel@lists.debian.org \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.com \
/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).