661aac744c4fd94293cb9f200e71b2bc06ec6605
They were saved only after a successful decryption, in the name of storing proven settings rather than typed ones. The consequence showed up the moment the password did not match: the URL and the token were lost on the next launch, and both had to be typed again - an API URL and forty characters of token, on a phone, on every attempt. A 200 with a container in hand already proves the address and the token. The password is a separate matter, and this call never stored it anyway. So the settings are kept there, before decryption, and the vault plus its fingerprint still wait for a decryption that actually worked. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Description
full local password manager
Languages
Pascal
46.7%
JavaScript
35.4%
HTML
9.4%
CSS
4.9%
PHP
2.1%
Other
1.4%