Repository navigation
occ encryption:scan:legacy-format not available at 20.0.3 #24681
Description
Activity
- added0. Needs triagePending check for reproducibility or if it fits our roadmapPending check for reproducibility or if it fits our roadmap
on Dec 13, 2020 - changed the title
[-]occ encryption:scan:legacy-format not availabel at 20.0.3[/-][+]occ encryption:scan:legacy-format not available at 20.0.3[/+]on Dec 13, 2020 https://github.com/nextcloud/documentation/ is the repository for the documentation.
However the command name is correct
server/apps/encryption/lib/Command/ScanLegacyFormat.php
Lines 73 to 77 in adc0012
protected function configure() { $this ->setName('encryption:scan:legacy-format') ->setDescription('Scan the files for the legacy format'); } but the command is only loaded if the encryption app is enabled. The warning is shown if encryption.legacy_format_support in your config.php is true. That's usually the case if the encryption app was enabled during the update and old key format use.
I guess if you enable the encryption app you can run the command. We should probably check if the app is enabled in the setup check.
Reacted by JeffI disabled the app I guess at some early 19.0.x (or even 18.0.x) state due to regular data loss. So this actually was not done by the update 19->20. However, I support the idea to consider whether he app is activated at all at this point.
Reacted by danielbSame here, my Encryption app is disabled since ages/versions ago (also was never used). I followed the yellow warning in admin page to docs, to the "unknown command" error, to this issue...
Reacted by Keunes, dryo and Lukas MartiniSame here, I never used encryption before and I started to get the warning after upgrading to v20 without possibility to scan my files because, as mentioned before, the module isn't enabled in my setup.
@danielb42 I just switched the legacy setting encryption in my config.php to false to get rid of the warning. Hope it helpsSame thing happens here on 20.0.3 after upgrading from 19.0.6. The documentation should be updated with a working how-to.
Also please update the documentation. I don't understand currently which kind of encryption is deprecated and if and how it potentially impacts me
Reacted by ape_lithium, Richard Rondu, Psyray, roboticsalign, Der Mundschenk & Compagnie, sery-cat, BiasF, Daniel Lerch, Omur Ozbahceliler, mwillig and 8 moreI get this error in NC 21.
I enabled the encryption module and ran
occ encryption:scan:legacy-format
It said: "All scanned files are properly encrypted. You can disable the legacy compatibility mode."
I then disabled the encryption module app and the server still said:
"The old server-side-encryption format is enabled. We recommend disabling this. For more details see the documentation."Then I ran
occ encryption:disable
It said "Encryption is already disabled"So I don't know why the server still complains about it.
Reacted by MichaelA friendly guy from a reddit forum has shown a way to get rid of the message: (https://www.reddit.com/r/NextCloud/comments/jyej7d/issue_with_occ_encryptionscanlegacyformat_command/)
- make sure you are not using the legacy encrytion with:
occ encryption:status - change the following parameter inside the config.php (should be in your nextcloud folder; e.g. /var/www/nextcloud/config/config.php) to false:
'encryption.legacy_format_support' => false,
- make sure you are not using the legacy encrytion with:
Is this Issue still valid in NC21.0.3? If not, please close this issue. Thanks! :)
- ghost addedstaleTicket or PR with no recent activityTicket or PR with no recent activity
on Aug 1, 2021 occ encryption:scan:legacy-format
Should be removed from the documentation, as the command is not longer available.
https://docs.nextcloud.com/server/22/admin_manual/configuration_files/encryption_migration.html
This issue is still here.
This page is wrong: https://docs.nextcloud.com/server/24/admin_manual/configuration_files/encryption_migration.html
the commandocc encryption:scan:legacy-formatdoes not work.Reacted by WalterCool and Fer
How to use GitHub
Steps to reproduce
Expected behaviour
Documentation tells a valid command
Actual behaviour
Command mentioned in documentation does not exist
Server configuration
Operating system:
Web server:
Database:
PHP version:
Nextcloud version: (see Nextcloud admin page)
Updated from an older Nextcloud/ownCloud or fresh install:
Where did you install Nextcloud from:
Signing status:
Signing status
List of activated apps:
App list
Nextcloud configuration:
Config report
Are you using external storage, if yes which one: local/smb/sftp/...
Are you using encryption: no (turned off after repeatly loosing data due to other bugs
Are you using an external user-backend, if yes which one: no
Client configuration
Browser:
Operating system:
Logs
Web server error log
Web server error log
Nextcloud log (data/nextcloud.log)
Nextcloud log
Browser log
Browser log