[gentoo-dev] Automated Package Removal and Addition Tracker, for the week ending 2010-05-02 23h59 UTC

2010-05-02 Thread Robin H. Johnson
The attached list notes all of the packages that were added or removed from the tree, for the week ending 2010-05-02 23h59 UTC. Removals: sys-devel/binutils-nios22010-04-26 05:59:41 vapier sys-fs/btrfs2010-04-28 15:21:09 lavajoe xfce-extra/xfce4-volstatus-icon 2

Re: [gentoo-dev] A policy to support random superuser account names

2010-05-02 Thread Enrico Weigelt
* Stefan Behte schrieb: > in some environments you have to rename "root" to something else, just > to be compliant to a (maybe dumb) security policy. This might be the > case for PCI, and as far as I remember, it is necessary (not just > "recommended") for a BSI Grundschutz certification (meaning

[gentoo-dev] paper on oss-qm project

2010-05-02 Thread Enrico Weigelt
hi folks, just in case anybody's interested: I've written a little paper on the OSS-QM project, which aims to provide fixed sourcetrees to many packages+versions and so offload much of the QM/patching work from individual distros to a common place: http://www.metux.de/download/oss-qm-project-201

Re: [gentoo-dev] A policy to support random superuser account names

2010-05-02 Thread Enrico Weigelt
* Krzysztof Pawlik schrieb: > Interesting... to me that's not only stupid but also kinda useless - there's > no > difference between brute-forcing a password for user named 'foo' or 'root' - > user name doesn't matter much. Actually according to my ssh logs attackers > usually don't even try roo

Re: [gentoo-dev] A policy to support random superuser account names

2010-05-02 Thread Enrico Weigelt
* Alec Warner schrieb: > Except as stated they are not fixed (as Fabian pointed out). I'm > happy to support something like setting ROOT_UID and ROOT_GID in > gentoo-x86 profiles and using those. Then if you want to do something > utterly ridiculous to your system you can just set the appropria

Re: [gentoo-dev] A policy to support random superuser account names

2010-05-02 Thread Stefan Behte
02.05.2010 17:23, Krzysztof Pawlik wrote: > Interesting... to me that's not only stupid but also kinda useless - there's > no > difference between brute-forcing a password for user named 'foo' or 'root' - > user name doesn't matter much. > It's better to disable password-based remote login altoget

Re: [gentoo-dev] [git migration] The problem of ChangeLog generation

2010-05-02 Thread Jim Ramsay
Peter Volkov wrote: > ?? ??, 13/04/2010 ?? 17:18 +0530, Nirbheek Chauhan ??: > > The traditional ChangeLog that is currently employed in gentoo-x86 > > (and in other projects) is simply an ugly hack > > The difference between gentoo-x86 ebuild ChangeLogs and ChangeLogs used > in other

Re: [gentoo-dev] A policy to support random superuser account names

2010-05-02 Thread Stefan Behte
Hi, in some environments you have to rename "root" to something else, just to be compliant to a (maybe dumb) security policy. This might be the case for PCI, and as far as I remember, it is necessary (not just "recommended") for a BSI Grundschutz certification (meaning something like "basic securi

Re: [gentoo-dev] A policy to support random superuser account names

2010-05-02 Thread Krzysztof Pawlik
On 05/02/10 16:13, Stefan Behte wrote: > Hi, > > in some environments you have to rename "root" to something else, just > to be compliant to a (maybe dumb) security policy. This might be the > case for PCI, and as far as I remember, it is necessary (not just > "recommended") for a BSI Grundschutz