Michael wrote: > On Thursday, 11 April 2024 16:08:54 BST Dale wrote: > >> I don't recall editing this file ever. From my understanding, commands >> are used to manage that file. I can't say for sure but it's doubtful I >> edited that file. >> >> I can easily do a emerge -ek world if you think it would be wise to do >> so. I guess that would reset ownership of files as it reinstalls. >> Thoughts? >> >> Thanks. >> >> Dale >> >> :-) :-) > > I can't really advise what to do, it depends on your level of concern about > this discrepancy with the 'man' account. The question to mull over is what > could a rogue 'man' account have changed since your last full emerge @world? > > If you upgraded your profile from 17.1 to 23.0 recently you would have re- > emerged @world, so all packages would have been reinstalled. If you run find > to print recently changed files since the profile upgrade, you'll have some > pointers for packages to emerge again. Or, with the 'man' account safely > back > in its box you can change passwds/keys and re-emerge the whole @world once > more. > > If you are totally worried to the point of not being able to trust your > system, then you'll need to reformat and start with a fresh stage3 download > and fresh sources. Do not blindly copy all your configuration files from the > backups, but diff them to make sure only changes you approve make it into the > new system. This can be a lot of work, which you may not be inclined to > embark on and could potentially be an overkill.
I guess I'll see what it does moving forward. I have to admit tho, I wonder how it got changed to begin with. Certainly odd. I wonder if I typed something in my mistake?? Anyway, time will tell. I'm behind a VPN and pretty good router so maybe that will be enough. Thanks. Dale :-) :-)
