[okular] [Bug 459173] Cannot use USB smartcard to sign document
https://bugs.kde.org/show_bug.cgi?id=459173 Syiad changed: What|Removed |Added Platform|Gentoo Packages |Kubuntu --- Comment #8 from Syiad --- It seems to be caused by the fact that there are two certificates on the card. Signing documents with okular suddenly worked as advertised, after I accidentally had deleted the one for "Non-repudiation". It's now been restored by the issuer of the card and signing is not possible anymore with okular; it goes into the endless loop of password requests. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 459173] Cannot use USB smartcard to sign document
https://bugs.kde.org/show_bug.cgi?id=459173 Syiad changed: What|Removed |Added Version|23.04.3 |23.08.5 --- Comment #7 from Syiad --- Still the case with - okular 23.08.5 - KDE framework 5.115.0 - Qt 5.15.12 - libpoppler-qt5-1 24.02.0 Could this be caused by the fact that the smart card holds *two* certificates? One is for "Digital Signature, Key Encipherment", the other one for "Non-Repudiation". They are both listed as options to choose from for signature, but then okular goes into the infinite loop of asking for the password again and again. Thunderbird also has an issue with the certificates on the smart card. It recognises only one for "Non-Repudiation" as useable for signing e-mails, claiming that there is none suitable for encryption. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 459173] Cannot use USB smartcard to sign document
https://bugs.kde.org/show_bug.cgi?id=459173 --- Comment #6 from Sune Vuorela --- (In reply to Robert Riemann from comment #5) > > What version of poppler (The underlying pdf library) are you using ? > > > > The double-pin should be fixed I think, by poppler 23.04, maybe 23.05. > > I am using Poppler 23.06.0 with PDF Backend 0.6.5. Do you have a link on the > poppler bug report? If it is already merged in 23.06.0 I may reopen it. There is no bug report on it. I noticed it while doing other stuff. https://gitlab.freedesktop.org/poppler/poppler/-/merge_requests/1339 is the merge request. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 459173] Cannot use USB smartcard to sign document
https://bugs.kde.org/show_bug.cgi?id=459173 --- Comment #5 from Robert Riemann --- > What version of poppler (The underlying pdf library) are you using ? > > The double-pin should be fixed I think, by poppler 23.04, maybe 23.05. I am using Poppler 23.06.0 with PDF Backend 0.6.5. Do you have a link on the poppler bug report? If it is already merged in 23.06.0 I may reopen it. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 459173] Cannot use USB smartcard to sign document
https://bugs.kde.org/show_bug.cgi?id=459173 Sune Vuorela changed: What|Removed |Added CC||k...@pusling.com --- Comment #4 from Sune Vuorela --- (In reply to Robert Riemann from comment #3) > So with this shared library, it seems to work, even though the PIN has to be > entered twice and a document password as well for no obvious reason. What version of poppler (The underlying pdf library) are you using ? The double-pin should be fixed I think, by poppler 23.04, maybe 23.05. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 459173] Cannot use USB smartcard to sign document
https://bugs.kde.org/show_bug.cgi?id=459173
Robert Riemann changed:
What|Removed |Added
CC||rob...@riemann.cc
--- Comment #3 from Robert Riemann ---
I am on Okular Version 23.04.3 (opensuse Tumbleweed with wayland). For me,
signing with my Belgium ID card in the smart card reader works.
1) I select digitally sign and draw a box
2) I choose the signing cert (in a dropbox with also a authorisation cert)
3) I enter the PIN
4) I get asked for a document password and click ok without providing a
password
5) I get a file save dialogue and pick a filename
6) I enter the PIN a second time
7) the new signed document is open in Okular with a signature stamp and
electronic signature attached to the original PDF.
In my firefox default profile pkcs11.txt, I have at the end:
library=libbeidpkcs11.so.0
name=Belgium eID PKCS#11 module
NSS=slotParams={0x=[slotFlags=PublicCerts ] }
So with this shared library, it seems to work, even though the PIN has to be
entered twice and a document password as well for no obvious reason.
--
You are receiving this mail because:
You are the assignee for the bug.
[okular] [Bug 459173] Cannot use USB smartcard to sign document
https://bugs.kde.org/show_bug.cgi?id=459173 --- Comment #2 from George Diamantopoulos --- I can confirm this also happens under X11. Versions: * KDE Frameworks Version 5.108.0 * plasma-desktop-5.27.6 * okular-23.04.3 * Qt Version 5.15.10 (built against 5.15.10) * wayland-1.22.0 * xorg-server-21.1.8 * poppler-23.07.0 -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 459173] Cannot use USB smartcard to sign document
https://bugs.kde.org/show_bug.cgi?id=459173 George Diamantopoulos changed: What|Removed |Added Platform|Kubuntu |Gentoo Packages Version|22.12.3 |23.04.3 CC||georged...@gmail.com --- Comment #1 from George Diamantopoulos --- Hello, I seem to be facing a similar issue if not the same. Everything works in the same way the OP described, until after the signature rectangle has been drawn. There, instead of being asked for the signature PIN, the okular window enters a "not responding" state and no popup seems to be produced. I'm also using NSS from firefox, with Thales (Gemalto) Safenet 5110 CC with Safenet Authentication Client 10.8 R1 (10.8.1050.0). Similarly, it seems to work OK with firefox. This behaviour is observed under Wayland, I'll try with X11 later and report the result on X11 as well. Thanks! -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 459173] Cannot use USB smartcard to sign document
https://bugs.kde.org/show_bug.cgi?id=459173 Syiad changed: What|Removed |Added Version|22.04.3 |22.12.3 -- You are receiving this mail because: You are the assignee for the bug.
