search for: tls_

Displaying 10 results from an estimated 10 matches for "tls_".

Did you mean: tls
2015 Oct 08
2
Dovecot auth-ldap ignores tls_* settings when using ldaps://
Hi, I'm using dovecot 2.2.9 (but after checking src/auth/db-ldap.c in 2.2.13 there seems to be the same bug/feature). The userdb and passdb use LDAP. All further configuration is done in auth-ldap.conf.ext. uri = ldaps://<host>/ # tls = tls_cert_file = /etc/ssl/certs/client-cert.pem tls_key_file = /etc/ssl/certs/client-key.file Dovecot ignores the tls_* options. If I use an ldap:// URI and switch on TLS using tls=yes it works as expected. But I do not see any reason why LDAPS should not read the tls_* settings. This small pa...
2015 Oct 13
0
Dovecot auth-ldap ignores tls_* settings when using ldaps://
...m using dovecot 2.2.9 (but after checking src/auth/db-ldap.c in 2.2.13 > there seems to be the same bug/feature). > > The userdb and passdb use LDAP. All further configuration is done in > auth-ldap.conf.ext. > > uri = ldaps://<host>/ > # tls = > tls_cert_file = /etc/ssl/certs/client-cert.pem > tls_key_file = /etc/ssl/certs/client-key.file > > Dovecot ignores the tls_* options. If I use an ldap:// URI and > switch on TLS using tls=yes it works as expected. > > But I do not see any reason why LDAPS should not read the t...
2015 Dec 07
7
v2.2.20 released
...nges. This fix includes some extra checks, which makes sure that if such a conflict still happens it's automatically fixed. In some situations such an automatic fix may now be unnecessarily triggered and an error logged. - director: Backend tags weren't working correctly. - ldap: tls_* settings weren't used for ldaps URIs. - ldap, mysql: Fixed setting connect timeout. - auth: userdb lookups via auth-worker couldn't change username - dsync: Fixed handling deleted directories. Make sure we don't go to infinite mailbox renaming loop. - imap: Fixed crash in NOTIFY...
2015 Dec 07
7
v2.2.20 released
...nges. This fix includes some extra checks, which makes sure that if such a conflict still happens it's automatically fixed. In some situations such an automatic fix may now be unnecessarily triggered and an error logged. - director: Backend tags weren't working correctly. - ldap: tls_* settings weren't used for ldaps URIs. - ldap, mysql: Fixed setting connect timeout. - auth: userdb lookups via auth-worker couldn't change username - dsync: Fixed handling deleted directories. Make sure we don't go to infinite mailbox renaming loop. - imap: Fixed crash in NOTIFY...
2008 Feb 11
1
v1.1.beta15 released
...error message is now written to a file in base_dir as well as to log file. When Dovecot starts the next time it shows this error message to user and asks to look into error log file. I'm hoping this will reduce "why dovecot exits silently after starting it?" questions. - LDAP: Added tls_* settings for using TLS with OpenLDAP. - POP3-only users shouldn't get dovecot.index.cache files created anymore when quota plugin is used - Fixed/optimized handling pipelined commands - rawlog: added -b parameter to log packet boundaries. - auth: %a and %b were broken -------------- next...
2015 Dec 03
8
v2.2.20 release candidate released
...nges. This fix includes some extra checks, which makes sure that if such a conflict still happens it's automatically fixed. In some situations such an automatic fix may now be unnecessarily triggered and an error logged. - director: Backend tags weren't working correctly. - ldap: tls_* settings weren't used for ldaps URIs. - ldap, mysql: Fixed setting connect timeout. - auth: userdb lookups via auth-worker couldn't change username - dsync: Fixed handling deleted directories. Make sure we don't go to infinite mailbox renaming loop. - imap: Fixed crash in NOTIFY...
2015 Dec 03
8
v2.2.20 release candidate released
...nges. This fix includes some extra checks, which makes sure that if such a conflict still happens it's automatically fixed. In some situations such an automatic fix may now be unnecessarily triggered and an error logged. - director: Backend tags weren't working correctly. - ldap: tls_* settings weren't used for ldaps URIs. - ldap, mysql: Fixed setting connect timeout. - auth: userdb lookups via auth-worker couldn't change username - dsync: Fixed handling deleted directories. Make sure we don't go to infinite mailbox renaming loop. - imap: Fixed crash in NOTIFY...
2015 Jun 23
2
a temporary failure
...c/auth/db-ldap.c description: auth ldap: Make sure config file path is included in all fatal error messages. changeset: 18359:ec2e7ae958c5 user: Timo Sirainen <tss at iki.fi> date: Mon Mar 16 23:17:39 2015 +0200 files: src/auth/db-ldap.c description: auth ldap: If any tls_* settings are given when they're not supported, fail with fatal instead of just warning. These may be important for intended security, especially tls_cipher_suite. We shouldn't allow setting them and then somewhat silently just ignore them. .... - -- Steffen Kaiser -----BEGIN PGP SIGNA...
2015 Jun 23
0
a temporary failure
...ke sure config file path is included in all > fatal error messages. > > > changeset: 18359:ec2e7ae958c5 > user: Timo Sirainen <tss at iki.fi> > date: Mon Mar 16 23:17:39 2015 +0200 > files: src/auth/db-ldap.c > description: > auth ldap: If any tls_* settings are given when they're > not supported, fail with fatal instead of just warning. > These may be important for intended security, especially > tls_cipher_suite. > We shouldn't allow setting them and then somewhat silently > just ignore them. > > .... > &g...
2015 Jun 23
2
a temporary failure
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, 22 Jun 2015, lejeczek wrote: > On 22/06/15 09:43, Steffen Kaiser wrote: >> On Mon, 22 Jun 2015, lejeczek wrote: >>> On 22/06/15 09:16, lejeczek wrote: >>>> >>>> to=<me at my.domain>,orig_to=<root at localhost>, relay=dovecot, delay=39296, >>>> delays=39294/2.2/0/0.27,