Trisquel's payment-auto-fill does not work properly
- Login o registrati per inviare commenti
I have been using Trisquel 11 since its launch, and Trisquel's payment-auto-fill never worked properly. On the same OS on the same machine, I tried the same operation in Firefox of the corresponding version, and it worked perfectly. So I am sure it is an issue of Trisquel.
I think it is either a configuration defect or a defect that is related to the Default keyring's associated "Firefox Encrypted Storage".
I believe more users have encountered this issue. Today I have some time to report the issue. Let's see if anyone can help.
SYMPTOM
The auto-filled payment card number is always empty.
STEPS TO REPRODUCE THE ISSUE
Step 1: In Trisquel, open a payment Web page, select a saved payment method to fill the HTML element, expecting the card number to be filled correctly.
Step 2: MATE desktop pops up a modal dialog box, saying ‘An application wants to access the keyring "Default keyring", but it is locked.’. Input the Default keyring password.
Now the modal dialog box disappears, and the auto-fill completes with an empty card number in the HTML element.
Step 3: In Trisquel's Setting > Privacy & Security > Saved Payment Methods, check the saved payment methods. They are all there but the card numbers are all missing, the other fields are good.
| Allegato | Dimensione |
|---|---|
| Screenshot at 2024-11-11 09-56-28.png | 21.98 KB |
| Screenshot at 2024-11-11 09-57-20.png | 26 KB |
When you read my post, please replace "Trisquel" with "Abrowser" in your mind. I meant "Abrowser" when I was typing "Trisquel".
UPDATE:
I checked the file ‘~/.mozilla/abrowser/py6nefmq.default-release/autofill-profiles.json’ ($HOME/.mozilla/abrowser/$MY_ACTIVE_PROFILE/autofill-profiles.json), and find all the encrypted card numbers in the field ‘cc-number-encrypted’.
I also found the corresponding autofill-profiles.json in the firefox folder ‘~/.mozilla/firefox/’.
It means that the information is stored properly, but somehow Abrowser cannot decrypt them properly or cannot read them properly.
It might be that credit card payment autofill is not built into Abrowser, since Abrowser is a privacy focused fork of Firefox with a lot of changes built in to deal with Firefox's many privacy problems.
From my way of thinking (and I'm not saying you have to see it the same way I do), browsers should not be keeping people's payment info. I see it as a big privacy risk - you may have good reasons to disagree however.
OK. I will open an issue. Thank you, Ark74!