[mythtv-users] About updating from Ubuntu 24.04 to 26.04

[Bill Meek]

On Wednesday 06 May 2026 04:26:21 PM (-05:00), Roland Ernst wrote:






On Wed, May 6, 2026 at 11:13 PM Will Dormann <wdormann at gmail.com <mailto:wdormann at gmail.com> > wrote:

On 5/6/26 4:56 PM, Roland Ernst wrote:

> Thus said, your installation of MySQL looks good to me.

Oh, so no need to change anything?  "Ouch!  This really needs fixing."
and "looks good to me" seem to be on opposite ends of the spectrum.


> One question:
> Did you enable the ppa for MythTV v36 (ppa:mythbuntu/36 <https://
> launchpad.net/~mythbuntu/+archive/ubuntu/36 <http://launchpad.net/~mythbuntu/+archive/ubuntu/36> >) after the upgrade and did
> you a `sudo apt-get dist-upgrade`?
> This may answer the question Bill is hunting for. ;-)


No, I didn't do any PPA stuff after the upgrade.  I see evidence of
there being PPAs used in the semi-distant past, but it looks like I'm
just using the MythTV version that comes with the distro:

...

-WD




Will,
I run a similar MySQL setup for years. I had no need to fix anything.
The problem is for me to remember the mysql root password :-)


Let us wait what Bill suggest. He is the author of the changes for the upgrade.


Roland


Hi Roland,


Here's what I've learned while working with the root SQL login process:


1. In MySQL, the mysql_native_password is going away. That is the original
issue I was trying to solve. And it's done for a new MythTV install. I haven't figured out
where to switch to the new (and default) caching_sha2_password for existing
users. At some point, if the native plugin goes away, access to the MythTV
DB would be lost. MariaDB continues to use the native password although
they claim to allow the caching one, but only for conversions, so I'm not
changing anything with MariaDB in our packaging.


2. /etc/mysql/debian.cnf is one old way of gaining access to the root SQL user
on both MySQL and MariaDB systems. In Ubuntu 26.04 with MariaDB, this
text appears in that file (the whole file is attached).


    # THIS FILE IS OBSOLETE. STOP USING IT IF POSSIBLE.
    # THIS FILE WILL BE REMOVED IN A FUTURE DEBIAN RELEASE.


I think that means that our Debian packaging should stop using this method.
And that's the only way Will was able to login to MySQL as a root user in a
previous message in this thread.


3. I agree with your observation about remembering the SQL root user's
password. The auth_socket plugin removes that issue, although it requires
that the login be done on the same host (localhost) that the DB server lives
on. I don't know why most of my hosts have a root user with auth_socket.
The one that doesn't still allows the sudo mysql login method.


4. I can't recommend the change to everyone yet, but here's how to do it (likely
that the ALTER USER method is all that's required):


   https://dev.mysql.com/doc/mysql-secure-deployment-guide/8.0/en/secure-deployment-configure-authentication.html


Roland, would you please post your output of these:


    SELECT PLUGIN_NAME, PLUGIN_STATUS FROM INFORMATION_SCHEMA.PLUGINS WHERE PLUGIN_NAME LIKE '%socket%';
    SELECT User,Host,plugin,RIGHT(HEX(authentication_string),22) AS authentication_string FROM user;


Thanks,


-- 
Bill
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20260507/75371cf3/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: debian.cnf
Type: application/octet-stream
Size: 546 bytes
Desc: not available
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20260507/75371cf3/attachment.obj>