From: Philip Webb <purslow@ca.inter.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Rooted/compromised Gentoo, seeking advice
Date: Mon, 9 Aug 2010 17:17:49 -0400 [thread overview]
Message-ID: <20100809211749.GF4258@ca.inter.net> (raw)
In-Reply-To: <AANLkTi=NSPKR50LCC5T2qqL8WWmBjGCneGAp_r20+xNy@mail.gmail.com>
100809 Robert Bridge wrote:
> On Mon, Aug 9, 2010 at 8:09 PM, Mick <michaelkintzios@gmail.com> wrote:
>> There have been discussions on this list why sudo is a bad idea
>> and sudo on *any* command is an even worse idea.
>> You might as well be running everything as root, right?
> sudo normally logs the command executed and the account which executes it,
> so while not relevant for single user systems,
> it STILL has benefits over running as root.
I follow 2 simple rules:
(1) never start X as root -- I open in a raw terminal, then 'startx',
so it's ok to login there as root to get some system fixes done,
but of course logout again before starting X as user --
& (2) do all system stuff in a virtual root terminal on its own desktop,
where the prompt says 'root' in red letters & the background is black
(my user terminal has a white background): that's down in the basement,
where all the pipes & wires are & you need a hard hat & safety boots
& you need to unlock the basement door, whose key is the root password.
also, my user terminal says :
524: gx> which sudo
which: no sudo in (/sbin:/usr/sbin:/usr/local/sbin::/bin:/usr/bin:/usr/local/bin:/usr/kde/3.5/bin)
--
========================,,============================================
SUPPORT ___________//___, Philip Webb
ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto
TRANSIT `-O----------O---' purslowatchassdotutorontodotca
next prev parent reply other threads:[~2010-08-09 21:18 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-09 16:25 [gentoo-user] Rooted/compromised Gentoo, seeking advice Paul Hartman
2010-08-09 16:48 ` Alan McKinnon
2010-08-09 18:48 ` Paul Hartman
2010-08-09 18:59 ` [gentoo-user] " 7v5w7go9ub0o
2010-08-09 19:08 ` Paul Hartman
2010-08-09 19:46 ` Mick
2010-08-10 13:50 ` Kyle Bader
2010-08-09 19:09 ` [gentoo-user] " Mick
2010-08-09 20:08 ` Robert Bridge
2010-08-09 20:20 ` Bill Longman
2010-08-10 0:30 ` Kevin O'Gorman
2010-08-10 1:18 ` William Hubbs
2010-08-10 6:42 ` Alan McKinnon
2010-08-10 13:03 ` Kevin O'Gorman
2010-08-10 18:50 ` Alan McKinnon
2010-08-10 19:22 ` Hazen Valliant-Saunders
2010-08-10 23:23 ` Peter Humphrey
2010-08-11 16:55 ` Stroller
2010-08-11 18:16 ` Dale
2010-08-11 20:30 ` Alan McKinnon
2010-08-11 22:11 ` [gentoo-user] Rooted/compromised Gentoo, seeking advice - AKA passwords Bill Longman
2010-08-11 23:09 ` Alan McKinnon
2010-08-12 4:30 ` Bill Longman
2010-08-12 13:01 ` [gentoo-user] Rooted/compromised Gentoo, seeking advice Stroller
2010-08-12 19:21 ` Alan McKinnon
2010-08-12 19:43 ` Peter Humphrey
2010-08-12 20:14 ` Alan McKinnon
2010-08-12 12:56 ` Stroller
2010-08-13 2:11 ` Dale
2010-08-11 16:58 ` Stroller
2010-08-11 20:26 ` Alan McKinnon
2010-08-09 20:25 ` Dale
2010-08-09 21:22 ` Mick
2010-08-09 22:19 ` Dale
2010-08-09 21:17 ` Philip Webb [this message]
2010-08-09 23:07 ` Paul Hartman
2010-08-10 2:14 ` Frank Steinmetzger
2010-08-10 2:24 ` Indexer
2010-08-11 1:05 ` Walter Dnes
2010-08-11 2:16 ` Dale
2010-08-11 4:36 ` Walter Dnes
2010-08-11 5:37 ` Dale
2010-08-10 2:30 ` Keith Dart
2010-08-10 3:06 ` Adam Carter
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=20100809211749.GF4258@ca.inter.net \
--to=purslow@ca.inter.net \
--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