[Bug 297452] security/libgcrypt: mlock fails, leading to "secure memory pool is not locked while in FIPS mode"

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=297452

            Bug ID: 297452
           Summary: security/libgcrypt: mlock fails, leading to "secure
                    memory pool is not locked while in FIPS mode"
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: [email protected]
          Reporter: [email protected]
             Flags: maintainer-feedback?([email protected])
          Assignee: [email protected]

When I try to run pinentry-gnome3 (from security/pinentry-gnome), it fails like
this:

> pinentry-gnome3
secure memory pool is not locked while in FIPS mode
fatal error in libgcrypt, file misc.c, line 91, function _gcry_fatal_error: out
of core in secure memory

Fatal error: out of core in secure memory
fish: Job 1, 'pinentry-gnome3' terminated by signal SIGABRT (Abort)

ktrace shows that an mlock call failed.  That sounds like an OS error.  Indeed,
I recently updated my OS from 15.1-RELEASE-p1 to -p2 .  However, if I run
pinentry-curses instead (which does not use libcrypt), it can successfully use
mlock.  So I don't know if the true problem lies in pinentry-gnome3, libcrypt,
or the OS.  But I'm guessing libcrypt

VERSIONS
========

OS: both 15.1-RELEASE-p1 and 15.1-RELEASE-p2
pinentry-gnome: 1.3.3 (installed on July 26 2026)
libgcrypt: 1.12.2 (installed on July 26)

KTRACE OUTPUT:
=============

Working program: pinentry-curses:
  4359 pinentry-curses CALL  mlock(0x63a0cc6a000,0x10000)
  4359 pinentry-curses RET   mlock 0

Failing program: pinentry-gnome3
  5559 pinentry-gnome3 CALL  mlock(0x2e31f5681000,0x8000)
  5559 pinentry-gnome3 RET   mlock -1 errno 12 Cannot allocate memory

-- 
You are receiving this mail because:
You are the assignee for the bug.