similar to: Working with PEM content

Guys, that was very interesting and useful stuff you preached there. Mind if I make a patch to the FAQ and include it somewhere? "Q: When should I develop against a branch? A: Only if you are making really big or controversial changes. ... blah blah I am thinking that it would be highly useful for the project, if somebody (yours sincerely) took it upon himself to hunt and gather the very

On Wed, Jun 13, 2012 at 3:41 PM, Mikael Lyngvig <mikael at lyngvig.org> wrote: > Guys, that was very interesting and useful stuff you preached there. Mind > if I make a patch to the FAQ and include it somewhere? > > "Q: When should I develop against a branch? A: Only if you are making > really big or controversial changes. ... blah blah > > I am thinking that it

I think the best way that I can currently contribute to the project is through technical writing. So I see myself as doing a serious, long-term project of extending the FAQ. So, I can affirm that I want to really start working :) This at the same time as I plan to regularly release an unofficial Windows distro of Clang with headers and libraries so people don't need to install MinGW to use

> 8. A Technical Writer FAQ (should include the Sphinx documentation from the lld docs). I'm working on the Sphinx stuff; if you have any questions about writing Sphinx docs feel free to ask. --Sean Silva On Wed, Jun 13, 2012 at 4:37 PM, Mikael Lyngvig <mikael at lyngvig.org> wrote: > I think the best way that I can currently contribute to the project is > through technical

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

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

I just finished up the first draft of the FAQ translated verbatim from HTML to Sphinx. Sphinx did puzzle me a few times but I got used to its approximate error messages and figured out what the problems were. Perhaps you could take a quick glance at this file and tell me if I am doing something wrong? Otherwise I'll send it off to llvm-commits and see what they say. Thanks, Mikael

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;

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:

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

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

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 >>>

Jan Vejvalka <jan.vejvalka at lfmotol.cuni.cz> writes: >> Mine are below and they work just fine: >> >> ssl_cipher_list = >>

On Fri, 22 Jun 2018, Aki Tuomi wrote: >> Do I need to make a fresh dh.pem? The upgrade doc tells how to convert >> ssl-parameters.dat but how to make a new one? > > ... or you can make a fresh one using openssl > gendh 4096 > dh.pem This also works openssl dhparam -out dh.pem 4096 > Note that this will require quite a lot of entropy, so you should > probably

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

> On 19 August 2018 at 20:55 Aki Tuomi <aki.tuomi at dovecot.fi> wrote: > > > > > On 19 August 2018 at 19:38 Kai Schaetzl <maillists at conactive.com> wrote: > > > > > > Aki Tuomi wrote on Sun, 19 Aug 2018 18:21:31 +0300: > > > > > Just generate new parameters on some machine with good entropy source. > > > > So, if

Don't know if this was corrected in 2.3.4 (haven't upgraded yet but didn't see it in the notes) - but in 2.3.3 I see this in my log: imap-login: Error: Diffie-Hellman key exchange requested, but no DH parameters provided. Set ssh_dh=</path/to/dh.pem So...either there's an undocumented feature of SSH-over-IMAP (that's Dovecot - always on the cutting edge!) or someone had

Done. Do you want to see it again or should I simply ship it off to llvm-commits? The only thing I've changed from the original HTML is that I've changed a few missing code pieces into using code markup. And now I've made the changes you requested and I think it looks really good: Each question being a subsection of its own works very well in my opinon. Oh, heck, I might as well

Thanks Joseph, Aki, but something missing from upgrade document, where does the dh param file go? I located ssl-parameters.dat so I will put it there. Quoting Joseph Tam <jtam.home at gmail.com>: > On Fri, 22 Jun 2018, Joseph Tam wrote: > >> However, recent advances make this condition obsolete [*] and not >> really safer, so a much faster way to generate a DH key is

I did that the last time one year ago, now on another machine with the same software (Ubuntu 16.04) it fails. openssl dhparam 4096 > /var/lib/dovecot/ssl-parameters.dat dd if=/var/lib/dovecot/ssl-parameters.dat bs=1 skip=88 | openssl dhparam -inform der > /etc/dovecot/dh.pem last command fails with 681+0 records in 681+0 records out 681 bytes copied, 0,00278343 s, 245 kB/s unable to load