Re: using {CRYPT} for rootpw, using SHA512?

[Brian Reichert <reichert@numachi.com>]

On Thu, Aug 14, 2014 at 01:48:20PM -0700, Quanah Gibson-Mount wrote:
> --On Thursday, August 14, 2014 2:45 PM -0700 Quanah Gibson-Mount 
> <quanah@zimbra.com> wrote:
> >
> >SHA512 works fine for me with 2.4.39.

I concede, it should be straightforward.

> More specifically, I build openldap myself,

That was my first speedbump, oddly enough.

This is a CentOS 6.5 box.  I removed CentOS's openldap-servers and
openldap-clients RPMs.  The core openldap RPM is still in place,
as CentOS has somee dependancies.

I installed openldap-ltb-2.4.39-2.el6.x86_64.rpm and
berkeleydb-ltb-4.6.21.NC-4.el6.patch4.x86_64.rpm from the LTB repo.
Successfully spun up slapd, using the shiny new mdb backend I
referred to in another thread.

Then:

  # lwp-download ftp://ftp.openldap.org/pub/OpenLDAP/openldap-release/openldap-2.4.39.tgz
  # tar -zxf openldap-2.4.39.tgz
  # cd openldap-2.4.39
  # ./configure
  ...
  checking db.h usability... no
  checking db.h presence... no
  checking for db.h... no
  configure: error: BDB/HDB: BerkeleyDB not available
  # rpm -q db4 berkeleydb-ltb
  db4-4.7.25-18.el6_4.x86_64
  berkeleydb-ltb-4.6.21.NC-4.el6.patch4.x86_64

I suppose I can start playing the 'configure' whack-a-mole game that
I've been playing for decades, to try to work past the mismatch in
expectations.  But, I'm really busy right now. :)

> and I do:

I'll happily give this a go, once I'm past other issues.  Then, if
successful, figure out to package it up as an RPM, as in my
environment, it's part of our deployment process...

> --Quanah
> 
> --
> 
> Quanah Gibson-Mount
> Server Architect
> Zimbra, Inc.
> --------------------
> Zimbra ::  the leader in open source messaging and collaboration

-- 
Brian Reichert				<reichert@numachi.com>
BSD admin/developer at large