Arch Linux User Repository

Switching back to botan2 from botan2.19 might need manual intervention.

In other words, first remove botan2.19 ignoring dependencies:

# pacman -Rdd botan2.19

And then reinstall atostekid.

Switching back to botan2 from botan2.19 might need manual intervention.

In other words, first remove botan2.19 ignoring dependencies:

# pacman -Rdd botan2.19

And then reinstall atostekid.

@the-k, thank you for fixing the original botan2 package! I have switched back to it.

I'm not sure if I can provide a smooth transition from botan2.19 back to botan2 just by editing the PKGBUILD of botan2.19.

FYI, I've not only fixed botan2 package, I've also pulled in available security fixes.

I created an alternative AUR package of Botan 2 (botan2.19) that works with current versions of Boost. I hope someone fixes the botan2 AUR package, so I don't have to maintain a separate version.

I also tried to update from Atostekid 4.4.0.0 to 4.4.1.0. Unfortunately, it core dumps at start. I could not yet figure out the reason. Seems upstream has dropped some system library dependencies and included them as bundled libraries. I'll try to make sense of it at some other time. But if someone wants to figure it out in the meantime, be my guest :)

@tomkarho, thanks for the feedback.

Regarding issue 1, someone has also raised the issue in the comments of the botan2 AUR package. I guess we could make atostekid depend on an older version of boost. Or let's see if the upstream AUR package comes up with another solution.

Regarding issue 2, I cannot reproduce this behavior. Do you have qt6-wayland installed? It is listed as an optional dependency for atostekid.

Couple of gotchas I ran into just in case someone else runs into these same problems:

1 The build failed for me due to botan2

I had to build botan2 with some modifications to the pkgbuild. Modfying its PKGBUILD like this solved the problem for me:

./configure.py \
    --prefix=/usr \
    --with-bzip \
    --with-lzma \
    --with-zlib \
    --disable-modules=boost_asio,socket,sockets,unix_sockets,streams \
    --without-documentation \
    --with-os-feature=getrandom \
    --build-targets=shared,tests

2 The app crashes as soon as I inserted the card in the reader

Seems to be an issue with Wayland an qt. Running with QT_QPA_PLATFORM=xcb solved that one for me.

QT_QPA_PLATFORM=xcb atostekid

@ewtoombs: How did you configure Firefox to use Atostek ID? For me Firefox only crashes, if the pcscd.{service,socket} is not started. In any case, the overall user experience is so sluggish and cumbersome, that I almost never use my ID card on Linux. I just test that suomi.fi login works after every update, and that's about it :D

Now, 4.3.0.0 tends to crash all of firefox and 4.3.1.0 doesn't work at all.

There's now a section for Atostek ID in the Arch Wiki: https://wiki.archlinux.org/title/Electronic_identification#Atostek_ID

Feel free to document more use cases or add other details.

I just tried the latest version of DigiSignClient (4:4.3.2_8863-1) on Arch Linux. If DigiSignClient is running, Firefox delegates the PIN dialog correctly to DigiSignClient. If it is not running, Firefox shows its own dialogs multiple times, and does not explicitly ask which PIN the user should enter.

I also tried Atostek ID (4.3.0.0) on Ubuntu 24.04 with regular Firefox (non-snap). PIN dialogs are shown by Firefox (multiple times), even though the Atostek ID app is running in the background. Well, at least the Firefox dialogs now explicitly tell which PIN it wants in this Atostek PKCS#11 module implementation.

In summary, it seems that the Atostek PKCS#11 module works equally bad with Firefox both in Arch Linux and Ubuntu.