Revision 24167,
1.1 KB
checked in by broder, 15 years ago
(diff) |
Import schroot upstream into subversion.
|
Line | |
---|
1 | Requirements -*- outline -*- |
---|
2 | ------------ |
---|
3 | |
---|
4 | * Allow a user to chroot() into a location specified in a configuration file. |
---|
5 | |
---|
6 | This will require the program to be setuid-root. |
---|
7 | |
---|
8 | * Allow the user to run a command or a login shell. |
---|
9 | |
---|
10 | * Allow the user to preserve their environment inside the chroot. |
---|
11 | |
---|
12 | This should not be the default. |
---|
13 | |
---|
14 | * Restrict access to the chroot to certain users or groups. |
---|
15 | |
---|
16 | Group restrictions are easiest to administer, and the default is to |
---|
17 | create users with their own group anyway. |
---|
18 | |
---|
19 | * Allow root access to non-root users. |
---|
20 | |
---|
21 | root access is required in order to install and remove packages in |
---|
22 | the root (i.e. general apt/dpkg stuff). |
---|
23 | |
---|
24 | In order for tools like sbuild to run non-interactively, this should |
---|
25 | be password-less if the user is authorised to have root access in |
---|
26 | the chroot. |
---|
27 | |
---|
28 | * Allow changing to other users, in addition to root, in the same manner as su(1). |
---|
29 | |
---|
30 | This will require authentication. |
---|
31 | |
---|
32 | * Allow querying of the available chroots. |
---|
33 | |
---|
34 | Tools need to know the available chroots, and should not be required |
---|
35 | to parse the configuration file by hand. |
---|
Note: See
TracBrowser
for help on using the repository browser.