It is because openbsd persists the auth via a cookie in the terminal. that is, to do it the openbsd way a change in the tty code is required. It is odd that the

It is because openbsd persists the auth via a cookie in the terminal. that is, to do it the openbsd way a change in the tty code is required. It is odd that the linux port does not track the process id or something. http://man.openbsd.org/tty.4#TIOCSETVERAUTH http://man.openbsd.org/tty.4#TIOCSETVERAUTH A post I found on the rational behind this mechanism. https://marc.info/?l=openbsd-misc&m=150032397404966&w=2 https://marc.info/?l=openbsd-misc&m=150032397404966&w=2 edit: I was looking at the opendoas project and it does something with the persist option, still reading the code but it looks like it sets some sort of timestamp on file descriptor 0. update: found it, here is the timestamp code. probably a user space version of what openbsd doas does in the kernel. https://github.com/Duncaen/OpenDoas/blob/master/timestamp.c https://github.com/Duncaen/OpenDoas/blob/master/timestamp.c So linux doas is trying to do something. Note that per that mail post I found doas auth persist has a different scope than sudo auth persist. this can have implications in a scripted environment.