tomas mohr <[EMAIL PROTECTED]> writes:
> hi,
> i still have the problem, but now it says sth different. instead of
> version incompatible it says mismatch.. suggestions?
> i used this line:
>
> '''$ LDFLAGS="-L/usr/local/lib -L/usr/local/BerkeleyDB.4.2/lib
> -L/usr/local/ssl/lib -R/usr/local/lib -
Howard Chu wrote:
A quick Google didn't turn up any statements to this effect for me.
Wherever you read that, ignore it. The password-hash should be {K5KEY}
if you want the Kerberos key to be used.
Should the config file say "password-hash {K5KEY}" then?
I've tried that, and it hasn't worked
Kris Maglione wrote
If I changed the order in krb5.conf to: v5 v4 afs3
would it put them in that order in LDAP?
I'll answer my own question: yes, and it solves the problem.
Would you mind putting that in the README?
Kris Maglione wrote:
I posted this along with another (solved) problem a few weeks back.
I have smbk5pwd with Samba 3 and heimdal 0.6.2 and openldap 2.2.26.
smbk5pwd.c is revision 1.6
When I set up an account with Samba and Heimdal credentials and perfrom
a password change exop, both the Samba
Kris Maglione wrote:
I'm sorry I didn't explain that better. I set the value back to
{K5KEY} after the exop changed it. I've read in several places that
"password-hash" had to be set to {CLEARTEXT} for this module to work,
but that stored the cleartext password.
A quick Google didn't turn
Kris Maglione wrote:
That seems obvious. The problem is, as I said, I can kinit to the
principal with the password set with the exop. That pretty much rules
out the kdc using another source. I store the keys in K4, K5, and
AFS formats, if that makes a difference
Yes, that makes the differen
hi,
i still have the problem, but now it says sth different. instead of
version incompatible it says mismatch.. suggestions?
i used this line:
'''$ LDFLAGS="-L/usr/local/lib -L/usr/local/BerkeleyDB.4.2/lib
-L/usr/local/ssl/lib -R/usr/local/lib -R/usr/local/BerkeleyDB.4.2/lib
-R/usr/local/ssl/lib"
Howard Chu wrote:
Peter Marschall wrote:
Hi,
On Saturday 02 July 2005 01:41, Alvaro Poole wrote:
Hi, I´m having problems configuring Openldap with TLS/SSL. First of
all, I´m trying to put a server certificate, so I create a certificate
with OpenSSL with the next line:
openssl req -newkey
Well, I thought everything was going ok with my replica servers, but I
have one problem. The only way that replication seems to work is if I
do a One Shot mode /usr/sbin/slurpd -d -1 -r "/var/lib/ldap/replog" -o
If I add a user and then do that, it works fine, but if I do a 'service
ldap start'
At 09:01 AM 7/2/2005, Hallvard B Furuseth wrote:
>Kurt D. Zeilenga writes:
>>At 01:57 PM 7/1/2005, Hallvard B Furuseth wrote:
>>> authz-regexp (OpenLDAP 2.3) seems to only work for SASL.
>>> I note it was called sasl-regexp before.
>>
>> Yes, because it was originally just for mapping SASL authoriz
Kurt D. Zeilenga writes:
>At 01:57 PM 7/1/2005, Hallvard B Furuseth wrote:
>> authz-regexp (OpenLDAP 2.3) seems to only work for SASL.
>> I note it was called sasl-regexp before.
>
> Yes, because it was originally just for mapping SASL authorization
> identities. Now it can map some additional aut
Peter Marschall wrote:
Hi,
On Saturday 02 July 2005 01:41, Alvaro Poole wrote:
Hi, I´m having problems configuring Openldap with TLS/SSL. First of
all, I´m trying to put a server certificate, so I create a certificate
with OpenSSL with the next line:
openssl req -newkey rsa:1024 -x509 -node
Howard Chu wrote:
> These two paragraphs don't make sense. The userPassword will get
> whatever hash is specified by the "password-hash" directive in
> slapd.conf. The only way the k5key_chk function can get called is if
> the hash is actually {K5KEY}. So if you're seeing a different value in
> th
Peter Marschall wrote:
Hi,
On Saturday 02 July 2005 01:41, Alvaro Poole wrote:
Hi, I´m having problems configuring Openldap with TLS/SSL. First of
all, I´m trying to put a server certificate, so I create a certificate
with OpenSSL with the next line:
openssl req -newkey rsa:1024 -x509 -nod
Hi,
On Saturday 02 July 2005 01:41, Alvaro Poole wrote:
> Hi, I´m having problems configuring Openldap with TLS/SSL. First of
> all, I´m trying to put a server certificate, so I create a certificate
> with OpenSSL with the next line:
>
> openssl req -newkey rsa:1024 -x509 -nodes -out ldapcert.pem
Kris Maglione wrote:
I posted this along with another (solved) problem a few weeks back.
I have smbk5pwd with Samba 3 and heimdal 0.6.2 and openldap 2.2.26.
smbk5pwd.c is revision 1.6
I just now tested it against 2.2.24 and 2.2.27, no problems with either.
Using Heimdal 0.6.3 at the moment
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Sameer N
Ingole
Sent: Friday, July 01, 2005 12:57 AM
To: openldap-software@OpenLDAP.org
Subject: Re: trouble in installing openldap: configure: error: Could not
locate TLS/SSL package
Yoginee Bhagwat wrote:
17 matches
Mail list logo
