@brynet @benjamineskola @judfilm @brightside

You in fact _are_ talking about PAM, though, because that's where 50% of the the #ifdef __Linux__ conditional compilation actually is, and 25% of it is in comments. (-:

Example: https://github.com/slicer69/doas/blob/master/doas.c#L423

#doas #LinuxPAM #PAM

doas/doas.c at master · slicer69/doas

A port of OpenBSD's doas which runs on FreeBSD, Linux, NetBSD, and illumos - doas/doas.c at master · slicer69/doas

GitHub

@brynet @benjamineskola @judfilm @brightside

Speaking as someone who put an event loop calling kevent() inside a #PAM conversation function just recently, I can say with authority that at least one of the tenets of that page is entirely wrong.

It's right about #LinuxPAM being buggy, and the fact that xyr bug got filed randomly against Fedora instead of against LinuxPAM itself is just one of the reasons that this sort of "upstream-downstream" development model is so frustrating.

@brynet @benjamineskola @judfilm @mark @brightside

Ironically, one of its open bugs is completely down to #PAM, specifically #LinuxPAM not doing what #OpenPAM does.

https://github.com/slicer69/doas/issues/17#issuecomment-1553249174

The other open bug has a very simple and blunt answer: #doas cannot compile an ioctl() out of the Linux kernel. This is a bug against #Linux, the world knows it, and the bug filer should know it.

https://github.com/slicer69/doas/issues/110

#OpenBSD

password is read from stdin, not TTY · Issue #17 · slicer69/doas

repro: echo foo | doas cat This breaks piping something to a command via doas, and breaks tools (dw/mitogen) expecting it to behave like the BSD version

GitHub
How To Set Password Policies In Linux - OSTechNix

This tutorial describes how to set password policies such as password length, password complexity, password expiration period etc., in Linux.