Re:Strong_password Rubygem hijacked
by viraptor on Sunday July 07, 2019 @10:09PM
(#20379399)
That's solved in similar frameworks by separating open and read/write. You open (or inherit from somewhere) a logging socket, drop the open privileges, retain the permission to write to the log socket.
[ Parent
| on HN ]
This discussion is basically inventing a per-library pledge(2).
or apparmor, selinux, grsec, tomoyo, ... But those systems can't integrate into scripting language per-library use case without some serious thread / IPC overhead.
These others can achieve what's intended, but the entire flavour of the discussion is a dead ringer for pledge's purpose and interface, which is much simpler and very much internal to the software (a self-check of sorts).