1 |
On Mon, Nov 08, 2004 at 02:05:26AM +0100 or thereabouts, Peter Simons wrote: |
2 |
> The entire contents of /usr/portage is not authenticated. |
3 |
> All the manifest files, all the patches, all the ebuilds are |
4 |
> obtained through a public network without _any_ form of |
5 |
> authentication. |
6 |
|
7 |
That is factually incorrect. |
8 |
|
9 |
Pick any Gentoo machine that has a reasonably recent portage tree and do |
10 |
any of the following: |
11 |
|
12 |
cat /usr/portage/sys-apps/portage/Manifest |
13 |
cat /usr/portage/app-editors/vim/Manifest |
14 |
cat /usr/portage/dev-lang/perl/Manifest |
15 |
|
16 |
Those are but three examples. Certainly not all files are signed, but to |
17 |
say that we're completely ignorant of the problem is a grossly unfair |
18 |
mischaracterization. |
19 |
|
20 |
> Does that make it any clearer why this problem might be |
21 |
> worth being solved, like, soon? |
22 |
|
23 |
It certainly does show that you haven't taken the time to understand what |
24 |
features portage currently does and does not offer. |
25 |
|
26 |
Again, nobody is arguing about signing ebuilds. That functionality already |
27 |
exists as of .51 and we're working on getting devs to sign their ebuilds. |
28 |
Work is *already* under way to solve this problem -- you're wasting your |
29 |
breath if this is all you're concerned about. |
30 |
|
31 |
The original message talked about eclasses and specifically, their lack of |
32 |
versioning. |
33 |
|
34 |
--kurt |