Package Details: sac-gui 10.8.1050-1

Git Clone URL: https://aur.archlinux.org/sac-core.git (read-only, click to copy)
Package Base: sac-core
Description: Thales/Gemalto SafeNet Authentication Client for eToken 5110/5300 & IDPrime (GUI tools)
Upstream URL: https://cpl.thalesgroup.com/access-management/security-applications/authentication-client-token-management
Keywords: etoken sac safenet
Licenses: custom
Submitter: s3rj1k
Maintainer: grawity
Last Packager: grawity
Votes: 12
Popularity: 0.37
First Submitted: 2015-08-10 09:03 (UTC)
Last Updated: 2023-08-23 18:07 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 Next › Last »

grawity commented on 2022-12-04 20:01 (UTC)

Yes, pcscd needs to be restarted to reload its IFD drivers. I'm really not sure why they are not included with SAC 10.8 even though it's supposed to support the 5110.

Once pcscd sees the device, either the 10.8 or legacy 10.0 PKCS#11 modules should work identically, even without the SACSrv daemon (I think that's only used by the GUI components).

pirofti commented on 2022-12-04 18:52 (UTC)

After restarting the pcscd daemon, the device was visible. So either I installed the sac-legacy package before starting the daemon, either something else was wrong, but I did manage to see the device with this. Thank you and sorry about the noise!

pirofti commented on 2022-12-04 10:32 (UTC)

Thank you for the quick reply! Sorry, forgot to mention that I also have core-legacy installed and the safenet service running. So that does not fix things.

grawity commented on 2022-12-04 09:06 (UTC)

SAC 10.8 only has partial support for 5110 and is missing the PCSC "USB card reader driver" (aks-ifdh). You'll need to have sac-core-legacy installed for that.

pirofti commented on 2022-12-03 22:16 (UTC)

My Safenet 5110 device is not displayed by SACTools even though I can use it in Windows and I see it in the dmesg when plugging it in. Are there any extra steps I need to run before starting SACTools? Is there any extra documentation I should read? Thank you!

grawity commented on 2022-11-27 11:33 (UTC)

I see that libeToken.so loads libcrypto.1.1 at run-time, but it seems to be optional – the PKCS#11 module still works without. Is there some functionality that requires OpenSSL?

antonbutanaev commented on 2022-11-25 08:18 (UTC)

Missing dependency openssl-1.1

andreqls commented on 2022-06-27 17:38 (UTC)

A new version is out (10.8.28). I got this PKGDBUILD to work normally by replacing the source link with the link for the previous version "https://installer.id.ee/media/etoken/older%20versions/SAC%2010.7%20Linux.zip", but I suppose it could be tested with the new version and then updated.

ecruz1986 commented on 2021-12-15 19:21 (UTC)

Hi, thanks for maintaining this! Why are the GUI tools not included? They were useful to me on my previous Ubuntu setup. If it's not too hard, could they be included?

grawity commented on 2021-03-10 13:22 (UTC) (edited on 2021-03-10 13:23 (UTC) by grawity)

Accessing the certificate isn't the problem. Literally any program implementing PKCS#11 can access the certificate through SafeNet's PKCS#11 module, so that's probably 95% of all certificate-related programs.

The problem is in dealing with the actual documents. What document formats are you working with? What signature formats do you need? There are plenty, and saying "like in windows" really doesn't say a lot.

If you don't need any special formats and you're just signing those PDFs straight in Acrobat Reader, then I think KDE's Okular has recently gained the ability to do that. LibreOffice might work too. It looks like LO uses NSS so you'll need to load the PKCS#11 module using modutil (or through Firefox GUI). I don't know what Okular uses, but it might be p11-kit (in which case you use ~/.config/pkcs11/modules), I'll try to check it later.

For Word .docx documents (not legacy .doc), LibreOffice's XML-DSig support looks like it might work, but the last time I tried it, it wasn't entirely compatible with MS Office. I think it was more oriented towards .odt than .docx at the time.

Creating for example .asice or .bdoc files (for government documents in Europe) is a different matter.

« First ‹ Previous 1 2 3 4 5 6 7 Next › Last »