Req #73340 [Opn]: SHMOP: Access to SHM_LOCK, SHM_UNLOCK
| From: | cmb@php.net | Date: | Tue, 12 Oct 2021 17:11:12 +0000 |
| Subject: | Req #73340 [Opn]: SHMOP: Access to SHM_LOCK, SHM_UNLOCK | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-237168@lists.php.net to get a copy of this message | ||
Edit report at https://bugs.php.net/bug.php?id=73340&edit=1
ID: 73340
Updated by: cmb@php.net
Reported by: narf at devilix dot net
Summary: SHMOP: Access to SHM_LOCK, SHM_UNLOCK
Status: Open
Type: Feature/Change Request
-Package: POSIX related
+Package: *Extensibility Functions
PHP Version: Irrelevant
Block user comment: N
Private report: N
New Comment:
SHM_LOCK is not part of POSIX[1], so might not be available
everywhere, and I don't think there's anything like that on
Windows.
[1] <https://pubs.opengroup.org/onlinepubs/9699919799/functions/shmctl.html>
Previous Comments:
------------------------------------------------------------------------
[2016-10-18 18:11:48] narf at devilix dot net
Description:
------------
I was looking for a way to store encryption keys in (guaranteed to be non-swap) memory, and
apparently setting the SHM_LOCK flag on a shared memory segment seems to be the only way to do that.
Obviously, PHP doesn't expose shmctl() directly and that's probably for a good reason, but
can we have something like shmop_lock(), or an optional parameter to shmop_open()?
(on a related note, shmop_stat() would be nice too)
------------------------------------------------------------------------
--
Edit this bug report at https://bugs.php.net/bug.php?id=73340&edit=1