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.

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.

There were some changes in the installation procedure upstream, so I have added install scripts to this package. The scripts included previously in the upstream version but not this package are now also included here. Please let me know if there are problems.

Edit: I although removed some weird parts of the scripts, so not entirely the same as upstream.

Version 4.2.4-8303 exists only for the Windows package. The latest downloadable Linux versions at https://dvv.fi/en/linux-versions show 4.2.4-8296, which is what this PKGBUILD uses.

Yep, that's how it should be. Corrected now.

This package overwrites /etc/xdg/autostart/mpollux-digisign-client.desktop - which it should not do, since that is a configuration file. Well, it's a small annoyance, but the ?#@%X! autostart will be there after every upgrade (despite changing the file).

EDIT: I suggest adding:

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

to the PKGBUILD. That way the configuration file will be handled correctly.

The download URL should work now, the GUID-looking string at the end seems to be the same every time. Also it worked for me without the parameter t. In this form it's only one more thing to manually copy-paste, I hope they don't start creating unique ids for every download.