Re: Does /etc/shadow exist in an sbuild environment?
On Thu, Apr 27, 2006 at 07:09:17AM +0200, Christian Perrier wrote: Turning shadow on in chroots is left up to the local admin. This is optionnally done by the passwd package when it is reconfigured, see /var/lib/dpkg/info/passwd.config Of course, using shadowconfig on is also possible without reconfiguring the passwd package..:) Apart from that, yes, enabling shadow passwords is the default on newly installed Debian. The relevant question is hidden in default high priority installs and has a positive answer as default. It is shown when the install is run at medium priority. I don't have passwd installed in my chroots, don't have a /etc/shadow, and installing passwd doesn't get create it either. It also seems to require that you have debconf installed, which I don't. Even with debconf installed it doesn't turn it on by default. Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Does /etc/shadow exist in an sbuild environment?
Hi all, Does anyone know whether the default sbuild environment includes the file /etc/shadow? I am sponsoring a package (root, cf. #325306) whose configure script tests the existence of /etc/shadow to decide whether or not to support shadow passwords. This is a compile-time setting, so I'd like to support the largest number of environments by having shadow support turned on, which I believe is the default in Debian. I discovered to my dismay that a default pbuilder environment does not include that file, so I am wondering what will happen on the buildds. In the meantime I'll see whether my sponsoree can force the packages to include shadow password support even if /etc/shadow doesn't exist. Thanks in advance! -- Kevin B. McCarty [EMAIL PROTECTED] Physics Department WWW: http://www.princeton.edu/~kmccarty/Princeton University GPG: public key ID 4F83C751 Princeton, NJ 08544 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Does /etc/shadow exist in an sbuild environment?
On Wed, Apr 26, 2006 at 06:07:37PM -0400, Kevin B. McCarty wrote: Hi all, Does anyone know whether the default sbuild environment includes the file /etc/shadow? It might, if the admin set it up inside the chroot. It's not guaranteed, though, as sbuild functions without it, too (though it might output an annoying (though harmless) warning message with every build, which shows up in mail) I am sponsoring a package (root, cf. #325306) whose configure script tests the existence of /etc/shadow to decide whether or not to support shadow passwords. That's horribly broken. Please fix the upstream build system before uploading the package (or have your sponsee fix it). -- Fun will now commence -- Seven Of Nine, Ashes to Ashes, stardate 53679.4 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Does /etc/shadow exist in an sbuild environment?
Quoting Kevin B. McCarty ([EMAIL PROTECTED]): Hi all, Does anyone know whether the default sbuild environment includes the file /etc/shadow? I am sponsoring a package (root, cf. #325306) whose configure script tests the existence of /etc/shadow to decide whether or not to support shadow passwords. This is a compile-time setting, so I'd like to support the largest number of environments by having shadow support turned on, which I believe is the default in Debian. Turning shadow on in chroots is left up to the local admin. This is optionnally done by the passwd package when it is reconfigured, see /var/lib/dpkg/info/passwd.config Of course, using shadowconfig on is also possible without reconfiguring the passwd package..:) Apart from that, yes, enabling shadow passwords is the default on newly installed Debian. The relevant question is hidden in default high priority installs and has a positive answer as default. It is shown when the install is run at medium priority. So, in short, using shadow passowrd is the default on current Debian systems but *not* using them is also possible if the local admin did choose this option when isntalling...or if the system has been upgraded from version to version after being installed in the old days where shadow passwords were not the default option (they're the default since woody, at least, and maybe even before). signature.asc Description: Digital signature
