Re: Beowulf/Buster upgrade - sudoers list - password problems

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sat, 29 Aug 2020 01:28:56 -0700
"William Morder via trinity-users" <trinity-users@xxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

> On Saturday 29 August 2020 01:10:15 Dr. Nikolaus Klepp wrote:
> > Hi Bill!
> >
> > Anno domini 2020 Fri, 28 Aug 17:06:31 -0700
> >
> >  William Morder via trinity-users scripsit:  
> > > Okay, so a new thread, as things have changed and progressed somewhat,
> > > but now I have new problems.
> > >
> > > I got my system restored *almost* to how I want it, but some things have
> > > changed in my system, and I did not make those changes.
> > >
> > > #1 - When installing, I deliberately chose *not* to set a root password;
> > > since nobody else ever gets to touch my system, it is enough that my user
> > > password is granted root privileges when I use sudo or su.  
> >
> > Always set a root password, even it's 123456789. Not all programs accept
> > root without password.  
> 
> Yeah, I tried that, but I always end up with this same problem. When I tried 
> setting a root password before (because it always seemed like the *right* 
> answer), I got this same result. 
> 
> When I made the move from Kubuntu to Debian, I went through this root-password 
> thing at least 5 or 6 times. I always ended up with a system where I could 
> not be granted admin or root privileges ... EXCEPT in a sudo su shell! So 
> that's what I usually do: I create a sudo su shell, then exit and allow 
> permissions to expire, then when I need quick access again, I just hit my UP 
> arrow key, re-enter password, and go back into sudo su to kill something or 
> whatever else needs immediate attention. 
> 
> Now, it would be nice to crack this nut, once and for all, but I don't want to 
> keep asking my own machine for permission to do things. The question is, 
> which of us is master? 

Let me ask a question that may sound rather odd at first:  Why do you have
sudo installed at all?  It doesn't offer much in the way of security improvement
in a typical one-person home-LAN setup (in fact, if you don't take the time to
configure it properly, you might even get negative security out of it).  Is having 
to type in logins slightly less often really worth the extra opacity?  Or is this a 
Debian thing, as the problem with starting GUI packages from the command
line as root seems to be?

(Note that I'm not against sudo in general—there are good use cases for it,
but they're in larger environments with a sysadmin who takes the time to
curate /etc/sudoers and related files and make sure every account has exactly
the access it needs and no more.)

E. Liddell

---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-users-unsubscribe@xxxxxxxxxxxxxxxxxxxxxxxxxx
For additional commands, e-mail: trinity-users-help@xxxxxxxxxxxxxxxxxxxxxxxxxx
Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/
Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting





[Index of Archives]     [Trinity Devel]     [KDE]     [Linux Sound]     [ALSA Users]     [ALSA Devel]     [Linux Audio Users]     [Linux Media]     [Kernel]     [Gimp]     [Yosemite News]     [Linux Media]     [Trinity Desktop Environment]

  Powered by Linux