-up script works. You may have
to also do "nscd -i passwd" to invalidate the name-service cache of the old
entry.
-- A.
--
Andrew Reid / andrew.ce.r...@gmail.com
Hi all --
I have just been bitten by this HDF5 default API bug in
Debian "squeeze". Juha Jäykkä's work-around solves my immediate
problem (thank you!!), but I will be upgrading numerous scientific
development systems to Debian "squeeze" in the coming months.
I appreciate that the API is
Hi all --
Just wanted to add my voice to this report.
A number of users in my lab here have run into this, the
initial symptom was that locally-commpiled versions of the
molecular-dynamics code LAMMPS were failing with SEGV when the
model systems got beyond a certain size. I conjecture
> From: Richard A Nelson <[EMAIL PROTECTED]>
> Subject: Re: Bug#465456: libnss-ldap rejects unexpired certificate as
> expired
> Date: Thu, 3 Jul 2008 05:05:03 + (UTC)
> To: [EMAIL PROTECTED]
>
>
> I've been leaving this open to hopefully help others, but it has been a
> while and I'd like t
On Tue, Feb 12, 2008 at 02:55:32PM -0800, Richard A Nelson wrote:
> On Tue, 12 Feb 2008, Andrew Reid wrote:
>
> >>Since the message deals with the peer certificate, you need
> >>to verify not the local cacert certificate - but the LDAP server
> >>certificate
On Tue, Feb 12, 2008 at 02:10:14PM -0800, Richard A Nelson wrote:
> On Tue, 12 Feb 2008, Andrew Reid wrote:
>
> >Package: libnss-ldap
> >Version: 258-1b+1
>
> This certainly appears to be an OpenSSL issue, not libnss-ldap
>
> > Running "id " with
Package: libnss-ldap
Version: 258-1b+1
I have a group of hosts which use libnss-ldap for passwd and
shadow information, and have recently added a lenny client to
the group, which otherwise consists of etch machines.
All clients use ldaps/TLS to communicate with the slapd on the
server. The
On Fri, Jul 06, 2007 at 07:53:46PM -0400, Ken Raeburn wrote:
> This code path requires that the principal in question have a policy
> dictating a minimum time before the password can be changed, and a
> password change made before that time has elapsed. (I should've
> thought of that given t
On Fri, Jul 06, 2007 at 07:53:46PM -0400, Ken Raeburn wrote:
> This code path requires that the principal in question have a policy
> dictating a minimum time before the password can be changed, and a
> password change made before that time has elapsed. (I should've
> thought of that given t
On Thu, Jul 05, 2007 at 03:55:03PM -0700, Russ Allbery wrote:
> Andrew Reid <[EMAIL PROTECTED]> writes:
>
> > I've had a chance to experiment a little more, and it's
> > clear that what is crashing the kadmind is a second or
> > subsequent kpasswd attemp
I've had a chance to experiment a little more, and it's
clear that what is crashing the kadmind is a second or
subsequent kpasswd attempt for a given principal a short
time after a (successful) first change.
It's as though there's some time window after a kpasswd
invocation on a principal dur
Package: krb5-admin-server
Version: 1.4.4-7etch1
Hi all --
I have a distributed system with a few servers and several
clients, using Kerboros for user authentication and LDAP for
accounts. All servers are Debian "etch", and the clients are
a mix of "etch" and "sarge".
The problem descr
-- A.
--
Andrew Reid / [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
I realize this is sort of late-breaking, but I've just run into
this bug (and implemented Thomas Hood's suggested work-around).
I want to point out that, while Hood's workaround is nicer, it
induces a dependency on the "fping" package, which is packaged
separately from "ping", and at least i
14 matches
Mail list logo
