<html><head></head><body><span class="viv-signature"></span>On Wednesday 06 May 2026 04:26:21 PM (-05:00), Roland Ernst wrote:<br><br><blockquote style="margin: 0 0 0.80ex; border-left: #0000FF 2px solid; padding-left: 1ex"><div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Wed, May 6, 2026 at 11:13 PM Will Dormann <<a href="mailto:wdormann@gmail.com">wdormann@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="padding-left:1ex;border-left-color:rgb(204, 204, 204);border-left-style:solid;border-left-width:1px;margin-left:0.8ex;margin-bottom:0px;margin-right:0px;margin-top:0px;">On 5/6/26 4:56 PM, Roland Ernst wrote:<br>
<br>
> Thus said, your installation of MySQL looks good to me.<br>
<br>
Oh, so no need to change anything? "Ouch! This really needs fixing." <br>
and "looks good to me" seem to be on opposite ends of the spectrum.<br>
<br>
<br>
> One question:<br>
> Did you enable the ppa for MythTV v36 (ppa:mythbuntu/36 <https:// <br>
> <a href="http://launchpad.net/~mythbuntu/+archive/ubuntu/36" rel="noreferrer">launchpad.net/~mythbuntu/+archive/ubuntu/36</a>>) after the upgrade and did <br>
> you a `sudo apt-get dist-upgrade`?<br>
> This may answer the question Bill is hunting for. ;-)<br>
<br>
<br>
No, I didn't do any PPA stuff after the upgrade. I see evidence of <br>
there being PPAs used in the semi-distant past, but it looks like I'm <br>
just using the MythTV version that comes with the distro:<br>
<br>...<br>
<br>
-WD<br><br></blockquote><div><br></div><div>Will,</div><div>I run a similar MySQL setup for years. I had no need to fix anything.</div><div>The problem is for me to remember the mysql root password :-)</div><div><br></div><div>Let us wait what Bill suggest. He is the author of the changes for the upgrade.<br><br></div><div>Roland</div></div></div></blockquote><span class="viv-signature-below"><div><span class="viv-signature-below"><br></span></div><div><span class="viv-signature-below">Hi Roland,</span></div><div><span class="viv-signature-below"><br></span></div><div><span class="viv-signature-below">Here's what I've learned while working with the root SQL login process:</span></div><div><span class="viv-signature-below"><br></span></div><div><span class="viv-signature-below">1. In MySQL, the mysql_native_password is going away. That is the original</span></div><div><span class="viv-signature-below">issue I was trying to solve. And it's done for a new MythTV install. I haven't figured out</span></div><div>where to switch to the new (and default) caching_sha2_password for existing</div><div>users. At some point, if the native plugin goes away, access to the MythTV</div><div>DB would be lost. MariaDB continues to use the native password although</div><div>they claim to allow the caching one, but only for conversions, so I'm not</div><div>changing anything with MariaDB in our packaging.</div><div><br></div><div>2. /etc/mysql/debian.cnf is one old way of gaining access to the root SQL user</div><div>on both MySQL and MariaDB systems. In Ubuntu 26.04 with MariaDB, this</div><div>text appears in that file (the whole file is attached).</div><div><br></div><div> # THIS FILE IS OBSOLETE. STOP USING IT IF POSSIBLE.</div><div> # THIS FILE WILL BE REMOVED IN A FUTURE DEBIAN RELEASE.</div><div><br></div><div>I think that means that our Debian packaging should stop using this method.</div><div>And that's the only way Will was able to login to MySQL as a root user in a</div><div>previous message in this thread.</div><div><br></div><div>3. I agree with your observation about remembering the SQL root user's</div><div>password. The auth_socket plugin removes that issue, although it requires</div><div>that the login be done on the same host (localhost) that the DB server lives</div><div>on. I don't know why most of my hosts have a root user with auth_socket.</div><div>The one that doesn't still allows the sudo mysql login method.</div><div><br></div><div>4. I can't recommend the change to everyone yet, but here's how to do it (likely</div><div>that the ALTER USER method is all that's required):</div><div><br></div><div> https://dev.mysql.com/doc/mysql-secure-deployment-guide/8.0/en/secure-deployment-configure-authentication.html</div><div><br></div><div>Roland, would you please post your output of these:</div><div><br></div><div> SELECT PLUGIN_NAME, PLUGIN_STATUS FROM INFORMATION_SCHEMA.PLUGINS WHERE PLUGIN_NAME LIKE '%socket%';</div><div> SELECT User,Host,plugin,RIGHT(HEX(authentication_string),22) AS authentication_string FROM user;</div><div><span class="viv-signature-below"><br></span></div><div><span class="viv-signature-below">Thanks,</span></div><div><span class="viv-signature-below"><br></span></div>-- <br>Bill</span></body></html>