Sure, use a language that has access to some kind of shared global variable. For example %_SHARED in plperl: Something like: CREATE OR REPLACE FUNCTION set_foo(name text) returns void as $$ my $name = shift; die…
It's not much different than seccomp/systrace/apparmor/grsec rbac/selinux in that regard. It's per process. So sure, if the plugin forks it could pledge(). Much the same way the plugin could seccomp once forked.…
For fun I made a perl web app use this. Much simpler than systace or seccomp. I use the path argument as simple form of chroot(2). Previously I had to create a vnd (think loopback device if you are coming from linux) to…
8,500 unique IP addresses during 7 months. How is this not trivial?
I grew up on linux as well (still use arch at work and at home). But for anything serious, use OpenBSD. Its just great.
Sure, use a language that has access to some kind of shared global variable. For example %_SHARED in plperl: Something like: CREATE OR REPLACE FUNCTION set_foo(name text) returns void as $$ my $name = shift; die…
It's not much different than seccomp/systrace/apparmor/grsec rbac/selinux in that regard. It's per process. So sure, if the plugin forks it could pledge(). Much the same way the plugin could seccomp once forked.…
For fun I made a perl web app use this. Much simpler than systace or seccomp. I use the path argument as simple form of chroot(2). Previously I had to create a vnd (think loopback device if you are coming from linux) to…
8,500 unique IP addresses during 7 months. How is this not trivial?
I grew up on linux as well (still use arch at work and at home). But for anything serious, use OpenBSD. Its just great.