Yeah this was kind just FYI. It's interesting they've already deprecated this while still not supporting Atostek ID in all their services.
FWIW I can not for some reason get Firefox to talk with DigiSign at the moment (while Firefox does work with Atostek). It seems Firefox can not communicate with DigiSign at all (after adding libcryptoki.so in Firefox), as it used to be. In case anyone has any insight as to why this might be, I'd be happy to hear (for time being I'm not going to troubleshoot this further).
Ah well, DigiSign always was kind of hit-or-miss and had really beginner-grade mistakes even in the script used to start it. I'm assuming this is just a sign of bad QC upstream.
Pinned Comments
ple commented on 2025-02-22 17:30 (UTC) (edited on 2025-03-09 15:24 (UTC) by ple)
If anyone did not know yet, the DigiSignClient application has been deprecated by upstream. The replacement is Atostek ID, which is available on AUR at https://aur.archlinux.org/packages/atostekid (packaged by @2-4601). I suggest everyone migrate to that, as I will be submitting a request for deletion of this package at some point in the near future.
Edit: upstream will apparently be providing bugfixes until the end of 2025, so I will keep updating this package if any updates become available. That said, everyone should still migrate to Atostek ID.