netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pierre Ossman <pierre-list@ossman.eu>
To: "David S. Miller" <davem@davemloft.net>,
	Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>,
	"Pekka Savola (ipv6)" <pekkas@netcore.fi>,
	James Morris <jmorris@namei.org>,
	Hideaki YOSHIFUJI <yosh
Cc: netdev@vger.kernel.org
Subject: Re: [RFC][PATCH] Export all RA options that we don't handle to userspace
Date: Sun, 20 Nov 2011 15:00:46 +0100	[thread overview]
Message-ID: <20111120150046.03c91963@mjolnir.ossman.eu> (raw)
In-Reply-To: <20110120091505.165737a1@mjolnir.ossman.eu>

[-- Attachment #1: Type: text/plain, Size: 1251 bytes --]

Reping!

On Thu, 20 Jan 2011 09:15:05 +0100
Pierre Ossman <pierre-list@ossman.eu> wrote:

> Ping!
> 
> The userspace support is rather useless without these kernel bits...
> 
> On Sun, 12 Dec 2010 14:47:06 +0100
> Pierre Ossman <pierre-list@ossman.eu> wrote:
> 
> > Second patch that exports everything. If noone objects to this model,
> > then merge the two patches and just use the commit message from the
> > second one.
> > 
> > Pros:
> > - Kernel doesn't need to be updated for every new RA option that might
> >   show up.
> > 
> > Cons:
> > - Possible security issue if it requires less privilege to read these
> >   netlink messages than to open a raw ICMPv6 socket.
> > - List of types the kernel is interested in is now in two places in the
> >   code, creating a risk for getting out of sync. I tried to come up
> >   with a structure that would prevent this, but couldn't think of
> >   anything that wouldn't require large changes. Ideas welcome...
> > 
> > Rgds
> 
> 


-- 
     -- Pierre Ossman

  WARNING: This correspondence is being monitored by FRA, a
  Swedish intelligence agency. Make sure your server uses
  encryption for SMTP traffic and consider using PGP for
  end-to-end encryption.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 230 bytes --]

  reply	other threads:[~2011-11-20 14:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-12 13:43 [RFC][PATCH] Export DNSSL RA option to userspace Pierre Ossman
2010-12-12 13:47 ` [RFC][PATCH] Export all RA options that we don't handle " Pierre Ossman
2011-01-20  8:15   ` Pierre Ossman
2011-11-20 14:00     ` Pierre Ossman [this message]
2011-11-20 16:29       ` David Miller
2011-03-03  1:30   ` Pierre Ynard
2010-12-12 14:07 ` [RFC][PATCH] Export DNSSL RA option " Pierre Ossman
2011-03-03  1:36   ` Pierre Ynard
2010-12-14 13:10 ` David Woodhouse
2010-12-14 13:43   ` Pierre Ossman
2010-12-16  1:18     ` Dan Williams
2011-03-03  1:27 ` Pierre Ynard

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=20111120150046.03c91963@mjolnir.ossman.eu \
    --to=pierre-list@ossman.eu \
    --cc=davem@davemloft.net \
    --cc=jmorris@namei.org \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=netdev@vger.kernel.org \
    --cc=pekkas@netcore.fi \
    /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).