1 |
On 11/07/2013 12:37 AM, Andreas K. Huettel wrote: |
2 |
> Am Donnerstag, 7. November 2013, 00:18:19 schrieb Denis M.: |
3 |
>> Hello gentoo-dev@, |
4 |
>> |
5 |
>> Starting with a little intro, I'm currently providing a Gentoo VM to a |
6 |
>> gentoo dev (Agostino Sarubbo (ago)) for the purpose of |
7 |
>> testing/stabilizing/keywording packages, which is part of his task as a |
8 |
>> developer and being part of the AT team. I've been running the VM for |
9 |
>> him for a couple of months now and AFAIK he's been giving it a great use |
10 |
>> ;-). |
11 |
>> |
12 |
>> The main idea here is to allow Gentoo contributors and members (not |
13 |
>> necessary) of the Gentoo community, to be able to support the developer |
14 |
>> team providing their spare system resources, by, for example, running a |
15 |
>> Virtual Machine (or any sort of xen, kvm, virtualbox, vmware, |
16 |
>> whatever...) instance where the devs can run tasks they'd normally |
17 |
>> wouldn't be able to run with their systems, because: |
18 |
>> |
19 |
> ... |
20 |
> |
21 |
> I appreciate the idea, but security-wise it's pretty dangerous - given that |
22 |
> you as a Gentoo dev are doing sensitive work that may affect many people on a |
23 |
> machine not controlled by you yourself nor Gentoo Infra. |
24 |
|
25 |
I completely agree with this, but it's not entirely true. Why? I'll give |
26 |
the example of the AT team: |
27 |
|
28 |
1. You sync the tree before you start your work (that way you verify the |
29 |
tree is clean). |
30 |
2. Then you start testing the packages or bugs you're after, which in |
31 |
matter of security is meaningless because testing packages is usually |
32 |
just compiling and running to see if it works as expected. |
33 |
2.1. Apply random patches to fix if there's an issue. |
34 |
2.2. goto 2. |
35 |
3. etc... |
36 |
|
37 |
I see no issue in this in matter of security. |
38 |
|
39 |
Another example would be devs testing packages under development |
40 |
(internal usage in gentoo), for example how new versions of |
41 |
openrc/systemd/glibc/whatever can affect X. |
42 |
|
43 |
I do understand your concern, although I wouldn't call you paranoid as |
44 |
it's just normal to not trust a system that's not completely under your |
45 |
control, but as I said, you don't really... 'care' about it/that. |
46 |
|
47 |
> |
48 |
> Call me paranoid, but please no. And in absolutely no case one should commit |
49 |
> to the tree from such a machine, even with stuff like agent forwarding. |
50 |
> |
51 |
|
52 |
Of course! Commiting or any other form of direct communication with the |
53 |
gentoo infra. (either commit to tree or `git push`-ing to any of the |
54 |
other gentoo repos) would be highly discouraged, and I didn't, in any |
55 |
moment, think someone would think of doing that :P. |
56 |
|
57 |
The idea behind this is using the provided instance only and exclusively |
58 |
for testing something you'd normally can't do on your system. |
59 |
|
60 |
|
61 |
Regards, |
62 |
Denis M. |