--On Thursday, March 31, 2022 3:13 PM -0400 Braiam <braiamp(a)gmail.com>
wrote:
>
>
>
>
>
>
> On Thu, Mar 31, 2022 at 11:46 AM Quanah Gibson-Mount
> <quanah(a)fast-mail.org> wrote:
>
>
>
> --On Thursday, March 31, 2022 12:16 PM -0400 Braiam <braiamp(a)gmail.com>
> wrote:
>
>> What would be the process to modify content on the openldap.org page?
>
> Depends on the content. The main web pages are in the OpenLDAP Web git
> repository.
>
>
> This repository seems to be the FAQ:
>
>
> https://git.openldap.org/project/faq/-/tree/master/data/item
>
>
> There's a website project too. I couldn't figure out what markup language
> items
> on the faq project uses.
It uses whatever format the FAQ-O-Matic software uses
(<https://sourceforge.net/projects/faqomatic/>)
--Quanah
Hi Michael,
Indeed, it's fine now :)
But is there any way that I make the password stuff working as well.
Thanks again....
-Asimananda
2009/7/20 Michael Ströder <michael(a)stroeder.com>
> Asimananda Mohanty wrote:
> >
> > The first command works fine (ldapsearch -x -H ldap://ldap-company.com
> > <http://ldap-company.com/> -ZZ) but the second one (ldapsearch -x -H
> > ldaps://ldap-company.com:636 <http://ldap-company.com:636/> -ZZ) is
> > showing error :
> >
> > *ldap_start_tls: Operations error (1)*
>
> Sorry, stupid copy&paste by me. Should have another coffee. Omit the -ZZ
> in the second command since LDAPS and StartTLS ext.op. cannot be used
> together.
>
> See also:
> http://www.openldap.org/faq/data/cache/605.html
>
> Ciao, Michael.
>
> --
> Michael Ströder
> E-Mail: michael(a)stroeder.com
> http://www.stroeder.com
>
Hi,
On Monday, 28. May 2012, Philip Guenther wrote:
> On Mon, 28 May 2012, Michael Ströder wrote:
> > Peter Marschall wrote:
> > > how do the openldap tools technically verfify certificates with
> > > ldapi:// ?
> >
> > Which certs do you want to verify?
>
> I assume the answer is "the one the server returns when you do StartTLS on
> the ldapi:// connection".
Correct.
> If that's not a sufficient option, and verifying certs is required, then
> it appears the code will treat the socket path as the hostname to verify
> for. For OpenSSL, for example, that means it'll compare it against any
> DNS: subjectAltNames as well as against the last CN component of the cert
> subject.
That's not what the openldap tools do.
My cerver certificates do not contain the ldapi socket path as hostnames,
yet
ldapsearch -LLL -x -H ldapi:/// -ZZ -s base -b ""
works and I want to find out how it does this.
Best
PEter
--
Peter Marschall
peter(a)adpm.de
sim123 wrote:
> So I did more research and found that java or spring source has APIs for
> encrypting passwords and I could store the hashed value in openldap. If thats
> the case would LDPA server be able to retrive the password during bind?
>
> And another interesting read is
>
> http://blogs.oracle.com/DirectoryManager/entry/the_ssha_password_storage_sc…
>
> Is that true for OpenLDAP? Can I use similar algorithm for generating
> password? Or should password policy will suffice ?
Should be the same. Compare to:
http://www.openldap.org/faq/data/cache/347.html
Generating the salted hash of the password can be done by the client or within
slapd when the client sends a LDAP Password Modify extended operation request
(RFC 3062) with the clear-text password (as stated in
http://www.openldap.org/faq/data/cache/906.html).
Note that there are various forms of bind requests. Hashed passwords in
attribute 'userPassword' can only be used with bind methods which sends the
plaintext password over the wire (simple bind, SASL/PLAIN) and therefore the
communication has to be protected (by LDAPS or LDAP with StartTLS).
Ciao, Michael.
c0re <nr1c0re(a)gmail.com> writes:
> # making clientkey
> openssl genrsa -out client.key 2048
> # making certificate request
> openssl req -new -key client.key -out client.csr
> # signing
> openssl x509 -req -days 1024 -CA ../ssl/rootcrt.pem -CAkey
> ../ssl/rootkey.pem -in client.csr -out client.crt -CAserial
> ../ssl/root.seq
>
> # configuring on client
> TLS_CACERT /usr/local/etc/openldap/ssl-client/rootcrt.pem
> TLS_CERT /usr/local/etc/openldap/ssl-client/client.crt
> and
> TLS_KEY /usr/local/etc/openldap/ssl-client/client.key
>
> Trying again with slapd debug and client calling "id test"
[...]
As there are no obvious errors in the log you should get TLS properly
working, prior to testing with pam. Just do a ldapsearch or a
ldapwhoami either on uri ldaps:// or startTLS on ldap://
-Dieter
--
Dieter Klünter | Systemberatung
sip: 7770535(a)sipgate.de
http://www.dpunkt.de/buecher/2104.html
GPG Key ID:8EF7B6C6
Hi,
I can't find anywhere on how to fix my RHEL 5 to use TLS/SSL authentication. I will work when I comment out the ssl startTLS and SSL. On my Solaris 10, I can do ldapsearch with the -ZZ option
Here is what I did with the debug on for ldapsearch. Please help me solve this problem...THANKS!!
TLS trace: SSL_connect:SSLv3 read server certificate A
TLS trace: SSL_connect:SSLv3 read server certificate request A
TLS trace: SSL_connect:SSLv3 read server done A
TLS trace: SSL_connect:SSLv3 write client certificate A
TLS trace: SSL_connect:SSLv3 write client key exchange A
TLS trace: SSL_connect:SSLv3 write change cipher spec A
TLS trace: SSL_connect:SSLv3 write finished A
TLS trace: SSL_connect:SSLv3 flush data
TLS trace: SSL3 alert read:fatal:handshake failure
TLS trace: SSL_connect:failed in SSLv3 read finished A
TLS: can't connect.
ldap_perror
ldap_start_tls: Connect error (-11)
additional info: error:14094410:SSL routines:SSL3_READ_BYTES:sslv3 alert handshake failure
Hi,
I can't find anywhere on how to fix my RHEL 5 to use TLS/SSL authentication. I will work when I comment out the ssl startTLS and SSL. On my Solaris 10, I can do ldapsearch with the -ZZ option
Here is what I did with the debug on for ldapsearch. Please help me solve this problem...THANKS!!
TLS trace: SSL_connect:SSLv3 read server certificate A
TLS trace: SSL_connect:SSLv3 read server certificate request A
TLS trace: SSL_connect:SSLv3 read server done A
TLS trace: SSL_connect:SSLv3 write client certificate A
TLS trace: SSL_connect:SSLv3 write client key exchange A
TLS trace: SSL_connect:SSLv3 write change cipher spec A
TLS trace: SSL_connect:SSLv3 write finished A
TLS trace: SSL_connect:SSLv3 flush data
TLS trace: SSL3 alert read:fatal:handshake failure
TLS trace: SSL_connect:failed in SSLv3 read finished A
TLS: can't connect.
ldap_perror
ldap_start_tls: Connect error (-11)
additional info: error:14094410:SSL routines:SSL3_READ_BYTES:sslv3 alert handshake failure
--On Tuesday, October 21, 2008 4:05 PM -0400 Kyle Barger <kbarger(a)ltsp.edu>
wrote:
> I have an OpenLDAP 2.3 server that is up and running. I have been trying
> to add SSL and TLS. SSL connections on port 636 work fine. However the
> TLS connection on 389 is not working. The only errors are "TLS accept
> failure" and "TLS negotiation failure." I've not been able to dig up any
> more information, even using the -d option, and I notice that people have
> posted log files with detailed TLS trace messages. How can I enable the
> TLS logging to find out what's going on? Thanks.
You can't do SSL over port 389, you need to do startTLS instead. You don't
say how you are testing these connections, but if you are using ldapsearch,
look at the "-Z[ZZ]" option(s).
--Quanah
--
Quanah Gibson-Mount
Principal Software Engineer
Zimbra, Inc
--------------------
Zimbra :: the leader in open source messaging and collaboration
Hi!
I am using the cn=admin,o=infra,c=com with correct password to connect. I
will further check ACLs! Thank you for that suggestion.
Just to make things more concrete, below are two samples. One on the MASTER
with contextCSN, and one from the SLAVE without contextCSN.
EXAMPLE SLAVE:
ldapsearch -x -H ldaps://$SERVER -D $LDAPBINDDN -w $ADMINPW -b
"o=infra,c=com" -s base contextCSN
# extended LDIF
#
# LDAPv3
# base <o=infra,c=com> with scope baseObject
# filter: (objectclass=*)
# requesting: contextCSN
#
# search result
search: 2
result: 0 Success
# numResponses: 1
EXAMPLE MASTER:
ldapsearch -x -H ldaps://$SERVER -D $LDAPBINDDN -w $ADMINPW -b
"o=infra,c=com" -s base contextCSN
# extended LDIF
#
# LDAPv3
# base <o=infra,c=com> with scope baseObject
# filter: (objectclass=*)
# requesting: contextCSN
#
# infra, com
dn: o=infra,c=com
contextCSN: 20180917142109.765066Z#000000#000#000000
contextCSN: 20230612144901.796553Z#000000#001#000000
contextCSN: 20230612144904.899482Z#000000#002#000000
# search result
search: 2
result: 0 Success
# numResponses: 2
# numEntries: 1
On Mon, 12 Jun 2023 at 16:42, Quanah Gibson-Mount <quanah(a)fast-mail.org>
wrote:
>
>
> --On Monday, June 12, 2023 5:36 PM +0200 cYuSeDfZfb cYuSeDfZfb
> <cyusedfzfb(a)gmail.com> wrote:
>
> > Hi Quanah,
> >
> > Thanks for the swift reponse! I think I do, yes, see, from consumer one:
> >
> > olcSyncrepl: {0}rid=202
> > provider=ldap://master-acc-02.ldap.infra.com:389 bindmethod=simple
> > filter="(objectClass=*)" scope=sub binddn="cn=mirrormode,ou=Directory
> > Access,o=infra,c=com" credentials=XYZ searchbase="o=infra,c=com"
> > schemachecking=on type=refreshAndPersist retry="60 +" attrs="*,+"
> > starttls=critical tls_reqcert=demand
> > olcSyncrepl: {1}rid=201
> > provider=ldap://master-acc-01.ldap.infra.com:389 bindmethod=simple
> > filter="(objectClass=*)" scope=sub binddn="cn=mirrormode,ou=Directory
> > Access,o=infra,c=com" credentials=XYZ searchbase="o=infra,c=com"
> > schemachecking=on type=refreshAndPersist retry="60 +" attrs="*,+"
> > starttls=critical tls_reqcert=demand
> > olcUpdateRef: ldap://provider-acc-02.ldap.infra.com:389
> > olcUpdateRef: ldap://provider-acc-01.ldap.infra.com:389
>
> That's syncrepl, not syncprov.
>
> However, the issue could be ACLs. If you use the rootdn for your database
> to run the query, can you see the contextCSN value stored in your database
> root?
>
> --Quanah
>
>
>
>