netdev - Re: IFF_PROMISC again

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>] [day] [month] [year] [list]

Message-ID: <b9800b70705281507r593ca9a3m18cbd3e6ac446587@mail.gmail.com>
Date:	Mon, 28 May 2007 19:07:43 -0300
From:	"Martín Ferrari" <martin.ferrari@...il.com>
To:	"Stephen Hemminger" <shemminger@...ux-foundation.org>
Cc:	"Ben Greear" <greearb@...delatech.com>, netdev@...r.kernel.org
Subject: Re: IFF_PROMISC again

Stephen,

On 5/28/07, Stephen Hemminger <shemminger@...ux-foundation.org> wrote:

> > Great that you point it out. Then, we're back to the initial
> > situation, there is no reliable way of polling promisc state, and I am
> > looking for a way to do that. Ways I think it could be done:
>
> Back to the original question. Why should an application care?

Not an application, but the sysadmin do cares about it. And most
rootkit detectors don't have any other way of checking if a
tcpdump-like tool is running.

I don't see the usefulness of keeping the current toggle via gflags,
which is confusing for users. But I see a benefit in exporting
promiscuity as a read-only value, and I think it's pretty trivial to
provide 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