diff options
| author | Jasper Lievisse Adriaanse <jasper@humppa.nl> | 2017-04-15 14:41:32 +0200 |
|---|---|---|
| committer | Jasper Lievisse Adriaanse <jasper@humppa.nl> | 2017-04-17 15:06:59 +0200 |
| commit | 68fc2e8b5f8bcd203598e6da2a98d5aa7359af1e (patch) | |
| tree | 513909183e7b174b06f5bc2b2e66230b23dd4e4f /README.md | |
| parent | 15973d1f5225ee4fc0114d70a24a695486f482d4 (diff) | |
Use bsd_auth(3) instead of PAM on OpenBSD
Also apply two security measures for OpenBSD:
- use explicit_bzero(3)
- mlock(2) works for non-root users too
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 4 |
1 files changed, 4 insertions, 0 deletions
@@ -16,6 +16,7 @@ Many little improvements have been made to i3lock over time: - You can specify whether i3lock should bell upon a wrong password. - i3lock uses PAM and therefore is compatible with LDAP etc. + On OpenBSD i3lock uses the bsd_auth(3) framework. Requirements ------------ @@ -37,6 +38,9 @@ Running i3lock Simply invoke the 'i3lock' command. To get out of it, enter your password and press enter. +On OpenBSD the `i3lock` binary needs to be setgid `auth` to call the +authentication helpers, e.g. `/usr/libexec/auth/login_passwd`. + Upstream -------- Please submit pull requests to https://github.com/i3/i3lock |