lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Mon, 22 Apr 2019 19:15:43 -0700
From:   Tom Herbert <>
To:     David Ahern <>
Cc:     Tom Herbert <>,
        "David S . Miller" <>,
        Linux Kernel Network Developers <>
Subject: Re: [PATCH v5 net-next 5/6] ip6tlvs: Add netlink interface

On Mon, Apr 22, 2019 at 6:49 PM David Ahern <> wrote:
> On 4/22/19 7:15 PM, Tom Herbert wrote:
> > Is there are particular reason why you think rtnetlink would be more
> > appropriate?
> Thinking about this from an app API perspective: rtnetlink is used to
> configure IPv6 addresses and IPv6 routes yet extensions will require a
> genl interface. Just seems odd for some network manager / FRR / other to
> deal with.


This interface is for configuring general parameters about TLV types,
it's not for setting TLVs on routes or packet. The "ip" command type
interface using genl should be sufficient for that purpose. For
exmple, here is "ip" command I'm using to allow non-privileged users
to set path MTU option (draft-hinden-6man-mtu-option-01):

sudo $QDIR/sbin/ip ip6tlv set type 62 order 80 user-perm 1 class 1
align-mult 2 align-off 0 min-len 4 max-len 4 len-mult 1 len-off 0


Powered by blists - more mailing lists