public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Hemmann, Volker Armin" <volker.armin.hemmann@tu-clausthal.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Eez a byootiful dai todai
Date: Sat, 31 Mar 2007 00:44:20 +0200	[thread overview]
Message-ID: <200703310044.20593.volker.armin.hemmann@tu-clausthal.de> (raw)
In-Reply-To: <200703301657.00738.bss03@volumehost.net>

On Freitag, 30. März 2007, Boyd Stephen Smith Jr. wrote:
> On Friday 30 March 2007, "Hemmann, Volker Armin"
> <volker.armin.hemmann@tu-clausthal.de> wrote about 'Re: [gentoo-user] Eez
>
> a byootiful dai todai':
> > On Freitag, 30. März 2007, Dan Farrell wrote:
> > > The neat computers in the world today deserver Linux, and let's face
> > > it, we all deserve to be gurus on 90% of computers and not 5%.
> >
> > 5% is totally ok for me, if 90% marketshare means ubuntu
> > I mean no real root (ubuntu),
>
> This is silly, Ubuntu has just as much of a root as any other linux, it
> just randomizes/expires the password instead of prompting you for one by
> default.  A simple 'sudo passwd' will fix let you login or su to root.  Of
> course, you might as well just use 'sudo -s'.
>
> Personally, I use Kubuntu on my laptop and have never had a reason to
> change root's password from the default.  Even on my Gentoo desktop, I use
> sudo (and my user password) 100x more often than su/login and the root
> password.
>
> The choice to not ask for root's password during installation was amde for
> good reason.  One less question makes the installation easier and faster,
> and providing the randomized password + sudo access increases or at least
> does not decrease security afforded by the "old" Debian way (which ends up
> prompting for two passwords; each twice).

one question makes soooo much of a difference. And instead of two passwords, 
one never entered in X, an attacker only needs to capture your user password, 
which is typed in douzends of time, to f* up your machine....

--
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2007-03-30 22:49 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-29  9:49 [gentoo-user] Eez a byootiful dai todai Jeff Rollin
2007-03-29 10:21 ` Kellystewart00
     [not found] ` <20070329120550.d98fc758.hilse@web.de>
2007-03-29 10:43   ` Jeff Rollin
2007-03-29 19:58     ` [gentoo-user] " »Q«
2007-03-29 20:32       ` Neil Bothwick
2007-03-29 22:20         ` »Q«
2007-03-29 23:23           ` Neil Bothwick
2007-03-30  6:27             ` Jeff Rollin
2007-03-30 17:10               ` Jeff Rollin
2007-03-29 21:24       ` Jeff Rollin
2007-03-29 22:29         ` »Q«
2007-03-29 20:19     ` [gentoo-user] " Bo Ørsted Andresen
2007-03-29 20:38     ` Richard Cox
2007-03-29 20:52       ` Jeff Rollin
2007-03-30  4:15         ` [gentoo-user] " Grant Edwards
2007-03-30  4:11     ` Grant Edwards
2007-03-30 18:27 ` [gentoo-user] " Dan Farrell
2007-03-30 18:42   ` Michael Sullivan
2007-03-30 20:08   ` Richard Cox
2007-03-30 21:01   ` Hemmann, Volker Armin
2007-03-30 21:56     ` Boyd Stephen Smith Jr.
2007-03-30 22:44       ` Hemmann, Volker Armin [this message]
2007-04-02  7:48         ` Nelson, David J
2007-03-31 21:17       ` Jeff Rollin

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=200703310044.20593.volker.armin.hemmann@tu-clausthal.de \
    --to=volker.armin.hemmann@tu-clausthal.de \
    --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