is this actually going to wind up stopping Sudo bash or is this "if you use it right you don't need to" which is a euphemism for "yea but everyone does"
However if you're running "sudo bash", you should probably consider setting the root shell appropriately and just use "sudo -l".
The proper fix would be VeraCrypt implementing polkit, but I just use cryptsetup's implementation.
If your linux doas does not timeout, try updating it?
1. http://man.openbsd.org/tty.4#TIOCSETVERAUTH
2. https://github.com/Duncaen/OpenDoas/blob/master/timestamp.c
ITYM "sudo -i" -l lists the programs your user may run as root/the-specified-user