open-eid / gentoo

Gentoo ebuild (community provided)
10 stars 14 forks source link

"Server access certificate expired on ." error when signing with ID card #67

Open jaakristioja opened 3 months ago

jaakristioja commented 3 months ago

Using app-crypt/qdigidoc4-4.3.0 I'm getting the following error message, when trying to sign an asice container using Estonian ID card: Server access certificate expired on . To renew the certificate please contact IT support team of your company. Additional information is available [sales@sk.ee](mailto:sales@sk.ee) or phone (+372) 610 1885.

image

What is this about? I'm a private person with no company and have no IT support team to contact. Please help.

Also note that the message seems to be missing the expiration date.

metsma commented 3 months ago

Server access certificate expired. One option is to use in settings dialog disable server access certificate. Or upgrade to 4.4.0

jaakristioja commented 3 months ago

First, this Gentoo overlay does not yet support 4.4.0.

Second, does upgrading to 4.4.0 have the exact same effect as disabling server access certificate or does it do something else?

Third, when I navigate to Settings -> Signing Services, mark the "Ignore server access certificate (IP based access)" checkbox and click "Close" (as there is no separate "Apply changes" or "Save settings" button), it still gives me the same error. When I navigate back to settings, the checkbox is shown unmarked.

metsma commented 3 months ago

I think there is PR #65 and the Gentoo overlay is community maintained repository. The server access certificate was removed in DigiDoc 4.4.0. I think it is possible to disable in digidocpp.conf file this also https://github.com/open-eid/libdigidocpp/blob/v3.14.12/etc/digidocpp.conf.cmake#L26

jaakristioja commented 3 months ago

This overlay only provides dev-libs/libdigidocpp-3.16.0 and this option seems to be gone in https://github.com/open-eid/libdigidocpp/blob/v3.16.0/etc/digidocpp.conf.cmake so I presumed that it would not work and did not test it.

Upgrading to qdigidoc4 to 4.4.0 using the ebuild from PR #65 seems to be a valid workaround thou. I suppose this issue can be closed after #65 is merged. Thanks! 😃