opendoas

my fork of doas with custom prompt
git clone git://git.kocotian.pl/opendoas.git
Log | Files | Refs | README | LICENSE

commit 9474e418d2184e86408f0dce09ca250e36138672
parent cfa9f0d3b306d6c1287ec4f2aa42be29de66c9de
Author: Duncan Overbruck <mail@duncano.de>
Date:   Fri, 29 Jan 2021 00:28:46 +0100

Replace build/installation instructions with discouragements

Diffstat:
MREADME.md | 24+++++++++++++++---------
1 file changed, 15 insertions(+), 9 deletions(-)

diff --git a/README.md b/README.md @@ -5,15 +5,21 @@ initially [written by Ted Unangst](http://www.tedunangst.com/flak/post/doas) of the OpenBSD project to provide 95% of the features of `sudo` with a fraction of the codebase. -At the moment only linux with GLIBC or musl libc is supported and tested. - -## Building and installing - -``` -$ ./configure -$ make -# make install -``` +## Building and installation discouragements + +There are a few steps you have to carefully consider before building and installing +opendoas: + +* There are less eyes on random doas ports, just because sudo had a vulnerability + does not mean random doas ports are more secure if they are not reviewed + or pam is configured incorrectly. +* If you want to use pam; You have to [configure pam](#pam-configuration) + and failing to do so correctly might leave a big open door. +* Use the configure script to configure the opendoas. +* Use the default make target to build the software. +* If you really want to install a setuid binary that depends on + pam being correctly configured, use the make install target + to install the software. ## About the port