Gentoo Archives: gentoo-amd64

From: Mark Knecht <markknecht@×××××.com>
To: gentoo-amd64@l.g.o
Subject: Re: [gentoo-amd64] Re: !!! Security Violation: A file exists that is not in the manifest.
Date: Fri, 03 Mar 2006 00:53:12
Message-Id: 5bdc1c8b0603021651q5aa15c84gc42bd393cc091eaf@mail.gmail.com
In Reply to: [gentoo-amd64] Re: !!! Security Violation: A file exists that is not in the manifest. by Duncan <1i5t5.duncan@cox.net>
1 Redoing eix-sync a few times over the last couple of hours and now
2 it's cleaned up.
3
4 cheers,
5 Mark
6
7 On 3/2/06, Duncan <1i5t5.duncan@×××.net> wrote:
8 > Mark Knecht posted
9 > <5bdc1c8b0603021524m572eedf7x18e22e51a1274d08@××××××××××.com>, excerpted
10 > below, on Thu, 02 Mar 2006 15:24:07 -0800:
11 >
12 > >>>> emerge (4 of 6) sys-apps/baselayout-1.11.14-r6 to /
13 > > !!! Security Violation: A file exists that is not in the manifest.
14 > > !!! File: files/digest-baselayout-1.12.0_pre16-r2
15 > > lightning ~ #
16 > >
17 > > What's the proper way to take care of this?
18 >
19 > Depends on how paranoid you are. While it could be someone trying to
20 > crack the Gentoo ecosystem, it's far more likely to be a simple mis-sync
21 > -- either you or the upstream rsync server you used happened to sync at
22 > just the wrong moment and get a modification in progress, with the file
23 > there but the manifest not yet updated to reflect it. It could also be
24 > due to a dev partial-syncing, with the same results.
25 >
26 > If you are willing to play the odds, you can just ebuild digest (see
27 > the ebuild manpage if necessary) the thing and it'll fix the issue on your
28 > system. If you are security conscious enough to not be comfortable doing
29 > that (I certainly wouldn't be -- those manifests are there for a reason,
30 > and it /could/ be a cracker trying something, even if rather unlikely),
31 > wait a minimum 90 minutes between syncs, and try another emerge --sync.
32 > Hopefully by then the problem will have corrected itself, or you'll get a
33 > different sync server assigned that doesn't have the problem.
34 >
35 > If the issue still exists several hours later, after a resync, check the
36 > logs and verify the servers you are syncing with, then file a bug on
37 > either the rsync server or baselayout, as it's something that needs fixed,
38 > still most likely a dev accident, but getting more likely it's a real
39 > security issue.
40 >
41 > That assumes nothing irregular at your end, like you added that subdir in
42 > your rsync-excludes file or something, but then again, if you'd done that,
43 > you'd likely know that was the reason without asking. That would be a bit
44 > hard to do by accident. =8^)
45 >
46 > --
47 > Duncan - List replies preferred. No HTML msgs.
48 > "Every nonfree program has a lord, a master --
49 > and if you use the program, he is your master." Richard Stallman in
50 > http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html
51 >
52 >
53 > --
54 > gentoo-amd64@g.o mailing list
55 >
56 >
57
58 --
59 gentoo-amd64@g.o mailing list