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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sat, 26 May 2007 03:42:20 -0300 From: "Martín Ferrari" <martin.ferrari@...il.com> To: "David Miller" <davem@...emloft.net> Cc: greearb@...delatech.com, netdev@...r.kernel.org Subject: Re: IFF_PROMISC again Hi David, On 5/22/07, David Miller <davem@...emloft.net> wrote: > > Anyone know the reasoning for masking out the PROMISC flag > > in dev_get_flags() ? > > Because promiscuous status is a counter, not a binary > on-off state. > > You can't expect to just clear it and expect all the > other promiscuous users to just "go away" and be ok > with the device leaving promiscuous mode. Yes, this is fully understood. > Since you can't sanely "set" it, we don't provide it > either. I think it's cleaner how is done now, but the needed information is hidden, not having a proper way of querying the counter or the real (binary) promiscuous state is a problem for userspace. Do you think the patch I suggested is not a good idea? Do you think there is a acceptable way of exporting that info to userspace? (as I just said to Ben, the /sys/.../flags file doesn't seem a very clean way of checking it). -- Martín Ferrari - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists