Signature configuration not working any more. What should I update? #310
-
Using pyhanko version 0.15.0 the following command line worked perfectly:
On the other other hand, there is a line in the manual that says those things should go into the configuration (yml) file, but I could not find how to do it. Any hints will be much appreciated. EDIT:
Nevertheless, when I use the --p11-setup argument, I got the error message:
=== Is let it known that when I downgraded pyhanko to version 0.15.1 it started working again. So, most likely, it has to do with a intentional change in the way command line parameters are read. Nevertheless, I have not been able to figure that out from the documentation (the last version at readthedocs).
|
Beta Was this translation helpful? Give feedback.
Replies: 3 comments
-
Hi @Fernando-Cabral, Are you sure you have installed pyHanko with the I should try to come up with a more user-friendly way to get Click to identify the pkcs11 command as something only exposed if optional deps are available. |
Beta Was this translation helpful? Give feedback.
-
@matthias, unfortunately I am completely confused. After installing and uninstalling different versions, the newest (0.20.1) started working with the same configuration as the old one. Unfortunately, I have not been able to identify what the problem was. Anyway, the good news is that the newest version is working as before. But there is still something I do not understand: I tried to replicate the installation in another new machine. This time the trick of installing/removing different versions till it worked did not work! Just in case you want to take a look in the new error messages:
The token is the same as in the other machine and the environment is supposed to be exactly the same (Debian 12 recently installed with the same packages)... |
Beta Was this translation helpful? Give feedback.
-
Sorry, @matthias, as soon as I posted the above answer I found the problem: pcscd and libccid, for some reason, were not running. So, it was entirely my fault. So, now version 0.20.0 is working in both machines. Thank you for your kind attention. |
Beta Was this translation helpful? Give feedback.
@matthias, unfortunately I am completely confused. After installing and uninstalling different versions, the newest (0.20.1) started working with the same configuration as the old one. Unfortunately, I have not been able to identify what the problem was. Anyway, the good news is that the newest version is working as before.
But there is still something I do not understand: I tried to replicate the installation in another new machine. This time the trick of installing/removing different versions till it worked did not work!
Just in case you want to take a look in the new error messages: