Displaying 20 results from an estimated 133 matches for "tlsv1.1".
Did you mean:
tlsv1.2
2014 Dec 02
2
disabling certain ciphers
On 12/2/2014 1:32 AM, Reindl Harald wrote:
>
> Am 02.12.2014 um 06:44 schrieb Will Yardley:
>> On Mon, Dec 01, 2014 at 09:27:48PM -0800, Darren Pilgrim wrote:
>>> On 12/1/2014 4:43 PM, Will Yardley wrote:
>>>> Can you use both ssl_protocols *and* ssl_cipher_list in the same config
>>>> (in a way that's sane)?
>>>
>>>> Is there a
2013 Sep 09
2
How to disable SSL and TLSv1.1?
I'm running Dovecot 2.2.5 and want to make it refuse SSLv2, SSLv3 and
TLSv1.0. Clients will opportunistically use TLS 1.1 and 1.2, but now I
want require they do so. Is it enough to set
ssl_cipher_list = HIGH:!SSLv2:!SSLv3:!TLSv1.0:!aNULL:!MD5
or are there additional settings I need to specify?
2014 Dec 02
4
disabling certain ciphers
On Mon, Dec 01, 2014 at 09:27:48PM -0800, Darren Pilgrim wrote:
> On 12/1/2014 4:43 PM, Will Yardley wrote:
> > Can you use both ssl_protocols *and* ssl_cipher_list in the same config
> > (in a way that's sane)?
>
> > Is there a way to exclude these ciphers, while still keeping my config
> > easy to parse and avoiding duplicative or deprecated configs?
>
>
2020 Oct 16
2
Dovecot won't accept IMAP TLS 1 connections from older devices [SOLVED]
I've spent days scouring the Internet and trying various solutions on a
problem with my Dovecot installation, so I thought I'd share what I
learned in hopes of saving other people a lot of time.? The dedicated
Dovecot hands will know all of the following already.? This is for those
of us that have to cover a lot of bases.
I upgraded my mail server from Ubuntu 18.04.1 to Ubuntu
2019 Jul 20
2
Dovecot with MySQL over SSL.
<!doctype html>
<html>
<head>
<meta charset="UTF-8">
</head>
<body>
<div>
<br>
</div>
<blockquote type="cite">
<div>
On 20/07/2019 13:12 Reio Remma via dovecot <
<a href="mailto:dovecot@dovecot.org">dovecot@dovecot.org</a>> wrote:
</div>
2019 Jul 22
1
Dovecot with MySQL over SSL.
On 20 Jul 2019, at 23.02, Reio Remma via dovecot <dovecot at dovecot.org> wrote:
>
> On 20.07.2019 22:37, Aki Tuomi via dovecot wrote:
>>
>>> On 20/07/2019 21:07 Reio Remma via dovecot <dovecot at dovecot.org> <mailto:dovecot at dovecot.org> wrote:
>>>
>>>
>>> On 20.07.2019 18:03, Aki Tuomi via dovecot wrote:
>>>>
2019 Jul 20
2
Dovecot with MySQL over SSL.
<!doctype html>
<html>
<head>
<meta charset="UTF-8">
</head>
<body>
<div>
<br>
</div>
<blockquote type="cite">
<div>
On 20/07/2019 21:07 Reio Remma via dovecot <dovecot@dovecot.org> wrote:
</div>
<div>
<br>
</div>
<div>
<br>
2014 Oct 17
1
POODLE and TLSv1
I read this on the RHN commentary respecting cve-2014-3566:
https://securityblog.redhat.com/2014/10/15/poodle-a-ssl3-vulnerability-cve-2014-3566/:
. . .
The first aspect of POODLE, the SSL 3.0 protocol vulnerability, has already
been fixed through iterative protocol improvements, leading to the current TLS
version, 1.2. It is simply not possible to address this in the context of the
SSL 3.0
2014 Dec 02
2
disabling certain ciphers
Can you use both ssl_protocols *and* ssl_cipher_list in the same config
(in a way that's sane)?
ssl_protocols (>= 2.1)
and
ssl_cipher_list
co-exist, or are they mutually exclusive?
I have a Dovecot 2.2.13 system, and I tried setting:
I also tried things like
ssl_cipher_list = HIGH
or
ssl_cipher_list = HIGH:!MEDIUM:!LOW
however, doing this seems to make v3 still work unless I
2017 Apr 27
2
confused with ssl settings and some error - need help
Thank You for answers. But:
1. How should be properly configured ssl_cipher_list?
2. Ok, removed !TLSv1 !TLSv1.1.
3. Strange thing with ssl_protocols and ssl_cipher_list, because on older
server on Ubuntu 14.04 LTS, dovecot 2.2.9 and postfix 2.11.0 these two
lines looks exactly this same and no errors in mail.err file and mailes
works without any problem.
4. No, currently I don't use LMTP.
2016 Aug 02
6
TLSv1.2 support for lftp on CentOS 6.x
Hello everybody,
I am writing on that mailing list because I have an issue using lftp and I would
love to have more infos about features available on the LFTP version provided by
CentOS 6.
I try to connect to a ftp server in secured mode using FTPS explicit and I would
love to use TLSv1.2.
After several tries, I understood that the TLS negociation was not possible
using TLSv1.2 (It works only
2016 Mar 07
2
Compilation fails: SSL_TXT_SSLV2 not defined
Hello all,
I'm trying to compile dovecot 2.2.21 on OS-X 10.11.3 and I'm running a
bit of trouble with OpenSSL. I've cloned OpenSSL (OpenSSL
1.1.0-pre4-dev) from github and in openssl/ssl.h SSL_TXT_SSLV2 is not
defined anymore. Compilation fails with:
libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -I../../src/lib
-I../../src/lib-test
2017 Sep 13
2
[RFC master-2.2 0/1] Support OpenSSL 1.1 API for setting allowed TLS versions
Hi,
I came up with the following patch while trying to figure out a good solution
for the situation described in Debian bug #871987[1]. In short, OpenSSL in
Debian unstable has disabled TLSv1.0 and TLSv1.1 *by default*. That means that
unless an application requests otherwise, only TLSv1.2 is supported. In the
world of e-mail this is seemingly an issue, as there are still way too many old
clients
2019 Dec 27
1
Disabling TLS 1.1 in Centos 7 cockpit
Sure did!
I am even playing with different options (including NONE) and it seems
to ignore the contents of ssl.conf
I have tried
Environment=G_TLS_GNUTLS_PRIORITY=NORMAL:+TLS1.2:!TLS1.1:!TLS1.0:!ECDHE-RSA-AES256-SHA:
Environment=G_TLS_GNUTLS_PRIORITY=NORMAL:+TLS1.2:!TLS1.1:!TLS1.0:!ECDHE-RSA-AES256-SHA
Environment=G_TLS_GNUTLS_PRIORITY=PFS
2020 Oct 01
3
BUG: _presence_ of valid openssl.cnf Option = 'ServerPreference' causes Dovecot submission relay FAIL: "failed: Failed to initialize SSL: ..."
hi,
On 10/1/20 12:21 AM, JEAN-PAUL CHAPALAIN wrote:
> I had the same problem when migrating from Dovecot V2.2.36 on, Centos-7 to?Dovecot v2.3.8 on Centos-8
My report is specifically/solely about the addition/use of the
Options = ServerPreference
parameter.
I don't see that in your configuration.
Are you using it? In a config using Dovecot's submission proxy?
2014 Dec 02
0
disabling certain ciphers
On 12/1/2014 4:43 PM, Will Yardley wrote:
> Can you use both ssl_protocols *and* ssl_cipher_list in the same config
> (in a way that's sane)?
> Is there a way to exclude these ciphers, while still keeping my config
> easy to parse and avoiding duplicative or deprecated configs?
Yes to both. If you need to support older clients:
ssl_cipher_list =
2014 Dec 02
0
disabling certain ciphers
Am 02.12.2014 um 17:33 schrieb Darren Pilgrim:
> On 12/2/2014 1:32 AM, Reindl Harald wrote:
>>>> ssl_cipher_list = HIGH:!RC4:!MD5:!SRP:!PSK:!aNULL:@STRENGTH
>>>> ssl_dh_parameters_length = 2048
>>>> ssl_parameters_regenerate = 0
>>>> ssl_protocols = !SSLv2 !SSLv3 TLSv1 TLSv1.1 TLSv1.2
>>>
>>> But why does ssl_protocols behave
2018 Nov 14
2
different TLS protocols on different ports
Am 14.11.18 um 20:22 schrieb Aki Tuomi:
> Not possible I'm afraid.
Hello Aki,
is it not possible in 2.2.36 or not possible at all?
I stumbled upon RFC 8314 *) and I found it a welcome option to enforce more modern protocols/ciphers.
IMAPS/SUBMISSIONS aren't used widely (at least to my knowlege, many postmaster used to configure IMAP+SUBMISSION and STARTTLS)
Switching Clients to
2019 Jul 20
0
Dovecot with MySQL over SSL.
On 19.07.2019 0:24, Reio Remma via dovecot wrote:
> I'm attempting to get Dovecot working with MySQL user database on
> another machine. I can connect to the MySQL (5.7.26) instance with SSL
> enabled:
>
> mysql -h db.mrst.ee --ssl-ca=/etc/dovecot/ca.pem
> --ssl-cert=/etc/dovecot/client-cert.pem
> --ssl-key=/etc/dovecot/client-key.pem --ssl-cipher=DHE-RSA-AES256-SHA
2019 Jul 20
0
Dovecot with MySQL over SSL.
On 20.07.2019 18:03, Aki Tuomi via dovecot wrote:
>
>> On 20/07/2019 13:12 Reio Remma via dovecot < dovecot at dovecot.org
>> <mailto:dovecot at dovecot.org>> wrote:
>>
>>
>> On 19.07.2019 0:24, Reio Remma via dovecot wrote:
>>> I'm attempting to get Dovecot working with MySQL user database on
>>> another machine. I can connect to