Val V

> 1. Where is your doas.conf file located? On FreeBSD-based systems it should be /usr/local/etc/ It's there, otherwise doas would've complained: already checked that > 2. Is your user part...

Once I hit this problem, I added it as per discussion in #31, because I noticed `sudo` file under `/usr/local/etc/pam.d`. So I tried before without it with no success. If...

`doas` is clearly linked against PAM, and as I see from here the error sits under `PAM_MAXTRIES` case returned by `pam_authenticate()`.

The difference in the audit log is: ``` user authenticated successfully for sudo [using OPNsense\Auth\Services\System + OPNsense\Auth\Local] ``` vs ``` user could not authenticate for doas. [using - + -]...

It's interesting, because the `sudo` port is in sync with upstream: - https://github.com/opnsense/ports/tree/master/security/sudo - https://github.com/freebsd/freebsd-ports/tree/main/security/sudo and the `sudo` PAM file is expected there. when I was inspecting PAM configs under...

ok, so I should've read https://docs.opnsense.org/development/components/authentication.html closer. After adding `doas` to [this list](https://github.com/opnsense/core/blob/master/src/opnsense/mvc/app/library/OPNsense/Auth/Services/System.php#L51-L55) it started working (with `/usr/local/etc/pam.d/doas` in place): ``` user authenticated successfully for doas [using OPNsense\Auth\Services\System + OPNsense\Auth\Local]...

I guess the biggest part of the request here is shortcuts, so with different shortcuts you could have different autotype sequences.

Yeah, exactly. TOTP is a special case though. If I have 800 entries and TOTP ones are only 50 of them, it makes little sense to output all for filtering...

Precisely. So keepmenu has to be smart to see if there's *only* `{TOTP}` in autotype, generate the list only of those entries that contain it.

Apparently this is a duplicate of #140. Recently dotool support was added -- I tested it and it worked as expected. But with pynput I get 1-to-1 conversion of `|`...