Worded for an itsme activation

[Malwprotector]

Hello,
This worked in chrome for an itsme activation (didn't with firefox, I don't know why but it's probably because of my odd firefox setup).
Just had to rename connective plugin path inside the generated json file because the path contained accents and they were shown with hexadecimal values, so I edited ~/.config/google-chrome/NativeMessagingHosts/com.connective.signer.json
from
/home/user/T\u00e9l\u00e9chargements/connective-plugin-linux-main/connective-backend.py
to
/home/user/Téléchargements/connective-plugin-linux-main/connective-backend.py
And it worked.

Thanks you very much for this script, this is so weird that the developers at itsme aren't capable of designing a system with add-on programs that run on linux (Connective Browser Package 🤡).

Here's the config I used :

Card Reader : Alcor Micro AU9540 00 00 (Integrated Card Reader)
OS : Linux Mint 21.3 / kernel 5.15.0-131-generic
Chrome version 133.0.6943.53
eid-mw version 5.1.15
pcsc-lite version 1.9.5

Best regards.

[roelderickx]

Just had to rename connective plugin path inside the generated json file because the path contained accents and they were shown with hexadecimal values, so I edited ~/.config/google-chrome/NativeMessagingHosts/com.connective.signer.json from /home/user/T\u00e9l\u00e9chargements/connective-plugin-linux-main/connective-backend.py to /home/user/Téléchargements/connective-plugin-linux-main/connective-backend.py And it worked.

This is an interesting observation, I'll create an issue in nativemesaging-ng to see if it can be corrected.

Thanks you very much for this script, this is so weird that the developers at itsme aren't capable of designing a system with add-on programs that run on linux (Connective Browser Package 🤡).

The irony is that you're signing a document using the connective plugin to be able to sign documents using itsme. Which is limited to smartphones, and as such defective in the same way as the connective plugin.