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
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 04 Jul 2007 17:08:33 +0200
From:	Johannes Berg <>
To:	Patrick McHardy <>
Cc:	netdev <>, jamal <>,
	Thomas Graf <>,
	Herbert Xu <>
Subject: Re: multicasting netlink messages to groups > 31 from userspace

On Wed, 2007-07-04 at 17:00 +0200, Patrick McHardy wrote:

> Not by itself probably but a user could DoS your wireless connectivity
> this way.

Hmm, if anything then not the connectivity but rather the MLME i.e. it
won't do roaming properly maybe. Maybe we should then have a way to say
that somebody only wants to receive messages from privileged users, that
way the MLME process wouldn't be affected.

> I'm not sure, it would probably also have to be called when userspace
> unsubscribes from a group, no?

No actually having that hook means I can do without multicast groups by
just publishing that "send configuration requests to pid N" where N is
either 0 (in-kernel MLME) or something else (userspace MLME); I just
didn't know the hook existed.

Not that we shouldn't fix the multicast issues anyway though the one
from this particular thread wouldn't be too interesting right now until
somebody needs userspace to multicast; the other three patches still
should be done now before there are more generic netlink multicast


Download attachment "signature.asc" of type "application/pgp-signature" (191 bytes)

Powered by blists - more mailing lists