public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Paul de Vrieze <gentoo-user@devrieze.net>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] Re: [gentoo-security] Trojan for Gentoo/GNU Linux, proof of concept
Date: Sat, 22 Mar 2003 22:14:23 +0100	[thread overview]
Message-ID: <200303222214.31606.gentoo-user@devrieze.net> (raw)
In-Reply-To: <3E7C4709.3090808@komcept.com>

[-- Attachment #1: signed data --]
[-- Type: text/plain, Size: 1090 bytes --]

On Saturday 22 March 2003 12:20, MAL wrote:
>
> I don't think I would trust a security/paranoid only update system
> within portage, as portage will still be working with an externally
> generated list of to-do.  Building aan update locally, making sure it's
> only what you want, then packaging it, (ebuild package - tbz2 format),
> and installing it on the remote machine, is the only method i'd feel
> satisfied with.
>

I agree with your point of view. While my only "server" is a home server that 
does some printing and ip sharing stuff I do make sure I don't just update 
world. I don't see the point of "running emerge -u world from cron" at all. 
The best protection from instability is keeping record of the mailing lists, 
and not updating what is not broken.

For my desktops, I even there wait with updates for packages like gcc, glibc, 
X etc. until I believe they are actually stable in a sense that I don't hear 
about problems concerning them anymore.

Paul

-- 
Paul de Vrieze
Researcher
Mail: pauldv@cs.kun.nl
Homepage: http://www.devrieze.net

[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

           reply	other threads:[~2003-03-22 21:14 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <3E7C4709.3090808@komcept.com>]

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=200303222214.31606.gentoo-user@devrieze.net \
    --to=gentoo-user@devrieze.net \
    --cc=gentoo-dev@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