Path: csiph.com!eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail
From: pinnerite <pinnerite@gmail.com>
Newsgroups: comp.databases.mysql
Subject: Re: Cannot remove MySQL completely
Date: Thu, 20 Jan 2022 12:44:30 +0000
Organization: A noiseless patient Spider
Lines: 52
Message-ID: <20220120124430.52c6e27199274bc0e5c712cf@gmail.com>
References: <20220117114805.c031fa47fced17cde62197b8@gmail.com> <4789f309-afb4-6231-cadc-2d1a524eee3a@gmx.de> <20220117165750.f8dc48ba66e8fc7513db85f0@gmail.com> <340e9e53-3beb-1f86-531c-27904f871ed1@gmx.de> <20220118124859.8f1c20b86f5722837b1a9d5f@gmail.com> <ss6imb$pn1$1@dont-email.me> <20220118164016.fa5d28bbfaff06ad6db1179c@gmail.com> <ss9f42$ss2$1@dont-email.me>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Injection-Info: reader02.eternal-september.org; posting-host="6968f8c5de0282761697f81d46f3874f"; logging-data="4587"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1+FVudFGcgIvOiMA2EbJFg4pZAO+nKKPHw="
Cancel-Lock: sha1:rIGoMdrkfg6zYkpFRCYwtx3RQSY=
X-Newsreader: Sylpheed 3.7.0 (GTK+ 2.24.32; x86_64-pc-linux-gnu)
Xref: csiph.com comp.databases.mysql:7639

On Wed, 19 Jan 2022 17:43:45 +0100
Axel Schwenke <axel.schwenke@gmx.de> wrote:

> On 18.01.2022 17:40, pinnerite wrote:
> > Axel Schwenke <axel.schwenke@gmx.de> wrote:
> > 
> >> Then let's take a step back. Something must have been broken so that you
> >> started digging into MySQL accounts. What was it? Perhaps a broken (or at
> >> least not up-to-date) mythtv package?
> > 
> > This is the User table prior to wiping out an starting again..
> > +------------------+------------------------------------------------------------------------+-----------+
> > | User             | authentication_string                                                  | Host      |
> > +------------------+------------------------------------------------------------------------+-----------+
> > | mythtv           | *B5BCD029F2268798922CDC55B5253D354B2C0246                              | %         |
> > | debian-sys-maint | $A$005$F5%d'zoHMtJEX88t/x1bvIEMnwtseub5Tc7Z02gRpckab8.tZPnvPL5       | localhost |
> > | mysql.infoschema | $A$005$THISISACOMBINATIONOFINVALIDSALTANDPASSWORDTHATMUSTNEVERBRBEUSED | localhost |
> > | mysql.session    | $A$005$THISISACOMBINATIONOFINVALIDSALTANDPASSWORDTHATMUSTNEVERBRBEUSED | localhost |
> > | mysql.sys        | $A$005$THISISACOMBINATIONOFINVALIDSALTANDPASSWORDTHATMUSTNEVERBRBEUSED | localhost |
> > !ug2Ym[S%/K+ca2n7M06VWGOgOzJFxxKkrg/c7pjNT6Dm3n3FzLXm56 | localhost |
> > | root             | *2B2E29BFA4C432ED2C7C49E07B175220796B98EE                              | localhost |
> > +------------------+------------------------------------------------------------------------+-----------+
> 
> I see nothing wrong here.
> 
> > Nothing I could do would change the erroneous hashed mythtv password nor could I remove the penultimate row with seemingly no user.
> 
> I see no row with no user. I see garbled output for whatever reason. What
> reports SHOW GRANTS ? And the hash for the 'mythtv' user looks ok. And it
> would be a trifle so set it to something else with CHANGE PASSWORD ...
> 
> So you are basically complaining about *nothing*. Or - to be more precise -
> about things that you don't understand and believe to be erroneous.
> 
> <shrug>
> 
> 
> XL

So you know that the hash for 'mythtv' looks OK. It just happens to be the wrong hash.
I could not change it to the correct one. 

So what is the user for: > > !ug2Ym[S%/K+ca2n7M06VWGOgOzJFxxKkrg/c7pjNT6Dm3n3FzLXm56 | localhost |  ?

Anyway it is arbritary as I deleted the database and started again.

Alan


-- 
Mint 20.3, kernel 5.4.0-95-generic, Cinnamon 5.2.7
running on an AMD Phenom II X4 Black edition processor with 16GB of DRAM.