> "Joey" == Joey Hess <[EMAIL PROTECTED]> writes:
Joey> Steve Langasek wrote:
>> - It will now be possible to choose md5 vs. crypt passwords at
>> install time without violating policy. (Currently, a number of
>> conffiles are being modified by maintainer scripts in order to
Steve Langasek <[EMAIL PROTECTED]> writes:
> - Essential packages which currently pre-depend on libpam0g (read:
> login) will also need a versioned Pre-Depends on libpam-runtime
> before adopting this scheme, so that they are usable in an
> unconfigured state. Please consider this an introdu
Steve Langasek wrote:
> Would you recommend this "best effort" approach for the present case?
> Will that be effective for d-i, or do we have to worry about
> libpam-runtime's postinst completing before debconf is available?
Basically the approach is to check to see if
/usr/share/debconf/confmodul
On Thu, Aug 21, 2003 at 08:11:21PM -0400, Joey Hess wrote:
> Steve Langasek wrote:
> > Given that all the files involved were conffiles prior to this
> > transition, I think no additional work is needed to correctly support
> > systems that are being upgraded. Can you confirm whether
> > /etc/pam.
Steve Langasek wrote:
> Given that all the files involved were conffiles prior to this
> transition, I think no additional work is needed to correctly support
> systems that are being upgraded. Can you confirm whether
> /etc/pam.d/other already contains 'md5' on the machine above? If not,
> I'll
Hi Marcelo,
On Thu, Aug 21, 2003 at 10:44:04AM +0200, Marcelo E. Magallon wrote:
> On Wed, Aug 20, 2003 at 10:37:59PM -0500, Steve Langasek wrote:
> > - Per-package /etc/pam.d/ configuration files should not include
> > explicit 'password' blocks. Instead, services should use the builtin
>
On Thu, Aug 21, 2003 at 12:40:35PM -0400, Joey Hess wrote:
> Steve Langasek wrote:
> > - It will now be possible to choose md5 vs. crypt passwords at install
> > time without violating policy. (Currently, a number of conffiles are
> > being modified by maintainer scripts in order to enable md5
Steve Langasek wrote:
> - It will now be possible to choose md5 vs. crypt passwords at install
> time without violating policy. (Currently, a number of conffiles are
> being modified by maintainer scripts in order to enable md5
> passwords.) Actually making this process policy-compliant wil
Hi Steve,
thanks for the work. A couple of questions for clarity's sake (as
sysadmin, not packager)
On Wed, Aug 20, 2003 at 10:37:59PM -0500, Steve Langasek wrote:
> - Per-package /etc/pam.d/ configuration files should not include
> explicit 'password' blocks. Instead, services should us
9 matches
Mail list logo
