Gentoo Archives: gentoo-user

From: gentuxx <gentuxx@×××××.com>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] Um...Who can fix this? -- SOLVED
Date: Mon, 24 Oct 2005 22:55:33
Message-Id: 435D60AC.5000302@gmail.com
In Reply to: Re: [gentoo-user] Um...Who can fix this? by Nick Rout
1 -----BEGIN PGP SIGNED MESSAGE-----
2 Hash: SHA1
3
4 Nick Rout wrote:
5
6 >On Mon, 24 Oct 2005 22:32:46 +0100
7 >Jonathan Wright wrote:
8 >
9 >>- Second, run the digest command. You'll need to do this if it's not in
10 >>the standard portage tree and it's something you have added. Portage
11 >>needs to be told all the files within the tree and their md5 values, to
12 >>make sure nothing bad gets in :)
13 >
14 >
15 >And by running emerge --digest <target> or ebuild <target.ebuild> digest
16 >screws the digest system, because it substitutes the values you got from
17 >the portage mirror with the values from the files on your computer. It
18 >destroys any safety that the digest system offers.
19 >
20 >So if someone has broken into your system and screwed around with the
21 >portage tree so that when you install sylpheed-claws it does something
22 >nasty, running the digest command will allow that to happen.
23 >
24 >If the digests are wrong find out what the problem is!
25 >
26 My guess is that it didn't even get to the digest checks when it gave
27 me the error/warning. emerge --sync seems to have fixed the problem.
28 I probably should have tried that before posting. ;-)
29
30 - --
31 gentux
32 echo "hfouvyAdpy/ofu" | perl -pe 's/(.)/chr(ord($1)-1)/ge'
33
34 gentux's gpg fingerprint ==> 34CE 2E97 40C7 EF6E EC40 9795 2D81 924A
35 6996 0993
36 -----BEGIN PGP SIGNATURE-----
37 Version: GnuPG v1.4.1 (GNU/Linux)
38
39 iD8DBQFDXWCsLYGSSmmWCZMRAhEwAJ4oplvQ41TfWsYJL9DmY6DGJ6dvHQCgi/Us
40 wpUly/Hz/3VTvZdFE7k1ILI=
41 =7dn/
42 -----END PGP SIGNATURE-----
43
44 --
45 gentoo-user@g.o mailing list

Replies

Subject Author
Re: [gentoo-user] Um...Who can fix this? -- SOLVED Ciaran McCreesh <ciaranm@g.o>