-
Notifications
You must be signed in to change notification settings - Fork 213
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Integrity Check Failed when trying to copy password #767
Comments
Hi,
Newly created accounts work fine since you're encrypting them with the "good" key (but it doesn't need to be the correct one) Greetings |
Thanks for the prompt reply. Yes I am actually using a non-LDAP user (admin) to do this and it fails for existing accounts. Yes the master password (not key) was changed on multiple occasions. |
Here you have a piece of code that would show the current master password used by the user logged in: https://gist.github.com/nuxsmin/ca59f3754312fb6d54b2cf45283bf754 This file is placed within Debug data will be only displayed to application admin users. |
DEBUG showed the same master password (non LDAP admin) as the one currently configured on the system. |
syspass.log now I see (although some days old):
|
Ummm, what version was running when the upgrade process took place?. Please let me know the steps you followed before you noticed the passwords were wrong. Regards. |
I didn't do any update. This is why I am surprised to see this in log file. When I initially installed syslog and logged in for the first time I did receive an upgrade message, which I followed. All accounts however have been created after that. Then they worked for about a day. When I came back to the portal to add a few additional ones and integrate with LDAP I noticed the error. |
I have just reinstalled syspass. Essentially downgraded to 2.1.6 as I noticed similar fixes in that one. I have then imported the old accounts that were created in 2.1.13. Result is exactly the same.
|
I have installed latest version today and recreated all accounts from scratch. Integrated with LDAP. So far it is working fine but I am really not happy about this. I still get sporadic errors that it is unable to copy password when using the button Copy to Clipboard. |
Hi, I take your points and those "Copy to Clipboard" errors are related to a browser security restriction. See #739 This issue is quite weird, since I've never received those upgrading messages when the application wasn't updated. I think there's something missing on the upgrade process, because the passwords seems to be encrypted with a different master password ("Integrity check failed." messages). Greetings |
Does that mean if I switch off encryption and implement HTTPS (still running on plain HTTP) it will not happen? |
No, encryption is always performed, so regardless the http protocol used, your data will be always encrypted. It means that copy to clipboard though the direct icon could fail because a browser security behaviour, since the app will retrieve the data from the server using an Ajax request and browsers don't like to copy data to clipboard from an Ajax request , so if it takes too much time to get the data it could fail. Greetings |
Thanks for info. Is there a way around this or are there any plans to overcome it? |
Hmmm, there's a W3C draft in which web browser would implement a trusted asynchronous clipboard API, but currently it isn't implemented yet: https://www.chromestatus.com/feature/5861289330999296 |
Hi,
I am getting
when attempting to view or copy passwords. I found that if I duplicate the account the new account (no changes) is working just fine. I then tried to export, delete and import back the accounts with no success.
This is not an update, it is a fresh install:
syspass version
database version
php version
syspass.log
I went through all issues with same error message but none of those seem related to me. This was working fine for a day and then just stopped working. The only noticeable change on the system at that time was integration with LDAP.
Greetings!
Stan
The text was updated successfully, but these errors were encountered: