1 This is the "OpenDoas" port of OpenBSD's doas.
3 The doas utility is a program originally written for OpenBSD that
4 allows a user to run a command as though they were another user,
5 typically root. doas acts as an alternative to sudo, with simple
6 configuration syntax and a smaller code base for ease of security
9 Please note that running this SlackBuild will install doas with SUID
12 To get started, write a configuration file at /etc/doas.conf. As an
13 example, including the line:
17 will allow all users in the wheel group to act as root with doas.
18 Consult the doas.conf(5) man page for further details.
20 The parameter "keepenv" in /etc/doas.conf allows for opening graphical
21 applications with doas:
23 permit keepenv gene as root
26 The owner and group for /etc/doas.conf should both be 0, file permissions should be set to 0400
28 chown -c root:root /etc/doas.conf
29 chmod -c 0400 /etc/doas.conf
32 "exec dbus-launch --exit-with-session" may be required for xinit in
33 Slackware 14.2. An alternative is to run "export $(dbus-launch)" after
34 starting the X session. As with su, KDE 4 graphical applications may
35 fail to open with doas.
37 Running this SlackBuild without parameters will provide a build of
38 OpenDoas with shadow support if PAM is not installed, and with PAM
39 support if PAM is installed. Password persistence is disabled by
42 To enable timestamp-based password persistence, call the SlackBuild
45 PERSIST=yes ./opendoas.SlackBuild
47 In addition, ensure that the appropriate user or group line in
48 /etc/doas.conf includes the "persist" option, as in this example:
50 permit persist jane as root
52 Please note that upstream considers timestamp-based password
53 persistence to be "new and potentially dangerous."
55 For users with PAM installed, enable shadow authentication instead by
56 calling the SlackBuild with PAM=no:
58 PAM=no ./opendoas.SlackBuild
60 If /etc/pam.d/other and /etc/pam.d/system-auth are unmodified from the
61 state in which they are shipped in -current, doas will run with PAM
62 support if so compiled. Otherwise, doas may require a dedicated file at
63 /etc/pam.d/doas to use PAM authentication.
65 To allow OpenDoas to write a new PAM configuration file for doas, call
66 the SlackBuild with PAM_FILE=yes:
68 PAM_FILE=yes ./opendoas.SlackBuild
70 Upstream is unlikely to include PAM configuration files in releases of
71 OpenDoas beyond 6.8.2.
73 opendoas has no outside dependencies on Slackware 14.2 or 15.0 and
74 adds no users or groups. opendoas conflicts with all other ports of
77 For a smooth transition from sudo to doas and to stay downward compatible,
78 you could add to your environment: