Arch Linux User Repository

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.

Hi, here's a 5-minute diff for the updated version. The version path component is now 4.4.0b so I just introduced a new variable.

diff --git a/PKGBUILD b/PKGBUILD
index a122d0f..0d32b6c 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -1,7 +1,8 @@
 # Maintainer: ple <ple21108@gmail.com>
 # Contributor: Atte Virtanen <aten.email@gmail.com>
 pkgname=vrk-mpollux-digisign-client
-pkgver=4.4.0_9019
+pkgver=4.4.0_9052
+_shortver=4.4.0b
 pkgrel=1
 epoch=4
 pkgdesc="Client program for Finnish chip ID cards"
@@ -11,9 +12,9 @@ license=('custom')
 depends=('pcsclite' 'qt5-base' 'nss')
 install=vrk-mpollux-digisign-client.install

-source_x86_64=($pkgname-$pkgver.deb::"https://files.fineid.fi/download/digisign/${pkgver%_*}/linux/mpollux-digisign-client-for-dvv_${pkgver//_/-}_amd64.deb")
+source_x86_64=($pkgname-$pkgver.deb::"https://files.fineid.fi/download/digisign/${_shortver}/linux/mpollux-digisign-client-for-dvv_${pkgver//_/-}_amd64.deb")

-sha256sums_x86_64=('efc4fd2ed98eb41f7ae4b2f6b75a98627e70546d53acd951e9f28cc7243eae1d')
+sha256sums_x86_64=('032077778089ffe2686001663c743b101248ec48d919d8d8954aefca5914115d')

 backup=('etc/xdg/autostart/mpollux-digisign-client.desktop'
         'etc/xdg/Fujitsu/CCryptoLib.conf')

atostek is total garbage. I'd rather use digisign if I can.

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.

I will be supporting this package as long as DVV provides updates for DigiSign (to the end of 2025 by current information). However, I cannot check every site (I did not know about kelain.fi at all, and there are likely many others), so this package will go when DVV decides to end support. The PKGBUILD will remain available for cloning even after deletion, so old versions can still be built.

This should be not phased out at least until all services support Atostek ID. Kelain.fi still seems to only support this client (it's only documented at kelain.fi, it seems, and even there it's difficult to find and notice).

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.

@direc85 Sadly, I haven't been able to find a reason for that as there are no logs or any other output from the program beyond this error message. It just fails to bind the HTTPS port after it successfully binds a port for HTTP.

One thing you could do is to remove /etc/xdg/autostart/mpollux-digisign-client.desktop to prevent autostarting, the authentication library is usable even without the GUI.

I'm getting this every startup: Failed to open local web server's HTTPS-port; Signing services are disabled. Any clue how to fix that? The authentication part still works fine, I don't need signing support at all.

Thanks @neonmoe, I seem to have missed that. Don't know how upstream manages to use this package at all. I'll see what I can do, but it might have to be a manual step, unless the directories are created for every directory in /home (which I think wouldn't be a good thing to do).

After recently upgrading, the application would bring up a dialog asking for the password of the certificate database, even though I hadn't (knowingly) set one. Deleting ~/.digisign and ~/.pki/nssdb (as per the application's user manual) fixed the issue.

The references to $HOME in the install script seem odd to me, aren't they ran as root? That would explain why I had to do the same thing manually as my regular user.