-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
"Bad Signature" error after activating encryption #23078
Comments
I'll take a look. |
In case of a move operation from an unencrypted to an encrypted storage the old encrypted version would stay with "0" while the correct value would be "1". Thus we manually set the value to "1" for those cases. See also #23078
A potential fix for this can be found at #23108. I tested it locally given your steps and did some smoke testing and everything seemed to pass. @mmaedler It would be utmost appreciated if you could retest your steps with this branch applied. It won't get back your old testing data but at least all new one should be there. In case anybody stumbles upon this with real life data, there is this trick that should make the data accessible again:
If you can afford I'd however recommend to restore a backup and retry with the patch applied. Way more reliable. Thanks a lot for reporting this bug back to us and sorry for the hassle! |
Good morning! I went through setting up a fresh installation again, applied the patch, uploaded the same test data like yesterday and now it works :) Thanks for fixing this so quickly! One more question: As I am now getting a notification that the integrity check fails (obviously) I want to wait with updating my production environment until the change made it into a release. Do you have an ETA when that will be available? Also one comment on the interface to change the temp key to the login password again. I think it is not really made clear by the form labels (at least not in the german version) where to put the temp key and where to put the login password. At least the labeling didn't make me feel comfortable that I had chosen the right content for the right field. Maybe it can be made more clearly if the first field is labelled with something like "Temporary Key (you received from your Admin)" or "Temporärer Schlüssel (von deinem Admin)"? Thanks again! |
Thanks @PVince81! As I really want to get going on the new version and beginning of April still feels ages away, is there a way to update the file expected signature value to match the changes and prevent the notification from showing up? |
Option 1: Change Lines 36 to 37 in f818057
Option 2: You could install the daily from https://download.owncloud.org/community/owncloud-daily-stable9.tar.bz2 which is properly signed. This requires however that the PR is first merged into stable9, which it is not yet. Option 3: Ignore the warning. Only admins will see it 😉 |
In case of a move operation from an unencrypted to an encrypted storage the old encrypted version would stay with "0" while the correct value would be "1". Thus we manually set the value to "1" for those cases. See also #23078
In case of a move operation from an unencrypted to an encrypted storage the old encrypted version would stay with "0" while the correct value would be "1". Thus we manually set the value to "1" for those cases. See also #23078
To do a bulk fix, I used this Mysql query: update oc_filecache set encrypted = 1 where storage = '1' AND encrypted=0 AND mimetype != '2' and PATH LIKE "files/%" (mimetype 2 are directories) All my files except versioned files then started to get decrypted again just fine. It's quite a mess! Can someone confirm in which version this is being fixed? and which steps I have now to do from this state? At which version I can safely run occ encrypt:decrypt-all again? Thanks, |
Steps to reproduce
Expected behaviour
Unencrypted version of file should be shown (incl. thumbs for images).
Actual behaviour
Every file returns "Bad Signature" error
Server configuration
Operating system: Ubuntu 12.04
Web server: nginx 1.8.1
Database: MySQL 5.6.24
PHP version:: 5.6.18 (as fpm)
ownCloud version: 9.0.0
Updated from an older ownCloud or fresh install: first updated version, then fresh install — behaviour is the same each time
Where did you install ownCloud from: zip file
Signing status (ownCloud 9.0 and above):
List of activated apps:
The content of config/config.php:
Are you using external storage, if yes which one: no
Are you using encryption: yes (at least kind of...)
Are you using an external user-backend, if yes which one: no
Client configuration
Browser: Chrome 49
Operating system: OSX 10.11.3
The text was updated successfully, but these errors were encountered: