Displaying 20 results from an estimated 6000 matches similar to: "ssl_dh"
2019 Mar 16
0
ssl_dh
<!doctype html>
<html>
<head>
<meta charset="UTF-8">
</head>
<body>
<div>
ssl_dh is required from 2.3.0-2.3.2. From 2.3.3 onwards its optional. You can rm the ssl-parameters.dat file to get rid of that warning.
</div>
<div>
<br>
</div>
<div>
Aki
</div>
<blockquote
2019 Feb 24
2
password protected ssl key seems unsupported after update to 2.3.4.1
Hi,
On a debian server after an update to dovecot to 2.3.4.1 imaps mail client stop working.
I?ve applied necessary migration for ssl_dh (cf https://wiki.dovecot.org/Upgrading/2.3 <https://wiki.dovecot.org/Upgrading/2.3> ) but that was not enough. The workaround I?ve setup was to remove password protection from the ssl_key file. All tests with ssl_key_password parameter failled (direct
2019 Mar 16
2
ssl_dh
I'm subscribed, please reply to list directly.
> ssl_dh is required from 2.3.0-2.3.2. From 2.3.3 onwards its optional.
> You can rm the ssl-parameters.dat file to get rid of that warning.
I have no ssl-parameters.dat file.
--
sergio.
2018 Jul 16
1
ssl_dh required, even though DH is disabled.
Here's my config:
# 2.3.2 (582970113): /etc/dovecot/dovecot.conf
# OS: Linux 4.17.5-1-ARCH x86_64 Arch Linux
# Hostname: vault
passdb {
? driver = pam
}
protocols = imap
service imap-login {
? inet_listener imap {
??? port = 0
? }
}
ssl = required
ssl_cert = </etc/letsencrypt/live/myhostname.com/fullchain.pem
ssl_cipher_list =
2018 Dec 14
2
Upgrade to 2.3.1 has failed
Problem:
We had Dovecot v2.2 working just fine under openSUSE Leap 42.3. But we
upgraded openSUSE to Leap 15.0.
In the process, Dovecot got upgraded from 2.2 to 2.3.1. It no longer
works and I haven't figured out how to downgrade to the older working
version.
The key issue seems to be the change to requiring dh.pem and changing s
sl_protocols to ssl_min_protocols.?I think I've navigated
2019 May 27
1
ssl_dh
Does ssl_dh need to be manually updated each time the underlying certificate renews?
--
2+2=5 for sufficiently large values of 2.
2017 Oct 29
2
dovecot-2.3 (-git) Warning and Fatal Compile Error
Hi Aki,
On 30/10/2017 12:43 AM, Aki Tuomi wrote:
>> On October 29, 2017 at 1:55 PM Reuben Farrelly <reuben-dovecot at reub.net> wrote:
>>
>>
>> Hi again,
>>
>> Chasing down one last problem which seems to have been missed from my
>> last email:
>>
>> On 20/10/2017 9:22 PM, Stephan Bosch wrote:
>>>
>>> Op 20-10-2017 om
2017 Oct 29
2
dovecot-2.3 (-git) Warning and Fatal Compile Error
Hi again,
Chasing down one last problem which seems to have been missed from my
last email:
On 20/10/2017 9:22 PM, Stephan Bosch wrote:
>
>
> Op 20-10-2017 om 4:23 schreef Reuben Farrelly:
>> On 18/10/2017 11:40 PM, Timo Sirainen wrote:
>>> On 18 Oct 2017, at 6.34, Reuben Farrelly <reuben-dovecot at reub.net>
>>> wrote:
This problem below is still
2017 Oct 31
2
dovecot-2.3 (-git) Warning (Was Re: dovecot Digest, Vol 174, Issue 64)
Hi,
On 30/10/2017 7:22 PM, dovecot-request at dovecot.org wrote:
> Message: 6
> Date: Mon, 30 Oct 2017 10:22:42 +0200
> From: Teemu Huovila <teemu.huovila at dovecot.fi>
> To: dovecot at dovecot.org
> Subject: Re: dovecot-2.3 (-git) Warning and Fatal Compile Error
> Message-ID: <7d2c0b5b-019a-067c-c6be-f36571ed9a96 at dovecot.fi>
> Content-Type: text/plain;
2017 Nov 01
2
dovecot-2.3 (-git) Warning (Was Re: dovecot Digest, Vol 174, Issue 64)
Hi again,
On 1/11/2017 12:01 AM, Aki Tuomi wrote:
>
> On 31.10.2017 15:00, Reuben Farrelly wrote:
>> Hi,
>>
>> On 30/10/2017 7:22 PM, dovecot-request at dovecot.org wrote:
>>> Message: 6
>>> Date: Mon, 30 Oct 2017 10:22:42 +0200
>>> From: Teemu Huovila <teemu.huovila at dovecot.fi>
>>> To: dovecot at dovecot.org
>>>
2017 Oct 20
3
dovecot-2.3 (-git) Warning and Fatal Compile Error
On 18/10/2017 11:40 PM, Timo Sirainen wrote:
> On 18 Oct 2017, at 6.34, Reuben Farrelly <reuben-dovecot at reub.net> wrote:
>>
>> I haven't been tracking dovecot-2.3 until now, but I've just given it a quick run, and there are a few things that may need some attention.
>>
>> /usr/include/features.h:376:4: warning: #warning _FORTIFY_SOURCE requires compiling
2019 Feb 25
0
password protected ssl key seems unsupported after update to 2.3.4.1
It's in our backlog, but not fixed yet.
Aki
On 24.2.2019 21.30, admin--- via dovecot wrote:
> Hi,
>
> On a debian server after an update to dovecot to 2.3.4.1 imaps mail
> client stop working.
> I?ve applied?necessary migration for ssl_dh
> (cf?https://wiki.dovecot.org/Upgrading/2.3?) but that was not enough.
> The workaround I?ve setup was to remove password protection
2018 Oct 09
3
Test report xen_4.11.1~pre.20180911.5acdd26fdc+dfsg-2
I'm just dumping all I got in here, after initial feedback we can see
how to organize todo's around it.
tl;dr:
* Does not upgrade cleanly from 4.8 packages, so we have to prevent this
from entering testing until we fix that.
* Live migration is broken, explodes with memory allocation errors.
---- >8 ----
1. Build packages
* I have built salsa/master using pbuilder targeting sid.
2019 Mar 29
0
Fwd: segfault in libdovecot-storage at unknown circumstances
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925961
-------- Forwarded Message --------
Subject: segfault in libdovecot-storage at unknown circumstances
Date: Fri, 29 Mar 2019 16:34:15 +0300
From: sergio <sergio+it at outerface.net>
To: Debian Bug Tracking System <submit at bugs.debian.org>
Package: dovecot-core
Version: 1:2.3.4.1-1~bpo9+1
Severity: normal
Yes, I know this is
2019 Mar 16
0
ssl_dh
On Sat, Mar 16, 2019, at 11:12 PM, sergio via dovecot wrote:
> I'm subscribed, please reply to list directly.
>
> > ssl_dh is required from 2.3.0-2.3.2. From 2.3.3 onwards its optional.
> > You can rm the ssl-parameters.dat file to get rid of that warning.
>
> I have no ssl-parameters.dat file.
Did you check
/var/lib/dovecot
?
-- K
2018 Jan 08
1
TLS problem after upgrading from v2.2 to v2.3
Jan Vejvalka <jan.vejvalka at lfmotol.cuni.cz> writes:
>> Mine are below and they work just fine:
>>
>> ssl_cipher_list =
>>
2018 Nov 05
2
usb post passthough stopped workng after kernel upgrade
Greetings,
I have a vm on debian 9.5 to which I pass an specific usb from the host. here is the relevant part in the vm's xml file:
<hostdev mode='subsystem' type='usb' managed='yes'>
<source>
<vendor id='0x148f'/>
<product id='0x5572'/>
</source>
<address type='usb'
New install - getting error: "Failed to initialize SSL server context: Couldn't parse DH parameters"
2018 Nov 13
1
New install - getting error: "Failed to initialize SSL server context: Couldn't parse DH parameters"
Actually you need to use ssl_dh=</usr/local/etc/dovecot/dh.pemNote the <Aki
-------- Original message --------From: "Michael A. Peters" <mpeters at domblogger.net> Date: 13/11/2018 05:44 (GMT+02:00) To: dovecot at dovecot.org Subject: Re: New install - getting error: "Failed to initialize SSL server context: Couldn't parse DH parameters" tryopenssl dhparam
New install - getting error: "Failed to initialize SSL server context: Couldn't parse DH parameters"
2018 Nov 13
3
New install - getting error: "Failed to initialize SSL server context: Couldn't parse DH parameters"
I?m setting up Dovecot using Homebrew on a new server and am getting this when I try to login via IMAP:
Nov 13 14:13:35 auth: Debug: auth client connected (pid=30719)
Nov 13 14:13:35 imap-login: Info: Aborted login (no auth attempts in 0 secs): user=<>, rip=::1, lip=::1, secured, session=<gM0HNIN6HtoAAAAAAAAAAAAAAAAAAAAB>
Nov 13 14:18:33 auth: Debug: Loading modules from directory:
2018 Aug 03
0
ssl_dh required, even though DH is disabled.
Hi!
This change has now been committed, please find it at
https://github.com/dovecot/core/compare/cd08262%5E...dd6323.patch
Aki
On 16.07.2018 09:53, Aki Tuomi wrote:
> This is a known issue, but thanks for reporting it.
>
>
>
> ---
> Aki Tuomi
> Dovecot oy
>
> -------- Original message --------
> From: Eric Toombs <ewtoombs at uwaterloo.ca>
> Date: