-
-
Notifications
You must be signed in to change notification settings - Fork 501
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
DietPi-Software | Fails to load global password on Stretch => Buster dist-upgraded systems #2937
Comments
@MattL0 Okay since I don't want to print the encryption keys and stuff here (although it's open source, if one wants to find it 😉), the easiest is:
The issue was that on Buster a new key derivation method is available and if not used, ugly warnings are printed. So some DietPi versions ago we moved Buster systems passwords to the new encryption method. But if you upgrade a system from Stretch to Buster, this is not done, hence DietPi-Software tries to use a key derivation method that does not fit the one of the encrypted password => failure. I will add the ondemand encryption method upgrade to every DietPi-Software and more current DietPi-Update runs. This is actually not a big deal and allows Buster distro-upgrades then. |
thanks :) |
Works perfect * |
@MattL0 |
Out of curiosity:
What where the exact steps (i.e. commands) you used? Did you change anything else apart from sources.list? |
No other step aappart from changing /etc/apt/sources.list.d/raspi.list with buster instead of stretch. also did apt update |
Finished: DietPi-Software will now automatically attempt do decrypt the password with the Stretch method, if it fails on Buster. If this succeeds, it will automatically re-encrypt the password with the Buster method. Will be merged into Beta 6.25.1 |
Creating a bug report/issue
Required Information
#!/bin/bash
G_DIETPI_VERSION_CORE=6
G_DIETPI_VERSION_SUB=24
G_DIETPI_VERSION_RC=1
G_GITBRANCH='master'
G_GITOWNER='MichaIng'
10.0
Linux DietPi-Salon 4.19.50-v7+ #896 SMP Thu Jun 20 16:11:44 BST 2019 armv7l GNU/Linux
RPI3 and RPI3b+
Steps to reproduce
Expected behaviour
Actual behaviour
The text was updated successfully, but these errors were encountered: