[Adduser-devel] [RFR] templates://adduser/{templates}
Justin B Rye
jbr at edlug.org.uk
Mon Jun 11 19:32:37 UTC 2007
Christian Perrier wrote:
> Your review should be sent as an answer to this mail.
> +_Description: Do you want system-wide readable home directories?
> + By default, the users' home directories are readable by all users on
> + the system. If you want to increase the security and privacy on the
> + system, you might want home directories to be only readable by their
> + owners.
>
> Hyphen: recommended use in English in such cases?
"System-wide"? Definitely.
> paragraph rewrite for what seems to be better wording to
> me..:-). Again, tending to avoid personnalization ("your home directories")
That makes sense. But (preserved from the original) "to increase
the security and privacy on the system" falls between two stools:
to increase the security/privacy of the system
to increase security/privacy on the system
and although it's not particularly jarring, it's enough to make me
notice that "on the system" is getting repeated.
_Description: Do you want system-wide readable home directories?
By default, user home directories are readable for all users on the
system. If you want to increase security and privacy, you might want
home directories to be readable only for their owners.
> If in doubt, you should enable this option.
Which means you should *not* change it from the default of "true"
("yes, leave them public"). There's a danger readers will
misunderstand this as advice that they should play safe by enabling
the option just mentioned ("no, make them private").
But if in doubt, leave this option enabled.
> + This will only affect newly created home directories for users added
> + with the adduser program.
>
> I feel this like better wording but this may be improved by native
> speakers, though.
I was thinking
This will affect only home directories of users added from this point
on with the adduser command.
> Adduser will choose appropriate UID and GID values, create a home
> - directory, copy skeletal user configuration, allow you to set an
> - initial password and the GECOS field.
> + directory, copy skeletal user configuration, fill in the GECOS field
> + and allow setting an initial password.
>
> Native speakers: is "allow setting" Frenglish? :-)
No, but I don't like "allow" here anyway, since adduser doesn't
normally offer an alternative! Also, adduser does not itself fill
in the GECOS field; it just lets you fill it in at the same time as
the password. And do we really need to use this term "GECOS", which
isn't explained even in "man 5 passwd"? It stands for "General
Electric Comprehensive Operating Supervisor", but even GE themselves
haven't called it by that name since 1970!
How about:
directory, copy skeletal user configuration, and automate setting
initial values for the user's password, real name and so on.
> Deluser can optionally remove and backup the user's home directory
The verb is (usually) "back up", not "backup", and it's safer to
archive things before you remove them... (Oh, and there's a "can
optionally" here too! But this time it works, contrasting with the
things adduser *will* do).
Deluser can optionally back up and remove the user's home directory
and mail spool or all files on the system owned by the removed user.
But I would gender-neutralise it this way instead:
Deluser can optionally back up and remove users' home directories
and mail spools or all the files they own on the system.
--
JBR
Ankh kak! (Ancient Egyptian blessing)
-------------- next part --------------
4,8c4,8
< _Description: Do you want system wide readable home directories?
< Normally, home directories can be viewed by all users on the system. If
< you want to increase the security/privacy on your system, you might want
< your home directories only readable by the user. If you are unsure,
< enable system wide readable home directories.
---
> _Description: Do you want system-wide readable home directories?
> By default, user home directories are readable for all users on the
> system. If you want to increase security and privacy, you might want
> home directories to be readable only for their owners. But if in
> doubt, leave this option enabled.
10,11c10,11
< This will only affect home directories of users added with the adduser
< program later.
---
> This will affect only home directories of users added from this point
> on with the adduser command.
15c15
< Description: Add and remove users and groups
---
> Description: add and remove users and groups
19,21c19,21
< - Adduser can create new users and groups and add existing users to
< existing groups.
< - Deluser can remove users and groups and remove users from a given
---
> - 'adduser' creates new users and groups and adds existing users to
> existing groups;
> - 'deluser' removes users and groups and removes users from a given
24c24
< Adding users with adduser is much easier than adding them by hand.
---
> Adding users with adduser is much easier than adding them manually.
26,27c26,27
< directory, copy skeletal user configuration, allow you to set an
< initial password and the GECOS field.
---
> directory, copy skeletal user configuration, and automate setting
> initial values for the user's password, real name and so on.
29,30c29,30
< Deluser can optionally remove and backup the user's home directory
< and mail spool or all files on the system owned by him.
---
> Deluser can optionally back up and remove users' home directories
> and mail spools or all the files they own on the system.
32c32
< Optionally a custom script can be executed after each of the commands.
---
> A custom script can be executed after each of the commands.
34,36c34,36
< Adduser is maintained on http://alioth.debian.org/projects/adduser/.
< There is also a development mailing list on
< http://lists.alioth.debian.org/mailman/listinfo/adduser-devel/.
---
> Homepage: http://alioth.debian.org/projects/adduser/
> Development mailing list:
> http://lists.alioth.debian.org/mailman/listinfo/adduser-devel/
-------------- next part --------------
Template: adduser/homedir-permission
Type: boolean
Default: true
_Description: Do you want system-wide readable home directories?
By default, user home directories are readable for all users on the
system. If you want to increase security and privacy, you might want
home directories to be readable only for their owners. But if in
doubt, leave this option enabled.
.
This will affect only home directories of users added from this point
on with the adduser command.
-------------- next part --------------
Source: adduser
Section: admin
Priority: important
Maintainer: Debian Adduser Developers <adduser-devel at lists.alioth.debian.org>
Uploaders: Roland Bauerschmidt <rb at debian.org>, Marc Haber <mh+debian-packages at zugschlus.de>
Standards-Version: 3.7.2
Build-Depends: po-debconf
Build-Depends-Indep: gettext (>= 0.13), po4a (>= 0.23)
Package: adduser
Architecture: all
Depends: perl-base (>=5.6.0), passwd (>= 1:4.0.12), debconf | debconf-2.0
Suggests: liblocale-gettext-perl, perl-modules
Replaces: manpages-pl (<= 20051117-1), manpages-it (<< 0.3.4-2)
Description: add and remove users and groups
This package includes the adduser and deluser commands for creating
and removing users.
.
- 'adduser' creates new users and groups and adds existing users to
existing groups;
- 'deluser' removes users and groups and removes users from a given
group.
.
Adding users with adduser is much easier than adding them manually.
Adduser will choose appropriate UID and GID values, create a home
directory, copy skeletal user configuration, and automate setting
initial values for the user's password, real name and so on.
.
Deluser can optionally back up and remove users' home directories
and mail spools or all the files they own on the system.
.
A custom script can be executed after each of the commands.
.
Homepage: http://alioth.debian.org/projects/adduser/
Development mailing list:
http://lists.alioth.debian.org/mailman/listinfo/adduser-devel/
More information about the Adduser-devel
mailing list