>/usr/X11R6/bin/xlock is installed by default
Most servers will not install Xenocara at all in order to avoid
most security and space issues, as a lot of them now are using
vmm(4) for testing purposes.
Also as xlock moved upsteeam, OpenBSD will stop importing xlock
and maybe the will implement a patched and pledge(4)d slock (with
some features such as passwd display as asterisks) as the
Xenocara's workstation locker.
If would not be weird at all. Today the default wm is FVWM because
of historical respect to BSD's/Unix, but the most common WM used
by OpenBSD fans is, by far, CWM, which came from evilwm.
As Xenocara was already a fork of X, having a patched slock as
"xenolock" would be the next logical step.
Because xlock(4) is a shitty security fest by itself. Not to
blame the OpenBSD developers, but the main project. It's full of
features and slock matches better the OpenBSD's philosophy.
Most servers will not install Xenocara at all in order to avoid
most security and space issues, as a lot of them now are using
vmm(4) for testing purposes.
Also as xlock moved upsteeam, OpenBSD will stop importing xlock
and maybe the will implement a patched and pledge(4)d slock (with
some features such as passwd display as asterisks) as the
Xenocara's workstation locker.
If would not be weird at all. Today the default wm is FVWM because
of historical respect to BSD's/Unix, but the most common WM used
by OpenBSD fans is, by far, CWM, which came from evilwm.
As Xenocara was already a fork of X, having a patched slock as
"xenolock" would be the next logical step.
Because xlock(4) is a shitty security fest by itself. Not to
blame the OpenBSD developers, but the main project. It's full of
features and slock matches better the OpenBSD's philosophy.