public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael <confabulate@kintzios.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] acct-user/man usermod: user 'man' does not exist in /etc/passwd
Date: Thu, 11 Apr 2024 16:41:33 +0100	[thread overview]
Message-ID: <1835615.TLkxdtWsSY@rogueboard> (raw)
In-Reply-To: <f90a9d9c-d15e-4402-780c-dc0741523cfa@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1478 bytes --]

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.

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2024-04-11 15:41 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-11  1:23 [gentoo-user] acct-user/man usermod: user 'man' does not exist in /etc/passwd Dale
2024-04-11  5:22 ` J. Roeleveld
2024-04-11  8:16   ` Dale
2024-04-11  8:52     ` J. Roeleveld
2024-04-11  7:57 ` Michael
2024-04-11  9:22   ` Dale
2024-04-11  9:30     ` Michael
2024-04-11 11:58       ` Dale
2024-04-11 14:52         ` Michael
2024-04-11 15:08           ` Dale
2024-04-11 15:41             ` Michael [this message]
2024-04-12 14:32               ` Dale

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1835615.TLkxdtWsSY@rogueboard \
    --to=confabulate@kintzios.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox