Christian Hesse

Sent my current implementation here: https://lists.archlinux.org/pipermail/pacman-dev/2022-January/025505.html Anybody wants to give it a try? Add this in your `pacman.conf`: ``` [cache-servers] Server = http://pkgbuild.com/~eworm/$repo/ ```

Just apply this commit on top of official PKGBUILD: https://github.com/eworm-de/pacman/commit/83d57f376da76d26fbaab2e690540b75ac29ba7f

The package from my repository works fine for me... Verified just now. Can you give any detail from your configuration that causes this? Any issue with pacman from official repository?

Wait, you took just the pacman binary from my package? Of course that breaks, as libalpm has API changes.

This already supports second factor on top of the stored challenge. What's wrong with that?

> Challenge is stored in clear available to anyone. If someone has access to yubikey, the response and at least half of luks passphrase is avalaible . That means it...

What happens if an error occurs half way through the process?

The actual work is done by a `udev` helper that does not have access to the terminal. So we can not display any messages.

This is not intended to be used that way. Just keep another key slot around with a human-friendly (but still strong!) password.

Well, that's not a crash, but an error caused by failed dbus auto-activation. You say "*seems to not always work*"... Is it always the second notification deamon start that fails?...