lists.openwall.net   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] [thread-next>] [day] [month] [year] [list]
Message-ID: <b7c2075a-bfcd-81fe-fa71-9486f6b8909f@6wind.com>
Date:   Wed, 21 Mar 2018 16:51:47 +0100
From:   Nicolas Dichtel <nicolas.dichtel@...nd.com>
To:     David Miller <davem@...emloft.net>, dsahern@...il.com
Cc:     netdev@...r.kernel.org, sharpd@...ulusnetworks.com
Subject: Re: [PATCH net-next] fib_rules: rename FRA_PROTOCOL to FRA_ORIGINATOR

Le 21/03/2018 à 16:15, David Miller a écrit :
> From: David Ahern <dsahern@...il.com>
> Date: Wed, 21 Mar 2018 09:00:09 -0600
> 
>> The rule->proto value is not used as a selector. It is passed in, stored
>> on a rule and returned to userspace. It is book keeping only so an admin
>> has some idea of which program installed the rule.
> 
> This is how I understand this value to work as well.
> 
Me too, and it's the reason why I propose to rename it, to make this clear.
'originator' is a lot more explicit than 'proto'.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ