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: <93a0f6cb-1aea-4b8d-a1a4-0f5876eb333b@sirena.org.uk>
Date:   Fri, 1 Sep 2023 13:18:53 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Zev Weiss <zev@...ilderbeest.net>
Cc:     Naresh Solanki <naresh.solanki@...ements.com>,
        Liam Girdwood <lgirdwood@...il.com>,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/3] regulator: userspace-consumer: Add regulator event
 support

On Fri, Sep 01, 2023 at 02:27:28AM -0700, Zev Weiss wrote:

> I for one frequently examine things in sysfs using shell commands like 'cat'
> and 'grep' and such, and I suspect I'm (very, very) far from alone in that.
> With this design a user doing that could cause a monitoring daemon to miss
> events that it was expecting to receive via this file.

> I don't think we should be creating sysfs files that are secretly land mines
> that allow a curious user innocently peeking around in sysfs doing (they
> think) read-only operations to break things for other programs using those
> files.

It could be switched to clear on read.  Like I said on the prior version
the userspace consumer is a bit of a sharp edge at the best of times.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ