Mysql your password does not satisfy the current policy requirements
=> http://diadephotic.nnmcloud.ru/d?s=YToyOntzOjc6InJlZmVyZXIiO3M6MjE6Imh0dHA6Ly9iaXRiaW4uaXQyX2RsLyI7czozOiJrZXkiO3M6Njg6Ik15c3FsIHlvdXIgcGFzc3dvcmQgZG9lcyBub3Qgc2F0aXNmeSB0aGUgY3VycmVudCBwb2xpY3kgcmVxdWlyZW1lbnRzIjt9
It seems buggy in that it checks for dictionary words for a regular mysql user but ignores the same word for the mysql root user. The root user gets all the privileges by default. The policies implement increasingly strict password tests.
Sounds like you need to start over with the Ubuntu server install. Added new User check functionality. There you were asked for to validate password strength when creating new user or changing for existing user. This will fix my main reason for submitting this bug report, however it could affect other packages.
Error Your Password does not satisfy the Current Policy Requirements One can set many variables for validating a password. Start-up options can be read from these file. It looks like an upstream decision as there is no reference to the variable outside the upstream tarball. Thanks for the suggestion, Barry. I have found that if a now invalid root password exists prior to upgrade it will continue to work. The function takes a password argument and returns an integer from 0 weak to 100 strong. Following command is used in my. When i create the password, i am given a 100% mark. I am stumped and cannot get any further in install.
〜初心者の気まぐれメモ〜: mysqlのパスワード変更ができない！！！ - Nupur Dave is a social media enthusiast and an independent consultant.
This has broken the zoneminder 'zmsetup' script as previously the password strength was not an issue. As far as I can tell from querying mariadb there is no password verification plugin enabled, so where has this change in cauldron come from. Version-Release number of selected component if applicable : How reproducible: Steps to Reproduce: 1. It looks like an upstream decision as there is no reference to the variable outside the upstream tarball. It seems buggy in that it checks for dictionary words for a regular mysql user but ignores the same word for the mysql root user. Also it appears to get the character count wrong depending on the text included, however testing gets very frustrating without any written policy to test against. Anyhow, do we really need to have this feature enabled by default. If not, can it be changed in our my. Also if a system is upgraded from Mga5 where this was not implemented, will passwords fail after upgrade. I have tested an upgrade from Mageia5 to Cauldron with the new version of zoneminder and the upgrade does go smoothly with the old mysql root password. This will fix my main reason for submitting this bug report, however it could affect other packages. My experience indicated it does check new root user pw. Going to depend on what is being done. Found out about new pw requirements, finally managed to change mysql root password, modified passwords to match new pw policy, loaded my mythtv database and was no longer able to login as root. I have found that if a now invalid root password exists prior to upgrade it will continue to work. Also if logged in as mysql root another now invalid root password may be set. If mysql your password does not satisfy the current policy requirements of any use to you I have a bash function to check passwords in zmsetup: chkpass. It seems that length is checked to be min of 8 Numbers, upper case and special characters seem to not be tested for. Dictionary words seem to be checked sometimes and possibly for a limited selection of words and then only when at the start of the password. For passwords to be accepted they need to pass the cracklib-check test. The following code snippet will do this for any intended password. Thanks for the suggestion, Barry.
