On PostgreSQL instances installed with an older dogu release, the superuser password (dogu config key password) was generated by a doguctl random that used Go's math/rand instead of crypto/rand. The value is predictable rather than random, and it is still in use today.
doguctl was fixed in 0.12.2 and reached this dogu through the base image, but the fix only applies to newly generated passwords. initAdmin in startup.sh runs only on an empty data directory, so an upgrade on its own changes nothing.
Affected values are indistinguishable from safe ones, so the rotation has to happen on every instance regardless of its installed version. The password lives in the database as well, so rotating the dogu config alone would break the login.
On PostgreSQL instances installed with an older dogu release, the superuser password (dogu config key
password) was generated by adoguctl randomthat used Go'smath/randinstead ofcrypto/rand. The value is predictable rather than random, and it is still in use today.doguctlwas fixed in 0.12.2 and reached this dogu through the base image, but the fix only applies to newly generated passwords.initAdmininstartup.shruns only on an empty data directory, so an upgrade on its own changes nothing.Affected values are indistinguishable from safe ones, so the rotation has to happen on every instance regardless of its installed version. The password lives in the database as well, so rotating the dogu config alone would break the login.