From bubulle@debian.org Tue Mar 15 07:35:46 2005 From: bubulle@debian.org (Christian Perrier) Date: Tue, 15 Mar 2005 08:35:46 +0100 Subject: [Pkg-shadow-devel] Re: Bug#299549: login: upgrade from woody fails due to conflicting files In-Reply-To: <20050314215842.GA5305@linuxfr.org> References: <20050314215842.GA5305@linuxfr.org> Message-ID: <20050315073546.GA7756@mykerinos.kheops.frmug.org> tags 299549 pending thanks Quoting Denis Barbier (barbier@debian.org): > I was told on a non-Debian mailing list that upgrade from woody to sarge > fails because of conflicts between login/sarge and manpages-it/woody. > This is similar to #284239. Thanks for investigating this completely, Denis. As usual, your contribution has a high value. I added manpages-it and manpages-ko to Replaces for login. I removed the useless entry for manpages-de (no real reason to keep a Replaces if unneeded) and sorted the Replaces line for passwd with no change, for readability. The package is currently building and will be uploaded ASAP with urgency set to high. I'll also set the pkg-shadow-devel@lists.alioth.debian.org mailing list as Maintainer and myself (and Sam Hartman) as uploader(s). This is the final occasion for me to thank Karl Ramm in his work maintaining this package. Further bug reports for shadow will go to pkg-shadow-devel@lists.alioth.debian.org From katie@ftp-master.debian.org Tue Mar 15 09:50:21 2005 From: katie@ftp-master.debian.org (Archive Administrator) Date: Tue, 15 Mar 2005 04:50:21 -0500 Subject: [Pkg-shadow-devel] Processing of shadow_4.0.3-31_i386.changes Message-ID: shadow_4.0.3-31_i386.changes uploaded successfully to localhost along with the files: shadow_4.0.3-31.dsc shadow_4.0.3-31.diff.gz passwd_4.0.3-31_i386.deb login_4.0.3-31_i386.deb Greetings, Your Debian queue daemon From installer@ftp-master.debian.org Tue Mar 15 10:02:30 2005 From: installer@ftp-master.debian.org (Debian Installer) Date: Tue, 15 Mar 2005 05:02:30 -0500 Subject: [Pkg-shadow-devel] shadow_4.0.3-31_i386.changes ACCEPTED Message-ID: Accepted: login_4.0.3-31_i386.deb to pool/main/s/shadow/login_4.0.3-31_i386.deb passwd_4.0.3-31_i386.deb to pool/main/s/shadow/passwd_4.0.3-31_i386.deb shadow_4.0.3-31.diff.gz to pool/main/s/shadow/shadow_4.0.3-31.diff.gz shadow_4.0.3-31.dsc to pool/main/s/shadow/shadow_4.0.3-31.dsc Announcing to debian-devel-changes@lists.debian.org Thank you for your contribution to Debian. From katie@ftp-master.debian.org Tue Mar 15 15:04:47 2005 From: katie@ftp-master.debian.org (Archive Administrator) Date: Tue, 15 Mar 2005 10:04:47 -0500 Subject: [Pkg-shadow-devel] Processing of shadow_4.0.3-31sarge1_i386.changes Message-ID: shadow_4.0.3-31sarge1_i386.changes uploaded successfully to localhost along with the files: shadow_4.0.3-31sarge1.dsc shadow_4.0.3-31sarge1.diff.gz passwd_4.0.3-31sarge1_i386.deb login_4.0.3-31sarge1_i386.deb Greetings, Your Debian queue daemon From installer@ftp-master.debian.org Tue Mar 15 15:17:22 2005 From: installer@ftp-master.debian.org (Debian Installer) Date: Tue, 15 Mar 2005 10:17:22 -0500 Subject: [Pkg-shadow-devel] shadow_4.0.3-31sarge1_i386.changes ACCEPTED Message-ID: Accepted: login_4.0.3-31sarge1_i386.deb to pool/main/s/shadow/login_4.0.3-31sarge1_i386.deb passwd_4.0.3-31sarge1_i386.deb to pool/main/s/shadow/passwd_4.0.3-31sarge1_i386.deb shadow_4.0.3-31sarge1.diff.gz to pool/main/s/shadow/shadow_4.0.3-31sarge1.diff.gz shadow_4.0.3-31sarge1.dsc to pool/main/s/shadow/shadow_4.0.3-31sarge1.dsc Announcing to debian-devel-changes@lists.debian.org Closing bugs: 299549 Thank you for your contribution to Debian. From bubulle@debian.org Tue Mar 15 20:19:09 2005 From: bubulle@debian.org (Christian Perrier) Date: Tue, 15 Mar 2005 21:19:09 +0100 Subject: [Pkg-shadow-devel] Here we are with the shadow package maintenance Message-ID: <20050315201909.GM26395@mykerinos.kheops.frmug.org> Folks, here we are.... Today, I have uploaded the 4.0.3-31sarge1 release of the Debian shadow package. It will reach unstable now and testing in 2 days. I have used the opportunity of a release critical bug report (upgrade failure from woody under some circumstances because of file conflicts) to do this. This package has this mailing list mentioned as "Maintainer:" which means the bug reports and mails sent to "shadow@packages.debian.org" will go here (I need to double-check this). I am myself recorded as "Uploader:" along with Sam Hartman (I'm not sure whether Sam is subscribed here or not). The CVS on Alioth has however currently NOT the current status of the debian/ package. I'll keep maintaining this manually as this is supposed to have very few changes now. Indeed it has the -32 upcoming release, targeted at post-sarge, which will use dpatch as a convenient way to have all Debian specific stuff in the debian/ directory (which will be the only one maintained through CVS). For avoiding confusion, I will probably not make an upload of -32 before the release of sarge (this would later require using testing-proposed-updates for sarge updates, which I want to avoid). Welcome to the new world of the shadow Debian package....we are not a lot of people, but I hope we'll make a good job. -- From owner@bugs.debian.org Tue Mar 15 20:51:14 2005 From: owner@bugs.debian.org (Debian Bug Tracking System) Date: Tue, 15 Mar 2005 12:51:14 -0800 Subject: [Pkg-shadow-devel] Bug#299681: marked as done (shadow: Just check if bugs go to the right place) In-Reply-To: <20050315204746.GO26395@mykerinos.kheops.frmug.org> References: <20050315204746.GO26395@mykerinos.kheops.frmug.org> <20050315202623.642812326F@mykerinos.kheops.frmug.org> Message-ID: Your message dated Tue, 15 Mar 2005 21:47:46 +0100 with message-id <20050315204746.GO26395@mykerinos.kheops.frmug.org> and subject line Bug#299681: Acknowledgement (shadow: Just check if bugs go to the right place) has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -------------------------------------- Received: (at submit) by bugs.debian.org; 15 Mar 2005 20:27:18 +0000 >From bubulle@debian.org Tue Mar 15 12:27:18 2005 Return-path: Received: from perrier.eu.org (kheops.perrier.eu.org) [81.56.227.253] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1DBIdK-0006M3-00; Tue, 15 Mar 2005 12:27:18 -0800 Received: from localhost (localhost [127.0.0.1]) by kheops.perrier.eu.org (Postfix) with ESMTP id EFB134F89B for ; Tue, 15 Mar 2005 21:26:40 +0100 (CET) Received: from kheops.perrier.eu.org ([127.0.0.1]) by localhost (kheops [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 21523-03 for ; Tue, 15 Mar 2005 21:26:40 +0100 (CET) Received: from mykerinos.kheops.frmug.org (mykerinos.kheops.frmug.org [192.168.1.3]) by kheops.perrier.eu.org (Postfix) with ESMTP id 6E7804F89A for ; Tue, 15 Mar 2005 21:26:23 +0100 (CET) Received: by mykerinos.kheops.frmug.org (Postfix, from userid 7426) id 642812326F; Tue, 15 Mar 2005 21:26:23 +0100 (CET) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Christian Perrier To: Debian Bug Tracking System Subject: shadow: Just check if bugs go to the right place X-Mailer: reportbug 3.8 Date: Tue, 15 Mar 2005 21:26:23 +0100 Message-Id: <20050315202623.642812326F@mykerinos.kheops.frmug.org> X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at kheops.frmug.org Delivered-To: submit@bugs.debian.org X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2005_01_02 X-Spam-Level: Package: shadow Severity: wishlist Fake bug, just to check where do the bug reports go..:) -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.9-1-686 Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to fr_FR.UTF-8) --------------------------------------- Received: (at 299681-done) by bugs.debian.org; 15 Mar 2005 20:48:19 +0000 >From bubulle@kheops.frmug.org Tue Mar 15 12:48:19 2005 Return-path: Received: from perrier.eu.org (kheops.perrier.eu.org) [81.56.227.253] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1DBIxe-0001Kx-00; Tue, 15 Mar 2005 12:48:19 -0800 Received: from localhost (localhost [127.0.0.1]) by kheops.perrier.eu.org (Postfix) with ESMTP id AF3754F89B for <299681-done@bugs.debian.org>; Tue, 15 Mar 2005 21:47:47 +0100 (CET) Received: from kheops.perrier.eu.org ([127.0.0.1]) by localhost (kheops [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 24161-02 for <299681-done@bugs.debian.org>; Tue, 15 Mar 2005 21:47:47 +0100 (CET) Received: from mykerinos.kheops.frmug.org (mykerinos.kheops.frmug.org [192.168.1.3]) by kheops.perrier.eu.org (Postfix) with ESMTP id 2E51F4F899 for <299681-done@bugs.debian.org>; Tue, 15 Mar 2005 21:47:47 +0100 (CET) Received: by mykerinos.kheops.frmug.org (Postfix, from userid 7426) id 193D42326F; Tue, 15 Mar 2005 21:47:47 +0100 (CET) Date: Tue, 15 Mar 2005 21:47:46 +0100 From: Christian Perrier To: 299681-done@bugs.debian.org Subject: Re: Bug#299681: Acknowledgement (shadow: Just check if bugs go to the right place) Message-ID: <20050315204746.GO26395@mykerinos.kheops.frmug.org> References: <20050315202623.642812326F@mykerinos.kheops.frmug.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-message-flag: Outlook is a good virus spreading tool. It can send mail, too. X-pot_a_miel: honeypot@kheops.frmug.org User-Agent: Mutt/1.5.6+20040907i X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at kheops.frmug.org Delivered-To: 299681-done@bugs.debian.org X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER autolearn=no version=2.60-bugs.debian.org_2005_01_02 X-Spam-Level: Closing the fake bug. Seems that bugs still go to Karl. I probably tested too early. From "Jaclyn" , 37297@bugs.debian.org Wed Mar 16 11:54:03 2005 From: "Jaclyn" , 37297@bugs.debian.org (Jaclyn) Date: Wed, 16 Mar 2005 05:54:03 -0600 Subject: [Pkg-shadow-devel] Bug#37297: Application approval for 37050@bugs.debian.org Wed, 16 Mar 2005 05:54:03 -0600 Message-ID: Hello, We sent you an email a while ago, because you now qualify for a much lower rate based on the biggest rate drop in years. You can now get $327,000 for as little as $617 a month! Bad credit? Doesn't matter, low rates are fixed no matter what! Follow this link to process your application and a 24 hour approval: http://www.realrxmeds.net/?id=e48 Best Regards, Andy Bolton opt out: http://www.realrxmeds.net/byebye.php From bubulle@debian.org Wed Mar 16 17:30:51 2005 From: bubulle@debian.org (Christian Perrier) Date: Wed, 16 Mar 2005 18:30:51 +0100 Subject: [Pkg-shadow-devel] Bug#37297..... In-Reply-To: References: Message-ID: <20050316173051.GC24521@mykerinos.kheops.frmug.org> > Hello, > > We sent you an email a while ago, because you now qualify .../... Funnily this spam is the very first proof that bug reports for the shadow package are now connected to the pkg-shadow developers list, fellows...:-)) I tried to check this myself yesterday but a bit too early, so it seems that I don't have to do it now, thanks to this bloody spammer. From service@intl.paypal.com Thu Mar 17 23:03:02 2005 From: service@intl.paypal.com (service@intl.paypal.com) Date: Thu, 17 Mar 2005 18:03:02 -0500 Subject: [Pkg-shadow-devel] PayPal Account Security Measures Message-ID: <200503172303.j2HN32cU018682@ice.southkent.net> 
Dear PayPal User,

We recently noticed one or more attempts to log in to your PayPal account
from a foreign IP address. We have temporarily limited access to sensitive
PayPal account features. Allowing your account access to remain limited for 
an extended period of time may result in further limitations on the use of
your account and possible account closure.

If you recently accessed your account while traveling, the unusual log in
attempts may have been initiated by you. However, if you did not initiate
the log ins, please visit PayPal as soon as possible to log in and perform 
the steps necessary to restore your account access:

https://www.paypal.com/us/cgi-bin/webscr?cmd=_login-run


After filling in the information required we advise you to change your password.
Changing your password is a security measure that will ensure that you are
the only person with access to the account.


Thanks for your patience as we work together to protect your account.

Sincerely,
PayPal
    


Please do not reply to this e-mail. Mail sent to this address cannot be
answered. For assistance, log in to your PayPal account and choose the
"Help" link in the header of any page.

PayPal Email ID PP321
From Mike Brodbelt , 300268@bugs.debian.org Fri Mar 18 17:59:09 2005 From: Mike Brodbelt , 300268@bugs.debian.org (Mike Brodbelt) Date: Fri, 18 Mar 2005 17:59:09 +0000 Subject: [Pkg-shadow-devel] Bug#300268: /usr/share/man/man5/passwd.5.gz contains inaccurate information Message-ID: Package: passwd Version: 1:4.0.3-31sarge1 Severity: minor "man 5 passwd" produces documentation that is not entirely accurate. The second paragraph contains the following text:- "The encryped password consists of 13 characters from the 64 character alphabet a thru z, A thru Z, 0 thru 9, . and /. Refer to crypt(3) for details on how this string is interpreted." This information is clearly incorrect when the system is set to use MD5 passwords, which is increasingly the case. There's also a typo in "encrypted". Mike. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.11.4 Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) Versions of packages passwd depends on: ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an ii libpam-modules 0.76-22 Pluggable Authentication Modules f ii libpam0g 0.76-22 Pluggable Authentication Modules l ii login 1:4.0.3-31sarge1 system login tools -- debconf information excluded From kloczek@zie.pg.gda.pl Fri Mar 18 20:43:29 2005 From: kloczek@zie.pg.gda.pl (=?ISO-8859-2?Q?Tomasz_K=B3oczko?=) Date: Fri, 18 Mar 2005 21:43:29 +0100 (CET) Subject: [Pkg-shadow-devel] Bug#300268: /usr/share/man/man5/passwd.5.gz contains inaccurate information In-Reply-To: References: Message-ID: This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --568760595-1096432268-1111178609=:30561 Content-Type: TEXT/PLAIN; charset=ISO-8859-2 Content-Transfer-Encoding: QUOTED-PRINTABLE On Fri, 18 Mar 2005, Mike Brodbelt wrote: > Package: passwd > Version: 1:4.0.3-31sarge1 > Severity: minor >=20 >=20 > "man 5 passwd" produces documentation that is not entirely accurate. The > second paragraph contains the following text:- >=20 > "The encryped password consists of 13 characters > from the 64 character alphabet a thru z, A thru Z, 0 thru 9, > . and /. Refer to crypt(3) for details on how this string is > interpreted." >=20 > This information is clearly incorrect when the system is set to use MD5 > passwords, which is increasingly the case. There's also a typo in > "encrypted". Thanks for report. English isn't my native language so it will be good if someone will verify below patch before I'll commit this to shadow CVS tree. Any volunteers on update non-english passwd(5) ? (pl is mine :o) $ ls -1 */passwd.5 cs/passwd.5 fr/passwd.5 it/passwd.5 ja/passwd.5 ko/passwd.5 pl/passwd.5 ru/passwd.5 --- passwd.5 11 Dec 2004 20:05:01 -0000 1.13 +++ passwd.5 18 Mar 2005 20:25:48 -0000 @@ -48,9 +48,13 @@ .PP The password field may not be filled if shadow passwords have been enabled= =2E If shadow passwords are being used, the encrypted password will be found i= n -\fI/etc/shadow\fR. The encrypted password consists of 13 characters from t= he -64 character alphabet a thru z, A thru Z, 0 thru 9, \. and /. Refer to -\fBcrypt\fR(3) for details on how this string is interpreted. +\fI/etc/shadow\fR. The encrypted password consists of characters from the +64 character alphabet a thru z, A thru Z, 0 thru 9, \. and /. Optionaly it +can start with "$" character. This mean encrypted password was generated +using another (not DES) algorithm. For example if it start with "$1$" it m= eans +MD5-based algorithm was used. +.PP +Refer to \fBcrypt\fR(3) for details on how this string is interpreted. .PP The comment field is used by various system utilities, such as \fBfinger\fR(1). Three additional values may be present in the comment (EN= D) kloczek --=20 ----------------------------------------------------------- *Ludzie nie maj=B1 problem=F3w, tylko sobie sami je stwarzaj=B1* ----------------------------------------------------------- Tomasz K=B3oczko, sys adm @zie.pg.gda.pl|*e-mail: kloczek@rudy.mif.pg.gda.p= l* --568760595-1096432268-1111178609=:30561-- From =?ISO-8859-2?Q?Tomasz_K=B3oczko?= , 300268@bugs.debian.org Fri Mar 18 20:43:29 2005 From: =?ISO-8859-2?Q?Tomasz_K=B3oczko?= , 300268@bugs.debian.org (=?ISO-8859-2?Q?Tomasz_K=B3oczko?=) Date: Fri, 18 Mar 2005 21:43:29 +0100 (CET) Subject: Bug#300268: [Pkg-shadow-devel] Bug#300268: /usr/share/man/man5/passwd.5.gz contains inaccurate information In-Reply-To: References: Message-ID: This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --568760595-1096432268-1111178609=:30561 Content-Type: TEXT/PLAIN; charset=ISO-8859-2 Content-Transfer-Encoding: QUOTED-PRINTABLE On Fri, 18 Mar 2005, Mike Brodbelt wrote: > Package: passwd > Version: 1:4.0.3-31sarge1 > Severity: minor >=20 >=20 > "man 5 passwd" produces documentation that is not entirely accurate. The > second paragraph contains the following text:- >=20 > "The encryped password consists of 13 characters > from the 64 character alphabet a thru z, A thru Z, 0 thru 9, > . and /. Refer to crypt(3) for details on how this string is > interpreted." >=20 > This information is clearly incorrect when the system is set to use MD5 > passwords, which is increasingly the case. There's also a typo in > "encrypted". Thanks for report. English isn't my native language so it will be good if someone will verify below patch before I'll commit this to shadow CVS tree. Any volunteers on update non-english passwd(5) ? (pl is mine :o) $ ls -1 */passwd.5 cs/passwd.5 fr/passwd.5 it/passwd.5 ja/passwd.5 ko/passwd.5 pl/passwd.5 ru/passwd.5 --- passwd.5 11 Dec 2004 20:05:01 -0000 1.13 +++ passwd.5 18 Mar 2005 20:25:48 -0000 @@ -48,9 +48,13 @@ .PP The password field may not be filled if shadow passwords have been enabled= =2E If shadow passwords are being used, the encrypted password will be found i= n -\fI/etc/shadow\fR. The encrypted password consists of 13 characters from t= he -64 character alphabet a thru z, A thru Z, 0 thru 9, \. and /. Refer to -\fBcrypt\fR(3) for details on how this string is interpreted. +\fI/etc/shadow\fR. The encrypted password consists of characters from the +64 character alphabet a thru z, A thru Z, 0 thru 9, \. and /. Optionaly it +can start with "$" character. This mean encrypted password was generated +using another (not DES) algorithm. For example if it start with "$1$" it m= eans +MD5-based algorithm was used. +.PP +Refer to \fBcrypt\fR(3) for details on how this string is interpreted. .PP The comment field is used by various system utilities, such as \fBfinger\fR(1). Three additional values may be present in the comment (EN= D) kloczek --=20 ----------------------------------------------------------- *Ludzie nie maj=B1 problem=F3w, tylko sobie sami je stwarzaj=B1* ----------------------------------------------------------- Tomasz K=B3oczko, sys adm @zie.pg.gda.pl|*e-mail: kloczek@rudy.mif.pg.gda.p= l* --568760595-1096432268-1111178609=:30561-- From Nicolas =?iso-8859-1?Q?Fran=E7ois?= , 300268@bugs.debian.org Fri Mar 18 22:18:23 2005 From: Nicolas =?iso-8859-1?Q?Fran=E7ois?= , 300268@bugs.debian.org (Nicolas =?iso-8859-1?Q?Fran=E7ois?=) Date: Fri, 18 Mar 2005 23:18:23 +0100 Subject: [Pkg-shadow-devel] Bug#300268: /usr/share/man/man5/passwd.5.gz contains inaccurate information In-Reply-To: References: Message-ID: <20050318221823.GC5610@nekral.homelinux.net> --3MwIy2ne0vdjdPXF Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hello Tomasz, On Fri, Mar 18, 2005 at 09:43:29PM +0100, Tomasz K=C5=82oczko wrote: > English isn't my native language so it will be good if someone will ver= ify > below patch before I'll commit this to shadow CVS tree. >=20 > --- passwd.5 11 Dec 2004 20:05:01 -0000 1.13 > +++ passwd.5 18 Mar 2005 20:25:48 -0000 > @@ -48,9 +48,13 @@ > .PP > The password field may not be filled if shadow passwords have been ena= bled. > If shadow passwords are being used, the encrypted password will be fou= nd in > -\fI/etc/shadow\fR. The encrypted password consists of 13 characters fr= om the > -64 character alphabet a thru z, A thru Z, 0 thru 9, \. and /. Refer to > -\fBcrypt\fR(3) for details on how this string is interpreted. > +\fI/etc/shadow\fR. The encrypted password consists of characters from = the > +64 character alphabet a thru z, A thru Z, 0 thru 9, \. and /. Optional= y it > +can start with "$" character. This mean encrypted password was generat= ed > +using another (not DES) algorithm. For example if it start with "$1$" = it means > +MD5-based algorithm was used. > +.PP > +Refer to \fBcrypt\fR(3) for details on how this string is interpreted. > .PP > The comment field is used by various system utilities, such as > \fBfinger\fR(1). Three additional values may be present in the comment= (END) English is neither my native language, so the followings are only proposa= ls: s/Optionaly/Optionally/ s/64 character/64 characters/ I would also write "it can start with a "$" character." "This means the encrypted password..." and "For example if it starts ..." BTW, the same correction could be applied to shadow.5 An updated patch is attached. Best Regards, --=20 Nekral --3MwIy2ne0vdjdPXF Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="shadow.patch" --- passwd.5.orig 2005-03-18 22:47:25.000000000 +0100 +++ passwd.5 2005-03-18 22:52:51.000000000 +0100 @@ -48,9 +48,13 @@ .PP The password field may not be filled if shadow passwords have been enabled. If shadow passwords are being used, the encrypted password will be found in -\fI/etc/shadow\fR. The encrypted password consists of 13 characters from the -64 character alphabet a thru z, A thru Z, 0 thru 9, \. and /. Refer to -\fBcrypt\fR(3) for details on how this string is interpreted. +\fI/etc/shadow\fR. The encrypted password consists of characters from the +64 characters alphabet a thru z, A thru Z, 0 thru 9, \. and /. Optionally it +can start with a "$" character. This means the encrypted password was generated +using another (not DES) algorithm. For example if it starts with "$1$" it means +the MD5-based algorithm was used. +.PP +Refer to \fBcrypt\fR(3) for details on how this string is interpreted. .PP The comment field is used by various system utilities, such as \fBfinger\fR(1). Three additional values may be present in the comment --- shadow.5.orig 2005-03-18 22:54:09.000000000 +0100 +++ shadow.5 2005-03-18 22:59:08.000000000 +0100 @@ -51,9 +51,12 @@ A reserved field .PP The password field must be filled. The encryped password consists of 13 to -24 characters from the 64 character alphabet a thru z, A thru Z, 0 thru 9, -\&\. and /. Refer to \fBcrypt\fR(3) for details on how this string is -interpreted. +24 characters from the 64 characters alphabet a thru z, A thru Z, 0 thru 9, +\&\. and /. Optionally it can start with a "$" character. This means the +encrypted password was generated using another (not DES) algorithm. For +example if it starts with "$1$" it means the MD5-based algorithm was used. +.PP +Refer to \fBcrypt\fR(3) for details on how this string is interpreted. .PP The date of the last password change is given as the number of days since Jan 1, 1970. The password may not be changed again until the proper number --3MwIy2ne0vdjdPXF-- From Jari Aalto , 300316@bugs.debian.org Fri Mar 18 22:23:48 2005 From: Jari Aalto , 300316@bugs.debian.org (Jari Aalto) Date: Sat, 19 Mar 2005 00:23:48 +0200 Subject: [Pkg-shadow-devel] Bug#300316: passwd: 4.0.3-30.10 Segmentation fault Message-ID: Package: passwd Version: 1:4.0.3-31sarge1 Severity: serious During upgrade, the package gives segmentation fault. (since apt-get dist-upgrade gave error, I tried directly) /var/cache/apt/archives# dpkg -i passwd_1%3a4.0.3-30.10_i386.deb (Reading database ... 54250 files and directories currently installed.) Preparing to replace passwd 1:4.0.3-30.10 (using passwd_1%3a4.0.3-30.10_i386.deb) ... Unpacking replacement passwd ... Setting up passwd (4.0.3-30.10) ... dpkg: error processing passwd (--install): subprocess post-installation script killed by signal (Segmentation fault) Errors were encountered while processing: passwd -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.10-1-686 Locale: LANG=C, LC_CTYPE=C (charmap=ISO-8859-1) (ignored: LC_ALL set to en_US) Versions of packages passwd depends on: ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an ii libpam-modules 0.76-22 Pluggable Authentication Modules f ii libpam0g 0.76-22 Pluggable Authentication Modules l ii login 1:4.0.3-31sarge1 system login tools -- debconf information excluded From Jari Aalto , 300316@bugs.debian.org Fri Mar 18 22:45:00 2005 From: Jari Aalto , 300316@bugs.debian.org (Jari Aalto) Date: Sat, 19 Mar 2005 00:45:00 +0200 Subject: [Pkg-shadow-devel] Bug#300316: [ignore this bug] Now a passwd problem Message-ID: Package: passwd Version: 1:4.0.3-31sarge1 Followup-For: Bug #300316 Hm, This wasn't upgrade's fault. Something has made the server to act strangely so it did gave core dumps. reboot fixed the situation. Please close the bug. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.10-1-686 Locale: LANG=C, LC_CTYPE=C (charmap=ISO-8859-1) (ignored: LC_ALL set to en_US) Versions of packages passwd depends on: ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an ii libpam-modules 0.76-22 Pluggable Authentication Modules f ii libpam0g 0.76-22 Pluggable Authentication Modules l ii login 1:4.0.3-31sarge1 system login tools -- debconf information excluded From owner@bugs.debian.org Fri Mar 18 23:03:35 2005 From: owner@bugs.debian.org (Debian Bug Tracking System) Date: Fri, 18 Mar 2005 15:03:35 -0800 Subject: [Pkg-shadow-devel] Bug#300316: marked as done (passwd: 4.0.3-30.10 Segmentation fault) In-Reply-To: <20050318225850.GA31698@andromeda> References: <20050318225850.GA31698@andromeda> Message-ID: Your message dated Fri, 18 Mar 2005 17:58:50 -0500 with message-id <20050318225850.GA31698@andromeda> and subject line Bug#300316: [ignore this bug] Now a passwd problem has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -------------------------------------- Received: (at submit) by bugs.debian.org; 18 Mar 2005 22:23:54 +0000 >From jari.aalto@cante.net Fri Mar 18 14:23:54 2005 Return-path: Received: from fep02-0.kolumbus.fi (fep02-app.kolumbus.fi) [193.229.0.44] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1DCPsn-00085h-00; Fri, 18 Mar 2005 14:23:53 -0800 Received: from bongo.cante.net ([81.197.3.110]) by fep02-app.kolumbus.fi with ESMTP id <20050318222351.FVXF8756.fep02-app.kolumbus.fi@bongo.cante.net> for ; Sat, 19 Mar 2005 00:23:51 +0200 Received: from ns2.cante.net ([192.168.1.3]:38438 helo=cante.cante.net) by bongo.cante.net with esmtp (Exim 4.44) id 1DCPsk-0002XW-6q for submit@bugs.debian.org; Sat, 19 Mar 2005 00:23:50 +0200 Received: from jaalto by cante.cante.net with local (Exim 4.50) id 1DCPsj-0003QI-CV for submit@bugs.debian.org; Sat, 19 Mar 2005 00:23:49 +0200 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Jari Aalto To: Debian Bug Tracking System Subject: passwd: 4.0.3-30.10 Segmentation fault X-Mailer: reportbug 3.8 Date: Sat, 19 Mar 2005 00:23:48 +0200 Message-Id: Delivered-To: submit@bugs.debian.org X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2005_01_02 X-Spam-Level: Package: passwd Version: 1:4.0.3-31sarge1 Severity: serious During upgrade, the package gives segmentation fault. (since apt-get dist-upgrade gave error, I tried directly) /var/cache/apt/archives# dpkg -i passwd_1%3a4.0.3-30.10_i386.deb (Reading database ... 54250 files and directories currently installed.) Preparing to replace passwd 1:4.0.3-30.10 (using passwd_1%3a4.0.3-30.10_i386.deb) ... Unpacking replacement passwd ... Setting up passwd (4.0.3-30.10) ... dpkg: error processing passwd (--install): subprocess post-installation script killed by signal (Segmentation fault) Errors were encountered while processing: passwd -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.10-1-686 Locale: LANG=C, LC_CTYPE=C (charmap=ISO-8859-1) (ignored: LC_ALL set to en_US) Versions of packages passwd depends on: ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an ii libpam-modules 0.76-22 Pluggable Authentication Modules f ii libpam0g 0.76-22 Pluggable Authentication Modules l ii login 1:4.0.3-31sarge1 system login tools -- debconf information excluded --------------------------------------- Received: (at 300316-done) by bugs.debian.org; 18 Mar 2005 22:58:56 +0000 >From justinpryzby@users.sourceforge.net Fri Mar 18 14:58:56 2005 Return-path: Received: from ms-smtp-01.nyroc.rr.com [24.24.2.55] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1DCQQi-000872-00; Fri, 18 Mar 2005 14:58:56 -0800 Received: from localhost (cpe-24-59-54-124.twcny.res.rr.com [24.59.54.124]) by ms-smtp-01.nyroc.rr.com (8.12.10/8.12.10) with ESMTP id j2IMwpK3018873; Fri, 18 Mar 2005 17:58:52 -0500 (EST) Received: from pryzbyj by localhost with local (Exim 3.36 #1 (Debian)) id 1DCQQc-0008GL-00; Fri, 18 Mar 2005 17:58:50 -0500 Date: Fri, 18 Mar 2005 17:58:50 -0500 To: Jari Aalto , 300316-done@bugs.debian.org Subject: Re: Bug#300316: [ignore this bug] Now a passwd problem Message-ID: <20050318225850.GA31698@andromeda> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.6+20040907i From: Justin Pryzby X-Virus-Scanned: Symantec AntiVirus Scan Engine Delivered-To: 300316-done@bugs.debian.org X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER autolearn=no version=2.60-bugs.debian.org_2005_01_02 X-Spam-Level: FYI: In the future, you can close a bug by mailing an explanation to N-done@bugs.debian.org, where N is the bug number. Thanks, Justin On Sat, Mar 19, 2005 at 12:45:00AM +0200, Jari Aalto wrote: > Package: passwd > Version: 1:4.0.3-31sarge1 > Followup-For: Bug #300316 > > Hm, This wasn't upgrade's fault. Something has made the server to act strangely so it did gave core dumps. reboot fixed the situation. > > Please close the bug. From owner@bugs.debian.org Sat Mar 19 10:03:29 2005 From: owner@bugs.debian.org (Debian Bug Tracking System) Date: Sat, 19 Mar 2005 02:03:29 -0800 Subject: [Pkg-shadow-devel] Processed: Re: Bug#300268: /usr/share/man/man5/passwd.5.gz contains inaccurate information In-Reply-To: <20050319094943.GM26523@mykerinos.kheops.frmug.org> References: <20050319094943.GM26523@mykerinos.kheops.frmug.org> Message-ID: Processing commands for control@bugs.debian.org: > tags 300268 upstream Bug#300268: /usr/share/man/man5/passwd.5.gz contains inaccurate information There were no tags set. Tags added: upstream > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) From Christian Perrier , 300268@bugs.debian.org Sat Mar 19 09:49:43 2005 From: Christian Perrier , 300268@bugs.debian.org (Christian Perrier) Date: Sat, 19 Mar 2005 10:49:43 +0100 Subject: [Pkg-shadow-devel] Bug#300268: /usr/share/man/man5/passwd.5.gz contains inaccurate information In-Reply-To: References: Message-ID: <20050319094943.GM26523@mykerinos.kheops.frmug.org> tags 300268 upstream thanks Quoting Mike Brodbelt (m.brodbelt@acu.ac.uk): > Package: passwd > Version: 1:4.0.3-31sarge1 > Severity: minor As the following discussions showed, this bug pertains to shadow upstream source. Such bugs will be dealt with when the Debian package will resync with upstream (which is currently being changed by Thomas, who is the upstream author). Hence, I'm tagging this upstream, of course. From arg@online.com.ua Sat Mar 19 19:57:57 2005 From: arg@online.com.ua (Alexander Gattin) Date: Sat, 19 Mar 2005 21:57:57 +0200 Subject: [Pkg-shadow-devel] Bug#300268: /usr/share/man/man5/passwd.5.gz contains inaccurate information In-Reply-To: <20050318221823.GC5610@nekral.homelinux.net> References: <20050318221823.GC5610@nekral.homelinux.net> Message-ID: <20050319195757.GA11797@cherokee.kiev.ua> On Fri, Mar 18, 2005 at 11:18:23PM +0100, Nicolas François wrote: > On Fri, Mar 18, 2005 at 09:43:29PM +0100, Tomasz Kłoczko wrote: > > English isn't my native language so it will be good if someone will verify > > below patch before I'll commit this to shadow CVS tree. ... > > Any volunteers on update non-english passwd(5) ? (pl is > > mine :o) > > > > $ ls -1 */passwd.5 > > cs/passwd.5 > > fr/passwd.5 > > it/passwd.5 > > ja/passwd.5 > > ko/passwd.5 > > pl/passwd.5 > > ru/passwd.5 I may look at Russian/Ukrainian version. But I don't promise, because now I have very urgent jub. > > --- passwd.5 11 Dec 2004 20:05:01 -0000 1.13 > > +++ passwd.5 18 Mar 2005 20:25:48 -0000 > > @@ -48,9 +48,13 @@ > > .PP > > The password field may not be filled if shadow passwords have been enabled. I have a question on the above. What does "may not be" mean? Does it mean slightly stronger negation than "should not be"? Does the phrase relate to _action_ [on the field] or to _state_ [of the field]? If former, then "MUST NOT be" (as for RFC conventions), should probably be used instead. If latter, then "MUST be empty when", or "IS empty when" may be used. Please consider these proposals. > English is neither my native language, I'm third one in your company :)). > so the followings are only proposals: > > s/Optionaly/Optionally/ yes > s/64 character/64 characters/ ? The whole phrase is "64 character alphabet". I'm not at all sure that pl. should be used here. For example: "nine inch nails", not "9 inches nails" and so on. > I would also write "it can start with a "$" character." '_a_ "$" character' -- yes > "This means the encrypted password..." "this mean_s_" -- yes > and "For example if it starts ..." "it start_s_" -- yes > BTW, the same correction could be applied to shadow.5 of course. -- WBR, xrgtn From bubulle@debian.org Sun Mar 20 07:40:13 2005 From: bubulle@debian.org (Christian Perrier) Date: Sun, 20 Mar 2005 08:40:13 +0100 Subject: [Pkg-shadow-devel] Bug#300268: /usr/share/man/man5/passwd.5.gz contains inaccurate information In-Reply-To: <20050319195757.GA11797@cherokee.kiev.ua> References: <20050318221823.GC5610@nekral.homelinux.net> <20050319195757.GA11797@cherokee.kiev.ua> Message-ID: <20050320074009.GF32638@mykerinos.kheops.frmug.org> > > > The password field may not be filled if shadow passwords have been= enabled. >=20 > I have a question on the above. What does "may not be" > mean? > Does it mean slightly stronger negation than "should not > be"? I would say "is likely to be empty if shadow...." PS=A0: probably no need to CC people to answers=A0: Nicolas, Thomas, you (Alexander) and me are all subscribed to pkg-shadow-devel. About the man pages and man pages translation handling=A0: the french team (which I'm part of as well as Nicolas) now uses PO files are original files for manual pages translations. This way this works may be seen in man/fr in the Debian package source tree (you have to "apt-get source shadow" for that.....the CVS we have on Alioth contains this as a patch in debian/patches). I'd like to promote this to upstream (Thomas) for all man pages translation handling.=20 This makes use of the po4a utility which helps in creating man pages from PO files back and forth. The advantage for translators is working on the well-known PO files, with correct handling of upstream changes and a far easier maintenance. po4a is hosted on http://po4a.alioth.debian.org This is not Debian-specific so I think it could be quite easily included in upstream sources. The target is having manual pages translations handled only as PO files and the real man pages generated in the build process (which means calling po4a in Makefiles). From martin.quinson@loria.fr Sun Mar 20 08:54:36 2005 From: martin.quinson@loria.fr (Martin Quinson) Date: Sun, 20 Mar 2005 09:54:36 +0100 Subject: [Pkg-shadow-devel] Bug#300268: /usr/share/man/man5/passwd.5.gz contains inaccurate information In-Reply-To: <20050320074009.GF32638@mykerinos.kheops.frmug.org> References: <20050318221823.GC5610@nekral.homelinux.net> <20050319195757.GA11797@cherokee.kiev.ua> <20050320074009.GF32638@mykerinos.kheops.frmug.org> Message-ID: <20050320085436.GC3779@papagos> --jy6Sn24JjFx/iggw Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Mar 20, 2005 at 08:40:13AM +0100, Christian Perrier wrote: >=20 > I'd like to promote this to upstream (Thomas) for all man pages > translation handling.=20 >=20 > This makes use of the po4a utility which helps in creating man pages > from PO files back and forth. The advantage for translators is working > on the well-known PO files, with correct handling of upstream changes > and a far easier maintenance. >=20 > po4a is hosted on http://po4a.alioth.debian.org >=20 > This is not Debian-specific so I think it could be quite easily > included in upstream sources. The target is having manual pages > translations handled only as PO files and the real man pages generated > in the build process (which means calling po4a in Makefiles). Christian forgot to say that po4a is a team work, and that both me and Nicolas are part of this team. So, we know it rather well and could probably work out any issue arising. Thanks, Mt. --jy6Sn24JjFx/iggw Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQFCPTpMIiC/MeFF8zQRAhG9AJ9j2aC72QDlF7R6QW4QEtuhXRcuJACfbgr6 vgqmskbHWTTGA7fXyvpNJzM= =HmaF -----END PGP SIGNATURE----- --jy6Sn24JjFx/iggw-- From bubulle@debian.org Sun Mar 20 09:08:26 2005 From: bubulle@debian.org (Christian Perrier) Date: Sun, 20 Mar 2005 10:08:26 +0100 Subject: [Pkg-shadow-devel] Bug#300268: /usr/share/man/man5/passwd.5.gz contains inaccurate information In-Reply-To: <20050320085436.GC3779@papagos> References: <20050318221823.GC5610@nekral.homelinux.net> <20050319195757.GA11797@cherokee.kiev.ua> <20050320074009.GF32638@mykerinos.kheops.frmug.org> <20050320085436.GC3779@papagos> Message-ID: <20050320090826.GL32638@mykerinos.kheops.frmug.org> > Christian forgot to say that po4a is a team work, and that both me and > Nicolas are part of this team. So, we know it rather well and could probably > work out any issue arising. While writing this, I indeed forgot that you also are subscribed here, Martin...:-) From bubulle@debian.org Mon Mar 21 07:37:48 2005 From: bubulle@debian.org (Christian Perrier) Date: Mon, 21 Mar 2005 08:37:48 +0100 Subject: [Pkg-shadow-devel] What is in the CVS repository Message-ID: <20050321073748.GM32638@mykerinos.kheops.frmug.org> Fellows, yesterday, I have populated/reorganised the CVS repository we have for the shadow package development on alioth.debian.org Those of you who had a local copy are advised to drop it and re-checkout. Sorry for the trouble. basically, you'll find there: sarge/=A0: the current copy of the whole source tree for the package which is currently in sarge. This is the copy we will continue to maintain the package from, with the release of sarge in mind sid/ =A0: only a debian/ directory. This should be applied to genuine 4.0.3 sources. This should produce the very same package than what's currently in the sarge/ branch All Debian specific changes have been moved in dpatch patches in debian/patches. The idea here is examining them all with the intent to decide whether they are still relevant for 4.0.7 (or further) sources. As far as I have seen up to now, several patches here are either no more relevant (l10n, man pages) because we know they have already been integrated upstream......or outdated because upstream has obviously made the same or similar changes in sources. The goal here is to make some triage in these patches, one by one. We will probably need another "branch" for an experimental package of shoadow 4.0.7. This will be the place where we will move Debian specific patches, one by one, when triaging from the sid branch. I have not used real CVS branches because this would currently add more complication to the process and I don't want to waste time in understanding branching (please don't try to sell me svn, arch or whatever fancy revision control system....this is not the appropriate time now). So, at this moment, please sync with this and tell me about your feelings. Thanks for your attention. --=20 From arg@online.com.ua Sat Mar 19 19:57:57 2005 From: arg@online.com.ua (Alexander Gattin) Date: Sat, 19 Mar 2005 21:57:57 +0200 Subject: [Pkg-shadow-devel] Bug#300268: /usr/share/man/man5/passwd.5.gz contains inaccurate information In-Reply-To: <20050318221823.GC5610@nekral.homelinux.net> References: <20050318221823.GC5610@nekral.homelinux.net> Message-ID: <20050319195757.GA11797@cherokee.kiev.ua> On Fri, Mar 18, 2005 at 11:18:23PM +0100, Nicolas Fran=C3=A7ois wrote: > On Fri, Mar 18, 2005 at 09:43:29PM +0100, Tomasz K=C5=82oczko wrote: > > English isn't my native language so it will be good if someone will v= erify > > below patch before I'll commit this to shadow CVS tree. ... > > Any volunteers on update non-english passwd(5) ? (pl is > > mine :o) > >=20 > > $ ls -1 */passwd.5 > > cs/passwd.5 > > fr/passwd.5 > > it/passwd.5 > > ja/passwd.5 > > ko/passwd.5 > > pl/passwd.5 > > ru/passwd.5 I may look at Russian/Ukrainian version. But I don't promise, because now I have very urgent jub. > > --- passwd.5 11 Dec 2004 20:05:01 -0000 1.13 > > +++ passwd.5 18 Mar 2005 20:25:48 -0000 > > @@ -48,9 +48,13 @@ > > .PP > > The password field may not be filled if shadow passwords have been e= nabled. I have a question on the above. What does "may not be" mean? Does it mean slightly stronger negation than "should not be"? Does the phrase relate to _action_ [on the field] or to _state_ [of the field]? If former, then "MUST NOT be" (as for RFC conventions), should probably be used instead. If latter, then "MUST be empty when", or "IS empty when" may be used. Please consider these proposals. > English is neither my native language, I'm third one in your company :)). > so the followings are only proposals: >=20 > s/Optionaly/Optionally/ yes > s/64 character/64 characters/ ? The whole phrase is "64 character alphabet". I'm not at all sure that pl. should be used here. For example: "nine inch nails", not "9 inches nails" and so on. > I would also write "it can start with a "$" character." '_a_ "$" character' -- yes > "This means the encrypted password..." "this mean_s_" -- yes > and "For example if it starts ..." "it start_s_" -- yes > BTW, the same correction could be applied to shadow.5 of course. --=20 WBR, xrgtn From Javier =?iso-8859-1?Q?Fern=E1ndez-Sanguino_Pe=F1a?= , 300720@bugs.debian.org Mon Mar 21 12:30:15 2005 From: Javier =?iso-8859-1?Q?Fern=E1ndez-Sanguino_Pe=F1a?= , 300720@bugs.debian.org (Javier =?iso-8859-1?Q?Fern=E1ndez-Sanguino_Pe=F1a?=) Date: Mon, 21 Mar 2005 13:30:15 +0100 Subject: [Pkg-shadow-devel] Bug#300720: Login: Configuration does not load limits.so while others do Message-ID: <20050321123014.GA1356@dat.etsit.upm.es> --Qxx1br4bt0+wmkIi Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Package: login Version: 1:4.0.3-31sarge1 Priority: important /etc/pam.d/login does not have the pam_limit module enabled: # Sets up user limits, please uncomment and read /etc/security/limits.conf # to enable this functionality. # (Replaces the use of /etc/limits in old login) # session required pam_limits.so However other pam.d configuration files for common stuff (gdm, ssh, xdm and= =20 suexec) enable it by default. Is there any reason why that pam module is not enabled by default. That=20 seems to be another hurdle in admin's way when he wants to configure=20 user limits as he needs to modify both /etc/security/limits.conf and then= =20 /etc/pam.d/login with no indication in either limits.conf nor=20 /etc/security/limits.conf that this module is not enabled per default in=20 'login'. Regards Javier --Qxx1br4bt0+wmkIi Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQFCPr5Vi4sehJTrj0oRAmi9AJ9+NhHrJg9h7NpUqwyqTo8deaRsCACggxqB PDR3ETDt5y6Qj90PUuaf+ns= =SK6E -----END PGP SIGNATURE----- --Qxx1br4bt0+wmkIi-- From kloczek@zie.pg.gda.pl Mon Mar 21 15:36:15 2005 From: kloczek@zie.pg.gda.pl (Tomasz =?iso-8859-2?Q?K=B3oczko?=) Date: Mon, 21 Mar 2005 16:36:15 +0100 Subject: [Pkg-shadow-devel] Bug#300268: /usr/share/man/man5/passwd.5.gz contains inaccurate information In-Reply-To: <20050320085436.GC3779@papagos> References: <20050318221823.GC5610@nekral.homelinux.net> <20050319195757.GA11797@cherokee.kiev.ua> <20050320074009.GF32638@mykerinos.kheops.frmug.org> <20050320085436.GC3779@papagos> Message-ID: <1111419375.4776.26.camel@test1.zie.pg.gda.pl> Dnia 20-03-2005, nie o godzinie 09:54 +0100, Martin Quinson napisał(a): > On Sun, Mar 20, 2005 at 08:40:13AM +0100, Christian Perrier wrote: > > > > I'd like to promote this to upstream (Thomas) for all man pages > > translation handling. > > > > This makes use of the po4a utility which helps in creating man pages > > from PO files back and forth. The advantage for translators is working > > on the well-known PO files, with correct handling of upstream changes > > and a far easier maintenance. > > > > po4a is hosted on http://po4a.alioth.debian.org > > > > This is not Debian-specific so I think it could be quite easily > > included in upstream sources. The target is having manual pages > > translations handled only as PO files and the real man pages generated > > in the build process (which means calling po4a in Makefiles). > > Christian forgot to say that po4a is a team work, and that both me and > Nicolas are part of this team. So, we know it rather well and could probably > work out any issue arising. I want only inform: on CVS shadow source tree I'm not interested using po4a. I plan convert all shadow man pages documentation to XML (this is much more commont format for documentation) and prepare translation framework basing on this source form. Probably will be used gnome-doc-utils (or something similar). kloczek -- ----------------------------------------------------------- *Ludzie nie mają problemów, tylko sobie sami je stwarzają* ----------------------------------------------------------- Tomasz Kłoczko,sys adm @zie.pg.gda.pl|e-mail:kloczek@rudy.mif.pg.gda.pl* From gps@mittelerde.physik.uni-konstanz.de Mon Mar 21 15:16:41 2005 From: gps@mittelerde.physik.uni-konstanz.de (Gerhard Schrenk) Date: Mon, 21 Mar 2005 16:16:41 +0100 Subject: [Pkg-shadow-devel] Re: adduser --system should add users without expire period In-Reply-To: <20050318171034.GA6544@lefler.int.l21.ma.zugschlus.de> References: <20050310141028.2FC3BC@gandalf.physik.uni-konstanz.de> <20050318171034.GA6544@lefler.int.l21.ma.zugschlus.de> Message-ID: <20050321151641.GA26374@frodo> * Marc Haber [2005-03-18 18:10]: > On Thu, Mar 10, 2005 at 03:10:28PM +0100, Gerhard Schrenk wrote: > > 'adduser --system' adds apparently users with expire and warn period > > from /etc/login.defs > > > > For example it reads the following setting in /etc/login.defs > > PASS_MAX_DAYS 183 > > PASS_MIN_DAYS 0 > > PASS_WARN_AGE 183 > > > > Example: After 1/2 year after upgrading to sarge logcheck (which added a > > new system user) suddenly stopped mailing its reports. > > Yuck. > > Did the account actually have a password? No password. Before I fixed it the shadow entry was gandalf:/.home/gandalf/gps# getent shadow logcheck logcheck:!:12656:0:183:183::: The system account logcheck was not in woody. It has been introduced in unstable/sarge. From /usr/share/doc/logcheck/NEWS.Debian.gz: |logcheck (1.2.19-2) unstable; urgency=low | | * As of version 1.2.19, logcheck no longer runs as root. | Logcheck runs as user logcheck which has been created | and added to group adm upon configuration. | | If you have customized your configuration, | you will need to be sure that your | logs are readable by the logcheck user. I upgraded from woody -> sarge on 26 Aug 2004. On 26 Feb 2004 logcheck stopped mailing. For sshd and sslwrap I had the same insane entries (183:183 instead of 99999:7; without password). > Can you please verify whether useradd -x 99999 will create an account > without that restriction? Um. No. gandalf:/home/gandalf/gps# useradd -x 99999 testit useradd: invalid option -- x usage: useradd [-u uid [-o]] [-g group] [-G group,...] [-d home] [-s shell] [-c comment] [-m [-k template]] [-f inactive] [-e expire ] [-p passwd] name useradd -D [-g group] [-b base] [-s shell] [-f inactive] [-e expire ] Do you mean useradd -e 99999? gandalf:/home/gandalf/gps# grep ^PASS /etc/login.defs PASS_MAX_DAYS 183 PASS_MIN_DAYS 0 PASS_WARN_AGE 183 PASS_MAX_LEN 8 gandalf:/home/gandalf/gps# useradd -e 99999 testit gandalf:/home/gandalf/gps# getent passwd testit testit:x:11322:100::/home/testit: gandalf:/home/gandalf/gps# getent shadow testit testit:!:12863:0:183:183::17324: > The only possible fix for _adduser_ would be to ignore PASS_MAX_DAYS > for system account creation. Is that what you're suggesting? Yes. I think this should be the sane default behaviour for 'adduser --system'. Only adduser and adduser.conf is mentioned in debian policy section 9.2.2 (and neither useradd nor /etc/login.defs). I suppose you should fix this independant of what useradd ist doing. But maybe the right thing is to actually fix useradd?? At least its manpage does not mention /etc/login.defs. Therefore I have cc'ed its maintainers. -- Gerhard From bubulle@debian.org Mon Mar 21 16:53:41 2005 From: bubulle@debian.org (Christian Perrier) Date: Mon, 21 Mar 2005 17:53:41 +0100 Subject: [Pkg-shadow-devel] Bug#300268: /usr/share/man/man5/passwd.5.gz contains inaccurate information In-Reply-To: <1111419375.4776.26.camel@test1.zie.pg.gda.pl> References: <20050318221823.GC5610@nekral.homelinux.net> <20050319195757.GA11797@cherokee.kiev.ua> <20050320074009.GF32638@mykerinos.kheops.frmug.org> <20050320085436.GC3779@papagos> <1111419375.4776.26.camel@test1.zie.pg.gda.pl> Message-ID: <20050321165341.GB8640@mykerinos.kheops.frmug.org> > I plan convert all shadow man pages documentation to XML (this is much > more commont format for documentation) and prepare translation framework > basing on this source form. Probably will be used gnome-doc-utils (or ....which does not prevent using PO format for documentation translation. The PO format is *designed* for translation handling, with good handling of "upstream" changes and impact on translations. All free software translation teams use PO tools for handling translation work because of the wide availability of tools and utilities (compendium, dictionaries, automation tools, web translation projects such as Pootle....) So, while the documentation (including man pages) benefits from being handled from a XML source, translations can still be handled with PO files and gettext utilities. And, yes, po4a also has a XML module (another tool is poxml which is for instance used in Debian installer documentation). So, well, from the translators point of view, handling translations with gettext is really a huge enhancement. From Christian Perrier , 300720@bugs.debian.org Mon Mar 21 16:59:20 2005 From: Christian Perrier , 300720@bugs.debian.org (Christian Perrier) Date: Mon, 21 Mar 2005 17:59:20 +0100 Subject: Bug#300720: [Pkg-shadow-devel] Bug#300720: Login: Configuration does not load limits.so while others do In-Reply-To: <20050321123014.GA1356@dat.etsit.upm.es> References: <20050321123014.GA1356@dat.etsit.upm.es> Message-ID: <20050321165920.GC8640@mykerinos.kheops.frmug.org> Quoting Javier Fern=E1ndez-Sanguino Pe=F1a (jfs@computer.org): > Package: login > Version: 1:4.0.3-31sarge1 > Priority: important >=20 > /etc/pam.d/login does not have the pam_limit module enabled: >=20 > # Sets up user limits, please uncomment and read /etc/security/limits.c= onf > # to enable this functionality. > # (Replaces the use of /etc/limits in old login) > # session required pam_limits.so >=20 > However other pam.d configuration files for common stuff (gdm, ssh, xdm= and=20 > suexec) enable it by default. >=20 > Is there any reason why that pam module is not enabled by default. That= =20 Good question. As the former maintainer has vanished, we may have hard times finding whether this was deliberate or not. Sam (Hartman), have you followed this=A0? I find no useful information in debian/changelog. Anyway, I'm very reluctant to make this change now so it's likely to be post-sarge. Apart from that, I tend to agree with Javier, particularly if other software using PAM have chosen to enable pam_limits From Javier =?iso-8859-1?Q?Fern=E1ndez-Sanguino_Pe=F1a?= , 300720@bugs.debian.org Tue Mar 22 00:05:13 2005 From: Javier =?iso-8859-1?Q?Fern=E1ndez-Sanguino_Pe=F1a?= , 300720@bugs.debian.org (Javier =?iso-8859-1?Q?Fern=E1ndez-Sanguino_Pe=F1a?=) Date: Tue, 22 Mar 2005 01:05:13 +0100 Subject: Bug#300720: [Pkg-shadow-devel] Bug#300720: Login: Configuration does not load limits.so while others do In-Reply-To: <20050321165920.GC8640@mykerinos.kheops.frmug.org> References: <20050321123014.GA1356@dat.etsit.upm.es> <20050321165920.GC8640@mykerinos.kheops.frmug.org> Message-ID: <20050322000513.GA26365@dat.etsit.upm.es> --vkogqOf2sHV7VnPd Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Mar 21, 2005 at 05:59:20PM +0100, Christian Perrier wrote: > Good question. As the former maintainer has vanished, we may have hard > times finding whether this was deliberate or not. It was probably deliberate at some point because it might have an issue=20 with that. If that was the case it's no longer true. > Anyway, I'm very reluctant to make this change now so it's likely to > be post-sarge. Apart from that, I tend to agree with Javier, > particularly if other software using PAM have chosen to enable > pam_limits It's a very safe change, actually, I asked this to the cron package=20 maintainer too (see #300725) and he has no issue changing that package. Regards Javier --vkogqOf2sHV7VnPd Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQFCP2E3i4sehJTrj0oRAlp1AJ9F7y/WMX8RTLyXk5Jw5OmwLC8VawCfZjle x2hctSYldKtelhLlhU+0QW0= =V9AI -----END PGP SIGNATURE----- --vkogqOf2sHV7VnPd-- From Christian Perrier , 300720@bugs.debian.org Tue Mar 22 05:44:12 2005 From: Christian Perrier , 300720@bugs.debian.org (Christian Perrier) Date: Tue, 22 Mar 2005 06:44:12 +0100 Subject: Bug#300720: [Pkg-shadow-devel] Bug#300720: Login: Configuration does not load limits.so while others do In-Reply-To: <20050322000513.GA26365@dat.etsit.upm.es> References: <20050321123014.GA1356@dat.etsit.upm.es> <20050321165920.GC8640@mykerinos.kheops.frmug.org> <20050322000513.GA26365@dat.etsit.upm.es> Message-ID: <20050322054412.GO8640@mykerinos.kheops.frmug.org> Quoting Javier Fern=E1ndez-Sanguino Pe=F1a (jfs@computer.org): > > Anyway, I'm very reluctant to make this change now so it's likely to > > be post-sarge. Apart from that, I tend to agree with Javier, > > particularly if other software using PAM have chosen to enable > > pam_limits >=20 > It's a very safe change, actually, I asked this to the cron package=20 > maintainer too (see #300725) and he has no issue changing that package. Steve (Grrenland, cron maintainer), input=A0? Javier asked for shadow to be changed to have the PAM configuration for login to use pam_limits.so and points me to the change he asked you about this. shadow (and login) being part of the base system, I'm very conservative about any change, while we are so close of the release. So, Steve, do you plan to push this in sarge, or only make the change in sid? In any case, I'll also request the advice of the release team... From martin.quinson@loria.fr Tue Mar 22 09:46:22 2005 From: martin.quinson@loria.fr (Martin Quinson) Date: Tue, 22 Mar 2005 10:46:22 +0100 Subject: [Pkg-shadow-devel] Bug#300268: /usr/share/man/man5/passwd.5.gz contains inaccurate information In-Reply-To: <20050321165341.GB8640@mykerinos.kheops.frmug.org> References: <20050318221823.GC5610@nekral.homelinux.net> <20050319195757.GA11797@cherokee.kiev.ua> <20050320074009.GF32638@mykerinos.kheops.frmug.org> <20050320085436.GC3779@papagos> <1111419375.4776.26.camel@test1.zie.pg.gda.pl> <20050321165341.GB8640@mykerinos.kheops.frmug.org> Message-ID: <20050322094622.GB4714@papagos> --dc+cDN39EJAMEtIO Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Mar 21, 2005 at 05:53:41PM +0100, Christian Perrier wrote: >=20 > > I plan convert all shadow man pages documentation to XML (this is much > > more commont format for documentation) and prepare translation framework > > basing on this source form. Probably will be used gnome-doc-utils (or >=20 > ....which does not prevent using PO format for documentation > translation. The PO format is *designed* for translation handling, > with good handling of "upstream" changes and impact on > translations. For example, we could try to convert shadow to po4a/man, then change the canonical format from man pages to xml and with a *bit of luck*, the previous translations could be saved and reused in po4a/xml with a minimal amount of work from the translator perspective. Bye, Mt. --dc+cDN39EJAMEtIO Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQFCP+luIiC/MeFF8zQRAsIkAJ48be2q09P3wQKcI3KYZBXK0koQAQCggo88 Rcx/f5D6aP/vRRhK+KjLjzU= =4+bD -----END PGP SIGNATURE----- --dc+cDN39EJAMEtIO-- From Steve Greenland , 300720@bugs.debian.org Tue Mar 22 13:33:57 2005 From: Steve Greenland , 300720@bugs.debian.org (Steve Greenland) Date: Tue, 22 Mar 2005 07:33:57 -0600 Subject: Bug#300720: Bug#300725: Bug#300720: [Pkg-shadow-devel] Bug#300720: Login: Configuration does not load limits.so while others do In-Reply-To: <20050322054412.GO8640@mykerinos.kheops.frmug.org> References: <20050321123014.GA1356@dat.etsit.upm.es> <20050321165920.GC8640@mykerinos.kheops.frmug.org> <20050322000513.GA26365@dat.etsit.upm.es> <20050322054412.GO8640@mykerinos.kheops.frmug.org> Message-ID: <20050322133357.GA9604@moregruel.net> On 21-Mar-05, 23:44 (CST), Christian Perrier wrote: > Quoting Javier Fern?ndez-Sanguino Pe?a (jfs@computer.org): > > It's a very safe change, actually, I asked this to the cron package > > maintainer too (see #300725) and he has no issue changing that package. > > Steve (Grrenland, cron maintainer), input?? > > Javier asked for shadow to be changed to have the PAM configuration > for login to use pam_limits.so and points me to the change he asked > you about this. > > shadow (and login) being part of the base system, I'm very > conservative about any change, while we are so close of the release. > > So, Steve, do you plan to push this in sarge, or only make the change > in sid? I was not planning on pushing this into sid. While I think that Javier is correct, I don't see it as necessary for sarge; it can easily be corrected on a local basis. OTOH, if the release team says "yes, please do it", I wouldn't object: it *is* about safe as a change can be. Steve -- Steve Greenland The irony is that Bill Gates claims to be making a stable operating system and Linus Torvalds claims to be trying to take over the world. -- seen on the net From Gerhard Schrenk , 300892-maintonly@bugs.debian.org Tue Mar 22 14:45:14 2005 From: Gerhard Schrenk , 300892-maintonly@bugs.debian.org (Gerhard Schrenk) Date: Tue, 22 Mar 2005 15:45:14 +0100 Subject: [Pkg-shadow-devel] Bug#300892: passwd: Missing references to /etc/login.defs and login.defs(5) in diverse manpages Message-ID: Package: passwd Version: 1:4.0.3-30.7 Severity: minor Hi, in login.defs(5) there is a nice cross reference which programs in the shadow password suite use which parameters. I have checked the manpages of the different programes for missing references. Especially the missing references in FILES and SEE ALSO sections are annoying. chfn(1): login.defs(5) [missing]; /etc/login.defs [ok]; CHFN_AUTH CHFN_RESTRICT [missing] chsh(1): login.defs(5) [missing]; /etc/login.defs [missing]; CHFN_AUTH [missing] groupadd(8): login.defs(5) [missing]; /etc/login.defs [missing]; GID_MAX GID_MIN [missing] newusers(8): login.defs(5) [missing]; /etc/login.defs [missing]; PASS_MAX_DAYS [missing]; PASS_MIN_DAYS [missing]; PASS_WARN_AGE UMASK [missing] pwconv(8): login.defs(5) [ok]; /etc/login.defs [ok but no FILE-section]; PASS_MAX_DAYS [ok]; PASS_MIN_DAYS [ok]; PASS_WARN_AGE [ok] useradd(8): login.defs(5) [missing]; /etc/login.defs [missing]; CREATE_HOME [missing]; GID_MAX [missing]; GID_MIN [missing]; PASS_MAX_DAYS [missing]; PASS_MIN_DAYS [missing]; PASS_WARN_AGE [missing]; UID_MAX [missing]; UID_MIN [missing]; UMASK [missing] userdel(8): login.defs(5) [missing]; /etc/login.defs [missing]; MAIL_DIR [missing]; USERDEL_CMD [missing] usermod(8): login.defs(5) [missing]; /etc/login.defs [missing]; MAIL_DIR [missing] -- Gerhard -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.4.29-ow1-clients Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1) Versions of packages passwd depends on: ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an ii libpam-modules 0.76-22 Pluggable Authentication Modules f ii libpam0g 0.76-22 Pluggable Authentication Modules l ii login 1:4.0.3-30.7 System login tools -- debconf information: passwd/password-mismatch: passwd/username: passwd/password-empty: passwd/make-user: true passwd/md5: false passwd/shadow: true passwd/username-bad: passwd/user-fullname: From owner@bugs.debian.org Tue Mar 22 18:18:34 2005 From: owner@bugs.debian.org (Debian Bug Tracking System) Date: Tue, 22 Mar 2005 10:18:34 -0800 Subject: Processed: Re: [Pkg-shadow-devel] Bug#300892: passwd: Missing references to /etc/login.defs and login.defs(5) in diverse manpages In-Reply-To: <20050322170650.GC20159@mykerinos.kheops.frmug.org> References: <20050322170650.GC20159@mykerinos.kheops.frmug.org> Message-ID: Processing commands for control@bugs.debian.org: > tags 300892 upstream Bug#300892: passwd: Missing references to /etc/login.defs and login.defs(5) in diverse manpages There were no tags set. Tags added: upstream > retitle 300892 [POST-SARGE] passwd: Missing references to /etc/login.defs and login.defs(5) in diverse manpages Bug#300892: passwd: Missing references to /etc/login.defs and login.defs(5) in diverse manpages Changed Bug title. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) From owner@bugs.debian.org Tue Mar 22 18:18:38 2005 From: owner@bugs.debian.org (Debian Bug Tracking System) Date: Tue, 22 Mar 2005 10:18:38 -0800 Subject: [Pkg-shadow-devel] Processed: retitle 280212 to [POST-SARGE] lastlog: fails when high UID's present In-Reply-To: <20050322173324.DA45223281@mykerinos.kheops.frmug.org> References: <20050322173324.DA45223281@mykerinos.kheops.frmug.org> Message-ID: Processing commands for control@bugs.debian.org: > # Automatically generated email from bts, devscripts version 2.8.10 > retitle 280212 [POST-SARGE] lastlog: fails when high UID's present Bug#280212: lastlog: fails when high UID's present Changed Bug title. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) From owner@bugs.debian.org Tue Mar 22 18:18:43 2005 From: owner@bugs.debian.org (Debian Bug Tracking System) Date: Tue, 22 Mar 2005 10:18:43 -0800 Subject: [Pkg-shadow-devel] Processed: Re: Bug#298060: Please don't install login as setuid root In-Reply-To: <20050322165434.GB20159@mykerinos.kheops.frmug.org> References: <20050322165434.GB20159@mykerinos.kheops.frmug.org> Message-ID: Processing commands for control@bugs.debian.org: > retitle 298060 [POST-SARGE] Please don't install login as setuid root Bug#298060: Please don't install login as setuid root Changed Bug title. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) From Christian Perrier , 300720@bugs.debian.org Tue Mar 22 16:53:13 2005 From: Christian Perrier , 300720@bugs.debian.org (Christian Perrier) Date: Tue, 22 Mar 2005 17:53:13 +0100 Subject: Bug#300720: Bug#300725: Bug#300720: [Pkg-shadow-devel] Bug#300720: Login: Configuration does not load limits.so while others do In-Reply-To: <20050322133357.GA9604@moregruel.net> References: <20050321123014.GA1356@dat.etsit.upm.es> <20050321165920.GC8640@mykerinos.kheops.frmug.org> <20050322000513.GA26365@dat.etsit.upm.es> <20050322054412.GO8640@mykerinos.kheops.frmug.org> <20050322133357.GA9604@moregruel.net> Message-ID: <20050322165313.GA20159@mykerinos.kheops.frmug.org> > I was not planning on pushing this into sid. While I think that Javier > is correct, I don't see it as necessary for sarge; it can easily be > corrected on a local basis. OTOH, if the release team says "yes, please > do it", I wouldn't object: it *is* about safe as a change can be. I am about the same mood, indeed. I'm highly confident in Javier judgement, for sure but as you mention, this is as safe as any change and we're indeed talking about a package in the base system (login). I'm quite reluctant asking the release team as I bet they would finally say "do just like you feel is the most appropriate" and thus I don't really want to add mroe load on their shoulders. For another situation related to the login package (dropping the setuid bit from login), I have finally concluded to delay this post-sarge. So, I think I'll do the same here.....unless other comments convince me to change my mind.... From Christian Perrier , 300892-maintonly@bugs.debian.org Tue Mar 22 17:06:50 2005 From: Christian Perrier , 300892-maintonly@bugs.debian.org (Christian Perrier) Date: Tue, 22 Mar 2005 18:06:50 +0100 Subject: Bug#300892: [Pkg-shadow-devel] Bug#300892: passwd: Missing references to /etc/login.defs and login.defs(5) in diverse manpages In-Reply-To: References: Message-ID: <20050322170650.GC20159@mykerinos.kheops.frmug.org> tags 300892 upstream retitle 300892 [POST-SARGE] passwd: Missing references to /etc/login.defs and login.defs(5) in diverse manpages thanks Quoting Gerhard Schrenk (gps@mittelerde.physik.uni-konstanz.de): > Package: passwd > Version: 1:4.0.3-30.7 > Severity: minor > > Hi, > > in login.defs(5) there is a nice cross reference which programs in the shadow > password suite use which parameters. I have checked the manpages of the > different programes for missing references. Especially the missing references > in FILES and SEE ALSO sections are annoying. Thanks for the useful summary. Given that Thomasz, upstream author of shadow, now follows the Debian package bug reports, I guess he will follow your suggestions (as far as I can see from his CVS, the discrepencies are in upstream as well, hence tagging this bug report). I guess this will be fixed when we will sync back with upstream, which is of course a post-sarge issue. Thomasz, could you please just ACK this so that I can tag the bug as "forwarded to upstream author"? If you want to establish work methods for such bugs coming from the Debian BTS and fit them nicely with your own way to deal with bug reports on shadow, please feel free to mention this. I would prefer any method involving not being online because I use to make my daily work on Debian packages with no net connection but, well, I'll deal with it if that's not possible. From Kevin Ryde , 300973-maintonly@bugs.debian.org Tue Mar 22 23:25:46 2005 From: Kevin Ryde , 300973-maintonly@bugs.debian.org (Kevin Ryde) Date: Wed, 23 Mar 2005 10:25:46 +1100 Subject: [Pkg-shadow-devel] Bug#300973: login: italian man page formatting typo Message-ID: <8764zjmfet.fsf@zip.com.au> Package: login Version: 1:4.0.3-31sarge1 Severity: minor "man -L it login" produces zsoelim: /tmp/zmankB1P9e:262: me.dom.: No such file or directory zsoelim: me.dom..gz: No such file or directory zsoelim: /tmp/zmankB1P9e:262: warning: failed .so request /tmp/zmankB1P9e:262: can't open `me.dom.': No such file or directory I think abbia il suffisso .some.dom. should be abbia il suffisso .some.dom. so it doesn't look like a ".so" formatting directive. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i586) Kernel: Linux 2.6.10-1-386 Locale: LANG=C, LC_CTYPE=C (charmap=ISO-8859-1) (ignored: LC_ALL set to en_AU) Versions of packages login depends on: ii libc6 2.3.2.ds1-18 GNU C Library: Shared libraries an ii libpam-modules 0.76-22 Pluggable Authentication Modules f ii libpam-runtime 0.76-22 Runtime support for the PAM librar ii libpam0g 0.76-22 Pluggable Authentication Modules l -- no debconf information From bubulle@debian.org Wed Mar 23 06:19:47 2005 From: bubulle@debian.org (Christian Perrier) Date: Wed, 23 Mar 2005 07:19:47 +0100 Subject: [Pkg-shadow-devel] News from (Alioth) CVS Message-ID: <20050323061947.GN20159@mykerinos.kheops.frmug.org> (the CVS here is not upstream CVS but our CVS for the Debian package development on Alioth. It can be checked out by "CVS_RSH=3Dssh cvs -d bubulle@alioth.debian.org:/cvsroot/pkg-shadow co ."...replace "bubulle" by your Alioth login) I continue working to prepare the future work on the shadow package.... Yesterday, I worked in the "sid" branch. As already mentioned, you will find there the future "debian/" directory for releases of the package which will follow what we currently have in sarge (4.0.3-31sarge1). This version will be 4.0.3-32. It consists of a switch to dpatch for handling Debian specific patches (OK, Martin, I know you don't like dpatch, but this is what I've used on my other packages...:-))). Target=A0: move ALL Debian-specific things in debian/ directory and DO NOT TOUCH the original directories....thus improving readability. The target currently is getting 4.0.3-32 exactly similar to 4.0.3-31sarge1. For checking this: In an empty directory=A0: -"apt-get source shadow" This will give you the source tree of 4.0.3-31sarge1 in "shadow-4.0.3-31sarge1" Indeed, the very same thing that is in the sarge/ directory of the CVS -mv shadow-4.0.3 shadow-4.0.3-31sarge1 -tar xvfz shadow_4.0.3.orig.tar.gz This will give you the original source tree of shadow 4.0.3 upstream in shadow-4.0.3 -copy there the debian/ directory from the sid branch -from there, run: debian/rules patch Then comparing both directories (shadow-4.0.3-31sarge1 and shadow-4.0.3) should give you the same result (except the debian/ directory). This can be checked with diff. The next step will be going into debian/patches in this sid/ directory and look these patches one by one with your help..... --=20 From Christian Perrier , 300973-maintonly@bugs.debian.org Wed Mar 23 06:09:41 2005 From: Christian Perrier , 300973-maintonly@bugs.debian.org (Christian Perrier) Date: Wed, 23 Mar 2005 07:09:41 +0100 Subject: Bug#300973: [Pkg-shadow-devel] Bug#300973: login: italian man page formatting typo In-Reply-To: <8764zjmfet.fsf@zip.com.au> References: <8764zjmfet.fsf@zip.com.au> Message-ID: <20050323060941.GM20159@mykerinos.kheops.frmug.org> tags 300973 upstream retitle 300973 [POST-SARGE] login: italian man page formatting typo thanks Quoting Kevin Ryde (user42@zip.com.au): > Package: login > Version: 1:4.0.3-31sarge1 > Severity: minor >=20 > "man -L it login" produces .../... I confirm this is also in upstream sources, hence tagging this bug report and triaging it. Tomasz, here we go again, please tell me if I need to do something for you to record the BR in your own BTS ot TODO list. PS=A0: this bug report seems to come from a systematic test campaign of man pages by Kevin Ryde. I've seen numerous other such bug reports by him for other packages, for formatting issues with man pages. So, it seems that this error is the only one for shadow...:-) From Christian Perrier , 277750@bugs.debian.org Wed Mar 23 08:43:57 2005 From: Christian Perrier , 277750@bugs.debian.org (Christian Perrier) Date: Wed, 23 Mar 2005 09:43:57 +0100 Subject: [Pkg-shadow-devel] Bug#277750: Shorten down the Dutch translation of the root password question dialog in package shadow Message-ID: <20050323084357.GD18053@mykerinos.kheops.frmug.org> --wzJLGUyc3ArbnUjN Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by onera.onera.fr id j2N8iNk9026415 Dear Dutch language team, In #277750, I reported a bug about a too long dialog box for the root password dialog. This dialog is used in standard installs and having it too long may confuse users. Please find attached the relevant nl.po file. Could you take care of shortening it. As the shadow package maintainer now (along with the maintenance team), I believe I get get this fixed in time for sarge even if I stupidely forgot about this and more stupidely forgot to CC you when reporting the bug. PS=A0: I didn't recheck since I reported this...so I assume the dialog is still too long but indeed, I'm not completely sure of that. --=20 --wzJLGUyc3ArbnUjN Content-Type: application/x-gettext Content-Disposition: attachment; filename="nl.po" Content-Transfer-Encoding: quoted-printable #=0A# Translators, if you are not familiar with the PO format, gettext= =0A# documentation is worth reading, especially sections dedicated to=0A= # this format, e.g. by running:=0A# info -n '(gettext)PO Files'= =0A# info -n '(gettext)Header Entry'=0A#=0A# Some information sp= ecific to po-debconf are available at=0A# /usr/share/doc/po-debc= onf/README-trans=0A# or http://www.debian.org/intl/l10n/po-debconf/= README-trans=0A#=0A# Developers do not need to manually edit POT or PO f= iles.=0A#=0Amsgid ""=0Amsgstr ""=0A"Project-Id-Version: shadow\n"=0A"Report= -Msgid-Bugs-To: \n"=0A"POT-Creation-Date: 2004-06-01 00:42-0300\n"=0A"PO-Re= vision-Date: 2004-04-23 11:47+0100\n"=0A"Last-Translator: Bart Cornelis \n"=0A"Language-Team: debian-l10n-dutch \n"=0A"MIME-Version: 1.0\n"=0A"Content-Type: text/plain; cha= rset=3DISO-8859-15\n"=0A"Content-Transfer-Encoding: 8bit\n"=0A=0A#. Type: p= assword=0A#. Description=0A#: ../passwd.templates:3=0Amsgid "Root password:= "=0Amsgstr "Beheerderswachtwoord (root):"=0A=0A#. Type: password=0A#. Descr= iption=0A#: ../passwd.templates:3=0Amsgid ""=0A"You need to set a password = for 'root', the system administrative account. A "=0A"malicious or unqualif= ied user with root access can have disastrous results, "=0A"so you should t= ake care to choose a root password that is not easy to guess. "=0A"It shoul= d not be a word found in the dictionary, or a word that could be "=0A"easil= y associated with you, like your middle name. A good password will "=0A"con= tain a mixture of letters, numbers and punctuation and will be changed at "= =0A"regular intervals. The root password is changed by running the 'passwd'= "=0A"program as root."=0Amsgstr ""=0A"Er dient nu een wachtwoord gekozen t= e worden voor de beheerdersaccount "=0A"('root'). Omdat een onwetende of kw= aadwillende gebruiker die zich als "=0A"beheerder aanmeldt rampzalige gevol= gen kan hebben is het belangrijk dat het "=0A"beheerderswachtwoord moeilijk= te raden is. Dit houdt in dat het geen woord "=0A"uit het woordenboek, of = iets dat makkelijk met u te associ=EBren valt "=0A"(banknummer, geboorte da= tum, tweede of derde voornaam, huisdier, ...) mag "=0A"zijn. Een ideaal wac= htwoord bevat een mengeling van letters, cijfers, "=0A"leestekens en specia= le tekens. Een relatief goede manier om een wachtwoord "=0A"te bedenken is = om van een lange zin, of een kort verhaaltje telkens de "=0A"eerste letter = (of de tweede, of de laatste, ...) van elk woord te nemen, "=0A"waarbij je = leestekens laat staan, en een willekeurige letter vervangt door "=0A"een sp= eciaal teken (vb. $ voor s). U kunt het wachtwoord van root later "=0A"vera= nderen door het commando 'passwd' uit te voeren als root."=0A=0A#. Type: pa= ssword=0A#. Description=0A#: ../passwd.templates:3=0Amsgid "Note that you w= ill not be able to see the password as you type it."=0Amsgstr "Merk op dat = u het wachtwoord niet kunt zien terwijl u het typt."=0A=0A#. Type: password= =0A#. Description=0A#: ../passwd.templates:17=0Amsgid ""=0A"Please enter th= e same root password again to verify that you have typed it "=0A"correctly.= "=0Amsgstr ""=0A"Gelieve het beheerderswachtwoord nogmaals in te tikken (te= neinde de "=0A"afwezigheid van tikfouten na te gaan)."=0A=0A#. Type: boolea= n=0A#. Description=0A#: ../passwd.templates:24=0Amsgid "Create a normal use= r account now?"=0Amsgstr "Wilt u nu een normale gebruikersaccount aanmaken?= "=0A=0A#. Type: boolean=0A#. Description=0A#: ../passwd.templates:24=0Amsgi= d ""=0A"It's a bad idea to use the root account for normal day-to-day activ= ities, "=0A"such as the reading of electronic mail, because even a small mi= stake can "=0A"result in disaster. You should create a normal user account = to use for those "=0A"day-to-day tasks."=0Amsgstr ""=0A"Het is een slecht i= dee om de beheerders-account (root) te gebruiken voor "=0A"alledaagse activ= iteiten zoals het lezen van e-mail. De reden hiervoor is dat "=0A"zelfs een= kleine fout rampzalige gevolgen kan hebben wanneer die gemaakt "=0A"wordt = als 'root'. Het is aan te raden om nu een normale gebruikersaccount "=0A"aa= n te maken voor die dagdagelijkse taken."=0A=0A#. Type: boolean=0A#. Descri= ption=0A#: ../passwd.templates:24=0Amsgid ""=0A"Note that you may create it= later (as well as any additional account) by "=0A"typing 'adduser ' as root, where is an user name, like "=0A"'imurdock' or 'rms= '."=0Amsgstr ""=0A"Merk op dat u later nog gewone gebruikers kunt aanmaken = met het commando "=0A"'adduser ', waarbij = de loginnaam is voor de "=0A"nieuwe account (vb. 'imurdock' of 'rms')."=0A= =0A#. Type: string=0A#. Description=0A#: ../passwd.templates:36=0Amsgid "En= ter a username for your account:"=0Amsgstr "Wat is de gebruikersnaam voor u= w account?"=0A=0A#. Type: string=0A#. Description=0A#: ../passwd.templates:= 36=0Amsgid ""=0A"Select a username for the new account. Your first name is = a reasonable "=0A"choice. The username should start with a lower-case lette= r, which can be "=0A"followed by any combination of numbers and more lower-= case letters."=0Amsgstr ""=0A"Wat is de gebruikersnaam voor de nieuwe accou= nt? Uw voornaam is een "=0A"redelijke keuze. Merk op dat de gebruikersnamen= dienen te bestaan uit een "=0A"kleine letter eventueel gevolgd door een co= mbinatie van kleine letters en "=0A"cijfers."=0A=0A#. Type: note=0A#. Descr= iption=0A#: ../passwd.templates:43=0Amsgid "Invalid username entered."=0Ams= gstr "De ingevoerde gebruikersnaam is ongeldig."=0A=0A#. Type: note=0A#. De= scription=0A#: ../passwd.templates:43=0Amsgid ""=0A"The user name you enter= ed is invalid. Note that usernames must start with a "=0A"lower-case letter= , which can be followed by any combination of numbers and "=0A"more lower-c= ase letters."=0Amsgstr ""=0A"De door u ingevoerde gebruikersnaam is ongeldi= g. Merk op dat de "=0A"gebruikersnamen dienen te bestaan uit een kleine let= ter eventueel gevolgd "=0A"een combinatie van kleine letters en cijfers."= =0A=0A#. Type: string=0A#. Description=0A#: ../passwd.templates:50=0Amsgid = "Enter a full name for the new user:"=0Amsgstr "Wat is de volledige naam va= n de nieuwe gebruiker?"=0A=0A#. Type: string=0A#. Description=0A#: ../passw= d.templates:50=0Amsgid ""=0A"A user account will be created for you to use = instead of the root account "=0A"for non-administrative activities."=0Amsgs= tr ""=0A"Er wordt een gebruikersaccount voor u aangemaakt. Het is sterk aan= te raden "=0A"om deze te gebruiken (i.p.v. de beheerdersaccount) wanneer u= niet met het "=0A"beheer van dit systeem bezig bent."=0A=0A#. Type: passwo= rd=0A#. Description=0A#: ../passwd.templates:56=0Amsgid "Enter a password f= or the new user:"=0Amsgstr "Wat is het wachtwoord voor de nieuwe gebruiker?= "=0A=0A#. Type: password=0A#. Description=0A#: ../passwd.templates:56=0Amsg= id ""=0A"A good password will contain a mixture of letters, numbers and pun= ctuation "=0A"and will be changed at regular intervals."=0Amsgstr ""=0A"Een= goed wachtwoord bevat een mengeling van letters, cijfers, leestekens, en "= =0A"speciale tekens, en wordt regelmatig veranderd."=0A=0A#. Type: password= =0A#. Description=0A#: ../passwd.templates:62=0Amsgid "Re-enter password to= verify:"=0Amsgstr "Wachtwoord nogmaals (ter bevestiging):"=0A=0A#. Type: p= assword=0A#. Description=0A#: ../passwd.templates:62=0Amsgid ""=0A"Please e= nter the same user password again to verify you have typed it "=0A"correctl= y."=0Amsgstr ""=0A"Gelieve hetzelfde wachtwoord nogmaals in te voeren, dit = om na te gaan dat er "=0A"geen tikfouten gemaakt werden."=0A=0A#. Type: not= e=0A#. Description=0A#: ../passwd.templates:68=0Amsgid "Password input erro= r."=0Amsgstr "Wachtwoord-invoerfout."=0A=0A#. Type: note=0A#. Description= =0A#: ../passwd.templates:68=0Amsgid "The two passwords you entered were no= t the same. Please try again."=0Amsgstr ""=0A"De twee door u ingevoerde wac= htwoorden waren kwamen niet overeen. Gelieve "=0A"nogmaals te proberen."=0A= =0A#. Type: note=0A#. Description=0A#: ../passwd.templates:73=0Amsgid "Empt= y password was entered."=0Amsgstr "Het ingevoerde wachtwoord was leeg."=0A= =0A#. Type: note=0A#. Description=0A#: ../passwd.templates:73=0Amsgid ""=0A= "You seem to have entered nothing for the password. That is not secure! "= =0A"Please try again."=0Amsgstr ""=0A"U heeft niks ingevoerd voor het wacht= woord. Dit is niet veilig! Gelieve "=0A"opnieuw te proberen."=0A=0A#. Type:= boolean=0A#. Description=0A#: ../passwd.templates:80=0Amsgid "Enable shado= w passwords?"=0Amsgstr "Wilt u schaduwwachtwoorden activeren?"=0A=0A#. Type= : boolean=0A#. Description=0A#: ../passwd.templates:80=0Amsgid ""=0A"Shadow= passwords make your system more secure because nobody is able to view "=0A= "even encrypted passwords. Passwords are stored in a separate file that can= "=0A"only be read by special programs. The use of shadow passwords is stro= ngly "=0A"recommended. However, if you're going to use NIS you could run in= to trouble."=0Amsgstr ""=0A"Schaduwwachtwoorden maken uw systeem veiliger o= mdat dan zelfs de "=0A"versleutelde versies van de wachtwoorden door nieman= d gezien kunnen worden. "=0A"Bij het gebruik van schaduwwachtwoorden worden= de versleutelde wachtwoorden "=0A"opgeslagen in een apart bestand dat enke= l door speciale programma's gelezen "=0A"kan worden. Het gebruik van schadu= wwachtwoorden is ten sterkste aan te "=0A"raden. Al kan dit wel problemen o= pleveren als u NIS gebruikt."=0A=0A#. Type: boolean=0A#. Description=0A#: .= =2E/passwd.templates:90=0Amsgid "Enable md5 passwords?"=0Amsgstr "Wilt u md= 5-wachtwoorden activeren?"=0A=0A#. Type: boolean=0A#. Description=0A#: ../p= asswd.templates:90=0Amsgid ""=0A"Md5 passwords are more secure and allow fo= r passwords longer than 8 "=0A"characters to be used. However, they can cau= se compatibility problems if you "=0A"are using NIS or sharing password fil= es with older systems."=0Amsgstr ""=0A"MD5-wachtwoorden zijn veiliger en la= ten toe wachtwoorden van meer dan 8 "=0A"tekens te gebruiken. Indien u NIS = gebruikt of wachtwoordbestanden deelt met "=0A"oudere systemen kan dit wel = compatibiliteitsproblemen opleveren."=0A=0A#~ msgid "Enter the full name of= the new user."=0A#~ msgstr ""=0A#~ "Hier dient u de volledige naam van de = nieuwe gebruiker in te voeren."=0A --wzJLGUyc3ArbnUjN-- From Luk Claes , 277750@bugs.debian.org Wed Mar 23 10:38:39 2005 From: Luk Claes , 277750@bugs.debian.org (Luk Claes) Date: Wed, 23 Mar 2005 11:38:39 +0100 Subject: [Pkg-shadow-devel] Bug#277750: Shorten down the Dutch translation of the root password question dialog in package shadow In-Reply-To: <20050323084357.GD18053@mykerinos.kheops.frmug.org> References: <20050323084357.GD18053@mykerinos.kheops.frmug.org> Message-ID: <4241472F.6020709@ugent.be> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Christian Perrier wrote: | Dear Dutch language team, Hi Christian ;-) | In #277750, I reported a bug about a too long dialog box for the root | password dialog. | | This dialog is used in standard installs and having it too long may | confuse users. | | Please find attached the relevant nl.po file. Could you take care of | shortening it. Maybe we can change it from "Beheerderswachtwoord (root):" to "Wachtwoord voor root:"? | As the shadow package maintainer now (along with the maintenance | team), I believe I get get this fixed in time for sarge even if I | stupidely forgot about this and more stupidely forgot to CC you when | reporting the bug. You still hope to break things? ;-) A Cc would indeed have been better, but the past is gone... | PS : I didn't recheck since I reported this...so I assume the dialog | is still too long but indeed, I'm not completely sure of that. The file has not changed since... Cheers Luk -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCQUcv5UTeB5t8Mo0RAk5sAJ0V7qEpseY+xICXNmhUN4Kx8WQlpgCbBzsf XzHh2MrEvKYooVQWPsJjk58= =+YDr -----END PGP SIGNATURE----- From kloczek@zie.pg.gda.pl Wed Mar 23 10:56:30 2005 From: kloczek@zie.pg.gda.pl (=?ISO-8859-2?Q?Tomasz_K=B3oczko?=) Date: Wed, 23 Mar 2005 11:56:30 +0100 (CET) Subject: [Pkg-shadow-devel] Bug#300268: /usr/share/man/man5/passwd.5.gz contains inaccurate information In-Reply-To: <20050321165341.GB8640@mykerinos.kheops.frmug.org> References: <20050318221823.GC5610@nekral.homelinux.net> <20050319195757.GA11797@cherokee.kiev.ua> <20050320074009.GF32638@mykerinos.kheops.frmug.org> <20050320085436.GC3779@papagos> <1111419375.4776.26.camel@test1.zie.pg.gda.pl> <20050321165341.GB8640@mykerinos.kheops.frmug.org> Message-ID: This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --568760595-192646210-1111575199=:25062 Content-Type: TEXT/PLAIN; CHARSET=ISO-8859-2 Content-Transfer-Encoding: QUOTED-PRINTABLE Content-ID: On Mon, 21 Mar 2005, Christian Perrier wrote: >=20 > > I plan convert all shadow man pages documentation to XML (this is much > > more commont format for documentation) and prepare translation framewor= k > > basing on this source form. Probably will be used gnome-doc-utils (or >=20 > ....which does not prevent using PO format for documentation > translation. The PO format is *designed* for translation handling, > with good handling of "upstream" changes and impact on > translations. All free software translation teams use PO tools for > handling translation work because of the wide availability of tools > and utilities (compendium, dictionaries, automation tools, web > translation projects such as Pootle....) You are wrong. You can use: - XML (refentry) as source format, - gnome-doc-utils for sucking .po file for translators and for track all=20 changes on this level for keep in synced form man pages in all=20 avalaible translations, - use .po files with translations for generate non-english XML files, - use XSLT for generate roff files. This guarangis *one common man pages stilistics*. Also allow use XML format as installabe form in future when like in Solaris man program will= =20 handle man pages also in SGML. I'm not perform yet some experiments but probably for generate .po files from XML rerfentry can be used plain gettext because xgettext can handle XLM files (I don't know now is it can handle refentry). If it will work now po4a will be redundant. If not probaly it will require some additional work on gettext level (which will be very good invesment also=20 for other projects). kloczek --=20 ----------------------------------------------------------- *Ludzie nie maj=B1 problem=F3w, tylko sobie sami je stwarzaj=B1* ----------------------------------------------------------- Tomasz K=B3oczko, sys adm @zie.pg.gda.pl|*e-mail: kloczek@rudy.mif.pg.gda.p= l* --568760595-192646210-1111575199=:25062-- From Christian Perrier , 277750@bugs.debian.org Wed Mar 23 10:48:12 2005 From: Christian Perrier , 277750@bugs.debian.org (Christian Perrier) Date: Wed, 23 Mar 2005 11:48:12 +0100 Subject: [Pkg-shadow-devel] Bug#277750: Shorten down the Dutch translation of the root password question dialog in package shadow In-Reply-To: <4241472F.6020709@ugent.be> References: <20050323084357.GD18053@mykerinos.kheops.frmug.org> <4241472F.6020709@ugent.be> Message-ID: <20050323104812.GH18053@mykerinos.kheops.frmug.org> > | Please find attached the relevant nl.po file. Could you take care of > | shortening it. >=20 > Maybe we can change it from "Beheerderswachtwoord (root):" to > "Wachtwoord voor root:"? Hmm, what needs to be shorten is indeed the long description translation more than the short one.... ie, all this: #. Type: password #. Description #: ../passwd.templates:3 msgid "" "You need to set a password for 'root', the system administrative account= . A " "malicious or unqualified user with root access can have disastrous resul= ts, " "so you should take care to choose a root password that is not easy to gu= ess. " "It should not be a word found in the dictionary, or a word that could be= " "easily associated with you, like your middle name. A good password will = " "contain a mixture of letters, numbers and punctuation and will be change= d at " "regular intervals. The root password is changed by running the 'passwd' = " "program as root." msgstr "" "Er dient nu een wachtwoord gekozen te worden voor de beheerdersaccount " "('root'). Omdat een onwetende of kwaadwillende gebruiker die zich als " "beheerder aanmeldt rampzalige gevolgen kan hebben is het belangrijk dat = het " "beheerderswachtwoord moeilijk te raden is. Dit houdt in dat het geen woo= rd " "uit het woordenboek, of iets dat makkelijk met u te associ=EBren valt " "(banknummer, geboorte datum, tweede of derde voornaam, huisdier, ...) ma= g " "zijn. Een ideaal wachtwoord bevat een mengeling van letters, cijfers, " "leestekens en speciale tekens. Een relatief goede manier om een wachtwoo= rd " "te bedenken is om van een lange zin, of een kort verhaaltje telkens de " "eerste letter (of de tweede, of de laatste, ...) van elk woord te nemen,= " "waarbij je leestekens laat staan, en een willekeurige letter vervangt do= or " "een speciaal teken (vb. $ voor s). U kunt het wachtwoord van root later = " "veranderen door het commando 'passwd' uit te voeren als root." #. Type: password #. Description #: ../passwd.templates:3 msgid "Note that you will not be able to see the password as you type it.= " msgstr "Merk op dat u het wachtwoord niet kunt zien terwijl u het typt." From martin.quinson@loria.fr Wed Mar 23 11:27:39 2005 From: martin.quinson@loria.fr (Martin Quinson) Date: Wed, 23 Mar 2005 12:27:39 +0100 Subject: [Pkg-shadow-devel] Solution to translate shadow documentation In-Reply-To: References: <20050318221823.GC5610@nekral.homelinux.net> <20050319195757.GA11797@cherokee.kiev.ua> <20050320074009.GF32638@mykerinos.kheops.frmug.org> <20050320085436.GC3779@papagos> <1111419375.4776.26.camel@test1.zie.pg.gda.pl> <20050321165341.GB8640@mykerinos.kheops.frmug.org> Message-ID: <20050323112739.GE4689@papagos> --pY3vCvL1qV+PayAL Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Mar 23, 2005 at 11:56:30AM +0100, Tomasz K?oczko wrote: > On Mon, 21 Mar 2005, Christian Perrier wrote: >=20 > >=20 > > > I plan convert all shadow man pages documentation to XML (this is much > > > more commont format for documentation) and prepare translation framew= ork > > > basing on this source form. Probably will be used gnome-doc-utils (or > >=20 > > ....which does not prevent using PO format for documentation > > translation. The PO format is *designed* for translation handling, > > with good handling of "upstream" changes and impact on > > translations. All free software translation teams use PO tools for > > handling translation work because of the wide availability of tools > > and utilities (compendium, dictionaries, automation tools, web > > translation projects such as Pootle....) >=20 > You are wrong. > You can use: > - XML (refentry) as source format, > - gnome-doc-utils for sucking .po file for translators and for track all= =20 > changes on this level for keep in synced form man pages in all=20 > avalaible translations, > - use .po files with translations for generate non-english XML files, > - use XSLT for generate roff files. Sure, that's just what Christian proposed. Why is he wrong? =20 > This guarangis *one common man pages stilistics*. Also allow use XML > format as installabe form in future when like in Solaris man program will= =20 > handle man pages also in SGML. I see this as somehow unrelated, but I may be wrong (see below). > I'm not perform yet some experiments but probably for generate .po files > from XML rerfentry can be used plain gettext because xgettext can handle > XLM files (I don't know now is it can handle refentry). Were did you get this information from? From the info xgettext, the list of supported format are:=20 -L NAME' --language=3DNAME' Specifies the language of the input files. The supported languages are `C', `C++', `ObjectiveC', `PO', `Python', `Lisp', `EmacsLisp', `librep', `Smalltalk', `Java', `JavaProperties', `C#', `awk', `YCP', `Tcl', `Perl', `PHP', `GCC-source', `NXStringTable', `RST', `Glade'. (xgettext (GNU gettext-tools) 0.14.1) > If it will work now po4a will be redundant. If not probaly it will require > some additional work on gettext level (which will be very good invesment > also for other projects). I guess it won't work because if it did, it would indeed make po4a redundant with gettext regular tools and I did check before investing so much time into this project ;) I guess that the authors of poxml did the same, too. As well as the gnome-doc-utils authors, which you plan to use. I must confess that I'm a bit lost here. You say at the same time that po4a is redundant with regular gettext tools and that you plan to use a concurent solution (xml2po, from gnome-doc-utils).=20 I'm perfectly ok with po4a not getting used in shadow, but could you please explain why (so that we get a chance to improve po4a, if needed/possible)? Thanks for your time, Mt. --pY3vCvL1qV+PayAL Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQFCQVKrIiC/MeFF8zQRAgQPAKDVWf0aYayrlvqeYGekkuviSX5F0QCglox5 OLRY1iKGL9SV0tyKcNhoceM= =7gl6 -----END PGP SIGNATURE----- --pY3vCvL1qV+PayAL-- From kloczek@zie.pg.gda.pl Wed Mar 23 12:19:10 2005 From: kloczek@zie.pg.gda.pl (=?ISO-8859-2?Q?Tomasz_K=B3oczko?=) Date: Wed, 23 Mar 2005 13:19:10 +0100 (CET) Subject: [Pkg-shadow-devel] Solution to translate shadow documentation In-Reply-To: <20050323112739.GE4689@papagos> References: <20050318221823.GC5610@nekral.homelinux.net> <20050319195757.GA11797@cherokee.kiev.ua> <20050320074009.GF32638@mykerinos.kheops.frmug.org> <20050320085436.GC3779@papagos> <1111419375.4776.26.camel@test1.zie.pg.gda.pl> <20050321165341.GB8640@mykerinos.kheops.frmug.org> <20050323112739.GE4689@papagos> Message-ID: This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --568760595-261023897-1111580350=:6369 Content-Type: TEXT/PLAIN; charset=ISO-8859-2 Content-Transfer-Encoding: QUOTED-PRINTABLE On Wed, 23 Mar 2005, Martin Quinson wrote: [..] > Sure, that's just what Christian proposed. Why is he wrong? To Christian: sorry .. my mistake (tooday I have very hard day in work=20 :>). > > I'm not perform yet some experiments but probably for generate .po file= s > > from XML rerfentry can be used plain gettext because xgettext can handl= e > > XLM files (I don't know now is it can handle refentry). >=20 > Were did you get this information from? From the info xgettext, the list = of > supported format are:=20 > -L NAME' > --language=3DNAME' > Specifies the language of the input files. The supported languages > are `C', `C++', `ObjectiveC', `PO', `Python', `Lisp', `EmacsLisp', > `librep', `Smalltalk', `Java', `JavaProperties', `C#', `awk', > `YCP', `Tcl', `Perl', `PHP', `GCC-source', `NXStringTable', `RST', > `Glade'. >=20 > (xgettext (GNU gettext-tools) 0.14.1) Glade files this XML files so some startup framework for sucking phrases without additional tools from XML files exist in xgettext. BTW: finish this for allow xgettext for fully operate on XML refentry and/or book will allow simplify for example translate all docbook LDP documentation. Few projects have now man pages in XML primary format=20 (IIRC: gnupg, mc and few other). kloczek --=20 ----------------------------------------------------------- *Ludzie nie maj=B1 problem=F3w, tylko sobie sami je stwarzaj=B1* ----------------------------------------------------------- Tomasz K=B3oczko, sys adm @zie.pg.gda.pl|*e-mail: kloczek@rudy.mif.pg.gda.p= l* --568760595-261023897-1111580350=:6369-- From martin.quinson@loria.fr Wed Mar 23 12:51:26 2005 From: martin.quinson@loria.fr (Martin Quinson) Date: Wed, 23 Mar 2005 13:51:26 +0100 Subject: [Pkg-shadow-devel] Solution to translate shadow documentation In-Reply-To: References: <20050318221823.GC5610@nekral.homelinux.net> <20050319195757.GA11797@cherokee.kiev.ua> <20050320074009.GF32638@mykerinos.kheops.frmug.org> <20050320085436.GC3779@papagos> <1111419375.4776.26.camel@test1.zie.pg.gda.pl> <20050321165341.GB8640@mykerinos.kheops.frmug.org> <20050323112739.GE4689@papagos> Message-ID: <20050323125126.GI4689@papagos> --ZOudaV4lSIjFTlHv Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Mar 23, 2005 at 01:19:10PM +0100, Tomasz K?oczko wrote: > On Wed, 23 Mar 2005, Martin Quinson wrote: > [..] > > Sure, that's just what Christian proposed. Why is he wrong? >=20 > To Christian: sorry .. my mistake (tooday I have very hard day in work=20 > :>). No problem, I guess, he's used to worse on the various debian ML he work on= ;) > > > I'm not perform yet some experiments but probably for generate .po fi= les > > > from XML rerfentry can be used plain gettext because xgettext can han= dle > > > XLM files (I don't know now is it can handle refentry). > >=20 > > Were did you get this information from? From the info xgettext, the lis= t of > > supported format are:=20 > > -L NAME' > > --language=3DNAME' > > Specifies the language of the input files. The supported languages > > are `C', `C++', `ObjectiveC', `PO', `Python', `Lisp', `EmacsLisp', > > `librep', `Smalltalk', `Java', `JavaProperties', `C#', `awk', > > `YCP', `Tcl', `Perl', `PHP', `GCC-source', `NXStringTable', `RST', > > `Glade'. > >=20 > > (xgettext (GNU gettext-tools) 0.14.1) >=20 > Glade files this XML files so some startup framework for sucking > phrases without additional tools from XML files exist in xgettext. >=20 > BTW: finish this for allow xgettext for fully operate on XML refentry > and/or book will allow simplify for example translate all docbook LDP > documentation. Few projects have now man pages in XML primary format=20 > (IIRC: gnupg, mc and few other). The only issue is that the glade support is only in xgettext. That is to say that there is no mecanism to reinject the translations into the xml file afterward. Such a mecanism seems to be in place for java properties (from what I see in source code, don't see how to use it in documentation). If you follow that way (which I agree to feel appealing), we could recode po4a to C in order to integrate it into gettext. It would be great, but we do use a great deal of perl regular expressions for parsing.=20 And moreover, I'm rather happy with the po4a modular design, and it's something which seems difficult to integrate in the existing gettext tool suite as is. Please just check the two following links: http://po4a.alioth.debian.org/en/Locale/Po4a/TransTractor.html http://po4a.alioth.debian.org/en/po4a.7.html That being said, I'm interested in merging po4a into gettext, if you have any viable solution. Thanks for your time, Mt. --ZOudaV4lSIjFTlHv Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQFCQWZOIiC/MeFF8zQRAqHwAJ9uMqIbdo7iFUQ9mndi0f4VZkFK3QCfZzBN sDYgUuAQ8hpQvEo/WkZ5pnI= =DwzK -----END PGP SIGNATURE----- --ZOudaV4lSIjFTlHv-- From "cobaco (aka Bart Cornelis)" , 277750@bugs.debian.org Wed Mar 23 13:01:06 2005 From: "cobaco (aka Bart Cornelis)" , 277750@bugs.debian.org (cobaco (aka Bart Cornelis)) Date: Wed, 23 Mar 2005 14:01:06 +0100 Subject: [Pkg-shadow-devel] Bug#277750: Shorten down the Dutch translation of the root password question dialog in package shadow In-Reply-To: <20050323104812.GH18053@mykerinos.kheops.frmug.org> References: <20050323084357.GD18053@mykerinos.kheops.frmug.org> <4241472F.6020709@ugent.be> <20050323104812.GH18053@mykerinos.kheops.frmug.org> Message-ID: <200503231401.07662.cobaco@linux.be> --nextPart4517339.nfSW9EYJhR Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Wednesday 23 March 2005 11:48, Christian Perrier wrote: > > | Please find attached the relevant nl.po file. Could you take care of > > | shortening it. > > > > Maybe we can change it from "Beheerderswachtwoord (root):" to > > "Wachtwoord voor root:"? > > Hmm, what needs to be shorten is indeed the long description > translation more than the short one.... ok, so how 'long' can the long description be? > #. Type: password > #. Description > #: ../passwd.templates:3 > msgid "" > "You need to set a password for 'root', the system administrative > account. A " "malicious or unqualified user with root access can have > disastrous results, " "so you should take care to choose a root password > that is not easy to guess. " "It should not be a word found in the > dictionary, or a word that could be " "easily associated with you, like > your middle name. A good password will " "contain a mixture of letters, > numbers and punctuation and will be changed at " "regular intervals. The > root password is changed by running the 'passwd' " "program as root." > msgstr "" > "Er dient nu een wachtwoord gekozen te worden voor de beheerdersaccount " > "('root'). Omdat een onwetende of kwaadwillende gebruiker die zich als " > "beheerder aanmeldt rampzalige gevolgen kan hebben is het belangrijk dat > het " "beheerderswachtwoord moeilijk te raden is. Dit houdt in dat het > geen woord " "uit het woordenboek, of iets dat makkelijk met u te > associ=EBren valt " "(banknummer, geboorte datum, tweede of derde voornaa= m, > huisdier, ...) mag " "zijn. Een ideaal wachtwoord bevat een mengeling van > letters, cijfers, " "leestekens en speciale tekens.=20 > Een relatief goede manier om een wachtwoord " "te bedenken is om van een > lange zin, of een kort verhaaltje telkens de " "eerste letter (of de > tweede, of de laatste, ...) van elk woord te nemen, " "waarbij je > leestekens laat staan, en een willekeurige letter vervangt door " "een > speciaal teken (vb. $ voor s).=20 this bit could be dropped if it is to long (loose translation to english: A relatively good way to choose a password is take a long sentence of which= =20 you take the first (or second, or last, or...) character of each word, keep= =20 punctiation and maybe replace all occurences of a random charater by some=20 special character (e.g. $ instead of s).=20 ) =2D-=20 Cheers, cobaco (aka Bart Cornelis) =20 1. Encrypted mail preferred (GPG KeyID: 0x86624ABB) 2. Plain-text mail recommended since I move html and double format mails to a low priority folder (they're mainly spam) --nextPart4517339.nfSW9EYJhR Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQBCQWiT5ihPJ4ZiSrsRAiMvAJ9tfBxxNlkjFFsWpgVPrzk3Cp2jdgCgj5/B 1/TQ+dfHi7R3xSr6ZN9XfLU= =kNLo -----END PGP SIGNATURE----- --nextPart4517339.nfSW9EYJhR-- From Christian Perrier , 277750@bugs.debian.org Wed Mar 23 13:02:06 2005 From: Christian Perrier , 277750@bugs.debian.org (Christian Perrier) Date: Wed, 23 Mar 2005 14:02:06 +0100 Subject: [Pkg-shadow-devel] Bug#277750: Shorten down the Dutch translation of the root password question dialog in package shadow In-Reply-To: <200503231401.07662.cobaco@linux.be> References: <20050323084357.GD18053@mykerinos.kheops.frmug.org> <4241472F.6020709@ugent.be> <20050323104812.GH18053@mykerinos.kheops.frmug.org> <200503231401.07662.cobaco@linux.be> Message-ID: <20050323130206.GC7913@mykerinos.kheops.frmug.org> > ok, so how 'long' can the long description be? Tricky..:-) But you can use the podebconf-display-po utility for this (from the po-debconf package). Of course you have to use it in a 80x25 terminal. From owner@bugs.debian.org Wed Mar 23 19:19:41 2005 From: owner@bugs.debian.org (Debian Bug Tracking System) Date: Wed, 23 Mar 2005 11:19:41 -0800 Subject: [Pkg-shadow-devel] Processed: Bug still =?iso-8859-15?Q?here=A0=3F_group?= =?iso-8859-15?Q?add_exit?= =?iso-8859-15?Q?s?= with signal 13 when invoked by 'adduser --system...' In-Reply-To: <20050323174833.GF13294@mykerinos.kheops.frmug.org> References: <20050323174833.GF13294@mykerinos.kheops.frmug.org> Message-ID: Processing commands for control@bugs.debian.org: > retitle 234307 [TO CLOSE 20050323] groupadd exits with signal 13 when invoked by 'adduser --system...' Bug#234307: groupadd exits with signal 13 when invoked by 'adduser --system...' Changed Bug title. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) From Nicolas =?iso-8859-1?Q?Fran=E7ois?= , 300973-maintonly@bugs.debian.org Wed Mar 23 18:39:23 2005 From: Nicolas =?iso-8859-1?Q?Fran=E7ois?= , 300973-maintonly@bugs.debian.org (Nicolas =?iso-8859-1?Q?Fran=E7ois?=) Date: Wed, 23 Mar 2005 19:39:23 +0100 Subject: [Pkg-shadow-devel] Bug#300973: login: italian man page formatting typo In-Reply-To: <20050323060941.GM20159@mykerinos.kheops.frmug.org> References: <8764zjmfet.fsf@zip.com.au> <20050323060941.GM20159@mykerinos.kheops.frmug.org> Message-ID: <20050323183923.GA4638@nekral.homelinux.net> Hi, This man page may also need a rewrite since it doesn't fit to the English man page (the Korean and Indonesian translations too). For example, I could not find anything about /etc/usertty in the shadow sources. The debian-l10n-{id,it,ko} teams could be asked if they rather like to remove, keep or update the translation (once we will know the way translations will be handled). You can find the original English man page used for these translations at: http://www.die.net/doc/linux/man/man1/login.1.html Regards, -- Nekral From owner@bugs.debian.org Wed Mar 23 19:19:18 2005 From: owner@bugs.debian.org (Debian Bug Tracking System) Date: Wed, 23 Mar 2005 11:19:18 -0800 Subject: [Pkg-shadow-devel] Processed: Dealing with these bug reports will certainly need external input In-Reply-To: <20050323190246.GB6065@mykerinos.kheops.frmug.org> References: <20050323190246.GB6065@mykerinos.kheops.frmug.org> Message-ID: Processing commands for control@bugs.debian.org: > tags 262453 help upstream Bug#262453: login: su, sudo: Local security hole -- arbitrary character injection There were no tags set. Bug#262455: login: su, sudo, super: Local security hole -- arbitrary character injection Tags added: help, upstream > tags 262455 help upstream Bug#262455: login: su, sudo, super: Local security hole -- arbitrary character injection Tags were: upstream help Bug#262453: login: su, sudo: Local security hole -- arbitrary character injection Tags added: help, upstream > retitle 262453 [EXPERT] login: su, sudo: Local security hole -- arbitrary character injection Bug#262453: login: su, sudo: Local security hole -- arbitrary character injection Changed Bug title. > retitle 262455 [EXPERT] login: su, sudo, super: Local security hole -- arbitrary character injection Bug#262455: login: su, sudo, super: Local security hole -- arbitrary character injection Changed Bug title. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) From owner@bugs.debian.org Wed Mar 23 19:22:43 2005 From: owner@bugs.debian.org (Debian Bug Tracking System) Date: Wed, 23 Mar 2005 11:22:43 -0800 Subject: [Pkg-shadow-devel] Bug#271407: marked as done (preseeding fixes (or, passwd.config hardcodes the wrong username for Joey Hess)) In-Reply-To: <20050323173914.GE13294@mykerinos.kheops.frmug.org> References: <20050323173914.GE13294@mykerinos.kheops.frmug.org> <20040913014116.GA3315@kitenet.net> Message-ID: Your message dated Wed, 23 Mar 2005 18:39:14 +0100 with message-id <20050323173914.GE13294@mykerinos.kheops.frmug.org> and subject line Acknowledging NMUs has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -------------------------------------- Received: (at submit) by bugs.debian.org; 13 Sep 2004 01:40:37 +0000 >From joey@kitenet.net Sun Sep 12 18:40:37 2004 Return-path: Received: from kitenet.net [64.62.161.42] (postfix) by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1C6fpd-0002dM-00; Sun, 12 Sep 2004 18:40:37 -0700 Received: from dragon.kitenet.net (unknown [66.168.94.144]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "Joey Hess", Issuer "Joey Hess" (verified OK)) by kitenet.net (Postfix) with ESMTP id E6B1917EC5 for ; Mon, 13 Sep 2004 01:40:36 +0000 (GMT) Received: by dragon.kitenet.net (Postfix, from userid 1000) id 336626E137; Sun, 12 Sep 2004 21:41:16 -0400 (EDT) Date: Sun, 12 Sep 2004 21:41:16 -0400 From: Joey Hess To: Debian Bug Tracking System Subject: preseeding fixes (or, passwd.config hardcodes the wrong username for Joey Hess) Message-ID: <20040913014116.GA3315@kitenet.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="2B/JsCI69OhZNC5r" Content-Disposition: inline X-Reportbug-Version: 2.64 User-Agent: Mutt/1.5.6+20040818i Delivered-To: submit@bugs.debian.org X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-3.0 required=4.0 tests=BAYES_00 autolearn=no version=2.60-bugs.debian.org_2004_03_25 X-Spam-Level: --2B/JsCI69OhZNC5r Content-Type: multipart/mixed; boundary="AhhlLboLdkugWU4S" Content-Disposition: inline --AhhlLboLdkugWU4S Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Package: passwd Version: 1:4.0.3-30 Severity: normal Tags: patch I've been working on allowing debian installs to be automated by debconf database preseeding. The problem I ran into with passwd is that even if I preseeded passwd/username to "joey", it would look at my passwd/user-fullname of "Joey Hess" and reset the default value to "joeyh". (Nice hardcoding of my username, but you choose the wrong one, BTW. ;-) The attached patch fixes that as well as some issues that made it impossible to preseed a root password. Preseeding a root password is of dubious security, but it's _very_ useful when you're using preseeding to do automated regression testing of full Debian installs. I think this use of it outweighs the possibility of someone doing something stupid security-wise, and I don't belive it opens any potential exploits. I'd appreciate seeing these fixes in sarge, but that's up to you. --=20 see shy jo --AhhlLboLdkugWU4S Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=patch --- old/shadow-4.0.3/debian/passwd.config 2004-09-12 21:29:23.000000000 -0400 +++ shadow-4.0.3/debian/passwd.config 2004-09-12 21:13:04.000000000 -0400 @@ -146,11 +146,6 @@ 3) # Prompt for a root password if there is none. if ! root_password; then - db_set passwd/root-password "" - db_fset passwd/root-password seen false - db_set passwd/root-password-again "" - db_fset passwd/root-password-again seen false - db_input critical passwd/root-password || true # Note that this runs at a slightly lower # priority, so it may not always be seen. If @@ -213,22 +208,22 @@ db_get passwd/make-user if [ "$RET" = true ] && ! is_system_user; then LOOP="" - db_get passwd/user-fullname - # Login defaults to user's first name - # Some hat off to a few d-i people - case "$RET" in - "Martin Michlmayr") - userdefault="tbm" - ;; - "Joey Hess") - userdefault="joeyh" - ;; - *) - userdefault="$(echo $RET | sed 's/ .*//' | tr A-Z a-z)" - ;; - esac - if test -n "$userdefault"; then - db_set passwd/username "$userdefault" + db_get passwd/username + if [ -z "$RET" ]; then + db_get passwd/user-fullname + # Login defaults to user's first name + # Some hat off to a few d-i people + case "$RET" in + "Martin Michlmayr") + userdefault="tbm" + ;; + *) + userdefault="$(echo $RET | sed 's/ .*//' | tr A-Z a-z)" + ;; + esac + if test -n "$userdefault"; then + db_set passwd/username "$userdefault" + fi fi db_input critical passwd/username || true db_input critical passwd/user-password || true --AhhlLboLdkugWU4S-- --2B/JsCI69OhZNC5r Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQFBRPq7d8HHehbQuO8RAtRlAKDSIKJ4dog2joO3TVADpT6ByPJhPwCgkzXx g/6hVRfeczWIRhTBDloZgiQ= =G/zc -----END PGP SIGNATURE----- --2B/JsCI69OhZNC5r-- --------------------------------------- Received: (at 271407-done) by bugs.debian.org; 23 Mar 2005 19:12:39 +0000 >From bubulle@kheops.frmug.org Wed Mar 23 11:12:39 2005 Return-path: Received: from perrier.eu.org (kheops.perrier.eu.org) [81.56.227.253] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1DEAtZ-0004Xm-00; Wed, 23 Mar 2005 10:47:57 -0800 Received: from localhost (localhost [127.0.0.1]) by kheops.perrier.eu.org (Postfix) with ESMTP id 7D1F14F8AB; Wed, 23 Mar 2005 19:47:25 +0100 (CET) Received: from kheops.perrier.eu.org ([127.0.0.1]) by localhost (kheops [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 28665-08; Wed, 23 Mar 2005 19:47:23 +0100 (CET) Received: from mykerinos.kheops.frmug.org (mykerinos.kheops.frmug.org [192.168.1.3]) by kheops.perrier.eu.org (Postfix) with ESMTP id 054824F8AA; Wed, 23 Mar 2005 19:47:22 +0100 (CET) Received: by mykerinos.kheops.frmug.org (Postfix, from userid 7426) id CE3EB232A0; Wed, 23 Mar 2005 18:39:14 +0100 (CET) Date: Wed, 23 Mar 2005 18:39:14 +0100 From: Christian Perrier To: 284239-done@bugs.debian.org, 283961-done@bugs.debian.org, 269907-done@bugs.debian.org, 271407-done@bugs.debian.org, 277563-done@bugs.debian.org, 141322-done@bugs.debian.org, 270168-done@bugs.debian.org, 242055-done@bugs.debian.org, 242586-done@bugs.debian.org, 242813-done@bugs.debian.org, 257700-done@bugs.debian.org, 260645-done@bugs.debian.org, 261022-done@bugs.debian.org, 261553-done@bugs.debian.org, 262928-done@bugs.debian.org, 263957-done@bugs.debian.org, 264956-done@bugs.debian.org, 268051-done@bugs.debian.org, 268151-done@bugs.debian.org, 268412-done@bugs.debian.org, 268646-done@bugs.debian.org, 269967-done@bugs.debian.org, 270083-done@bugs.debian.org, 273585-done@bugs.debian.org, 275781-done@bugs.debian.org, 277741-done@bugs.debian.org, 277751-done@bugs.debian.org, 278051-done@bugs.debian.org, 282160-done@bugs.debian.org, 282443-done@bugs.debian.org, 282580-done@bugs.debian.org, 284338-done@bugs.debian.org, 286522-done@bugs.debian.org, 288879-done@bugs.debian.org, 289837-done@bugs.debian.org, 291703-done@bugs.debian.org, 292353-done@bugs.debian.org, 293911-done@bugs.debian.org, 294330-done@bugs.debian.org, 295543-done@bugs.debian.org Subject: Acknowledging NMUs Message-ID: <20050323173914.GE13294@mykerinos.kheops.frmug.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-message-flag: Outlook is a good virus spreading tool. It can send mail, too. X-pot_a_miel: honeypot@kheops.frmug.org User-Agent: Mutt/1.5.6+20040907i X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at kheops.frmug.org Delivered-To: 271407-done@bugs.debian.org X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-3.0 required=4.0 tests=BAYES_00 autolearn=no version=2.60-bugs.debian.org_2005_01_02 X-Spam-Level: X-CrossAssassin-Score: 25 Given that the shadow package maintenance team has now taken over this package, we can know acknowledge all non-maintainer uploads which were made during the interim period. So, hoping I made no typo, I hereby close all these bugs definitely. Thanks a lot to all bug reporters. -- From owner@bugs.debian.org Wed Mar 23 19:22:21 2005 From: owner@bugs.debian.org (Debian Bug Tracking System) Date: Wed, 23 Mar 2005 11:22:21 -0800 Subject: [Pkg-shadow-devel] Bug#270083: marked as done (shadow: [INTL:da] Updated Danish debconf-po translation) In-Reply-To: <20050323173914.GE13294@mykerinos.kheops.frmug.org> References: <20050323173914.GE13294@mykerinos.kheops.frmug.org> Message-ID: Your message dated Wed, 23 Mar 2005 18:39:14 +0100 with message-id <20050323173914.GE13294@mykerinos.kheops.frmug.org> and subject line Acknowledging NMUs has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -------------------------------------- Received: (at submit) by bugs.debian.org; 5 Sep 2004 11:03:21 +0000 >From claus@image.dk Sun Sep 05 04:03:21 2004 Return-path: Received: from fitch5.uni2.net [130.227.52.108] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1C3uno-0007GE-00; Sun, 05 Sep 2004 04:03:20 -0700 Received: from reber (129.142.124.192.ip.tele2adsl.dk [129.142.124.192]) by fitch5.uni2.net (8.12.6/8.11.6) with ESMTP id i85B3FWI017796; Sun, 5 Sep 2004 13:03:15 +0200 Received: from claus by reber with local (Exim 4.34) id 1C3unm-0000tv-2Y; Sun, 05 Sep 2004 13:03:18 +0200 Content-Type: multipart/mixed; boundary="===============1979198818==" MIME-Version: 1.0 From: Claus Hindsgaul To: Debian Bug Tracking System Subject: shadow: [INTL:da] Updated Danish debconf-po translation X-Mailer: reportbug 2.64 Date: Sun, 05 Sep 2004 13:03:17 +0200 Message-Id: Sender: Claus Hindsgaul Delivered-To: submit@bugs.debian.org X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-4.0 required=4.0 tests=DATING,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2004_03_25 X-Spam-Level: This is a multi-part MIME message sent by reportbug. --===============1979198818== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Disposition: inline Content-Transfer-Encoding: 7bit Package: shadow Severity: wishlist Tags: patch l10n Please use the attached updated Danish debc