netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@vyatta.com>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: Andrew Hendry <andrew.hendry@gmail.com>,
	David Miller <davem@davemloft.net>,
	Greg Kroah-Hartman <gregkh@suse.de>,
	netdev <netdev@vger.kernel.org>,
	devel@driverdev.osuosl.org,
	Debian kernel maintainers <debian-kernel@lists.debian.org>,
	linux-x25@vger.kernel.org
Subject: Re: [PATCH 3/3] x25: Move to staging
Date: Mon, 22 Nov 2010 20:31:55 -0800	[thread overview]
Message-ID: <20101122203155.27534f3b@nehalam> (raw)
In-Reply-To: <1290484528.6770.1336.camel@localhost>

On Tue, 23 Nov 2010 03:55:28 +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 x25 protocol (PF_X25) receives only 'odd fixes'.  There appear to
> be no published applications for it, and it has never progressed
> beyond 'experimental' status.
> 
> 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>
> ---
> I'm somewhat less sure about this one; maybe it's improving?  But there
> is little enough sign of any usefulness after 10 years.
> 
> There are several X25 dependencies that presumably should be moved too.

No. If you don't like it then don't enable it.

  reply	other threads:[~2010-11-23  4:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-23  3:55 [PATCH 3/3] x25: Move to staging Ben Hutchings
2010-11-23  4:31 ` Stephen Hemminger [this message]
2010-11-23  5:05   ` Andrew Hendry

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=20101122203155.27534f3b@nehalam \
    --to=shemminger@vyatta.com \
    --cc=andrew.hendry@gmail.com \
    --cc=ben@decadent.org.uk \
    --cc=davem@davemloft.net \
    --cc=debian-kernel@lists.debian.org \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@suse.de \
    --cc=linux-x25@vger.kernel.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).