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
blowfish_secret of not exactly 32 characters causes server error #17369
Comments
Hi, I'm using a 93 chars secret, and I'm also having this problem. 5.2.0 just updated from 5.1.3. |
Is there a reason it needs to be exactly 32 characters long? Surely a longer key is more secure? |
Seems like this is a technical issue from the php extension: https://www.php.net/manual/en/function.sodium-crypto-secretbox.php
|
We just updated phpMyAdmin on one of our staging servers to phpMyAdmin 5.2. No further errors are logged or thrown. So except this confusing error phpMyAdmin works fine. I see this was changed in this commit: 411bacf If it actually should always be 32 bit length I think this should be improved in the documentation.
|
any News about this? |
I agree it should be re-phrased A longer key will not be more secure because the software will not accept it |
I generated secret using
i am still getting error. PS. |
it worked thanks bro!! |
I find a probably better solution is to do something like the following, so it is still a proper 32-byte key.
But I think it should be more user-friendly. |
Related to phpmyadmin/phpmyadmin#17369 Signed-off-by: Maurício Meneghini Fauth <mauricio@fauth.dev>
yaa, in v5.2 its getting error |
try the latest 5.2 version in development (phpMyAdmin 5.2+snapshot) ;) |
Thanks for that, worked great! |
QA_5_2 and master have a problem if blowfish_secret isn't exactly 32 bytes long. The main pane is blank aside from the top tabs and this is logged:
We should definitely handle this more gracefully and show the user a warning that their blowfish_secret isn't the correct length.
The text was updated successfully, but these errors were encountered: