Bug #2166
nm-strongswan stores the PIN when using smartcard authentication
Status:
Closed
Priority:
Normal
Assignee:
Category:
networkmanager (charon-nm)
Target version:
Start date:
03.11.2016
Due date:
Estimated time:
Affected version:
5.5.1
Resolution:
Fixed
Description
Quoting from the attached patch:
The secret storage flag wasn't being saved when using smartcard
authentication, resulting in the PIN being stored.
The patch fixes it by storing the flags, but it doesn't clear any stored PIN.
Associated revisions
History
#1 Updated by Tobias Brunner over 5 years ago
- Tracker changed from Issue to Bug
- Status changed from New to Closed
- Assignee set to Tobias Brunner
- Target version set to 5.5.3
- Start date set to 03.11.2016
- Resolution set to Fixed
Sorry for missing this. I can't really reproduce what you are seeing. Instead, in my tests if I didn't set the flag the entered password somehow got lost and I always received a final secrets request failed to provide sufficient secrets
errors. Anyway, setting the flag somehow seems to fix that too. Applied to master, thanks!
nm: Explicitly prevent the smartcard PIN from being stored
The secret storage flag wasn't being saved when using smartcard
authentication, resulting in the PIN being stored.
Fixes #2166.