Hi,

On 2025-04-23 12:32:45 -0700, Soren Stoutner wrote:
> It looks like the otpclient package could change the default maximum 
> memlock for all users by installing a config file in /etc/systemd/
> user.conf.d.
[...]

Is there any news? I would have hoped this to be fixed for trixie.

There actually seem to be 2 issues:

1. A warning is displayed even though the limit will not necessarily
be reached. This has been fixed upstream; see upstream bug and commit:

https://github.com/paolostivanin/OTPClient/commit/d5f1e4f3cf15cf2067d46a5ee1740f1a0f5b2544

  Only show memlock warning dialog when secure memory is unavailable

  This change ensures that secure memory availability is checked on
  demand.
  The warning dialog with a link to the wiki is now only displayed if
  there isn't enough secure memory available, avoiding unnecessary
  interruptions when everything is correctly configured.

2. The limit may really be too low (I suppose that if a warning is
displayed, this means that this limit is likely to be reached, at
the point that it should be increased). Note that the upstream bug
does not mention any memory improvement. So I suppose that the limit
should also be increased.

-- 
Vincent Lefèvre <[email protected]> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / Pascaline project (LIP, ENS-Lyon)

Reply via email to