public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Walter Dnes <waltdnes@waltdnes.org>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] [SOLVED] fetchmail: OpenSSL reported: error:0A00018A:SSL routines::dh key too small
Date: Tue, 29 Oct 2024 02:10:36 -0400	[thread overview]
Message-ID: <MTAwMDAzMC53ZG5lc2RheQ.1730182231@quikprotect> (raw)
In-Reply-To: <MTAwMDA0MC53ZG5lc2RheQ.1729962853@quikprotect>

On Sat, Oct 26, 2024 at 01:14:17PM -0400, Walter Dnes wrote
>   My personal domain inbound email is directed to COTSE.net.  I pull
> with fetchmail.  After yesterday's world update, fetchmail has been
> failing with the error message in the subject.  I can still access my
> incoming email via webmail mode (BLEAGH!!!).  I've set my gmail address
> to forward directly to my ISP inbox, avoiding this problem.

  *I'M BACK!*  It may have been a co-incidence that I ran into the
problem right after an @world update https://www.cotse.net/notices.html

> Oct 28 - During a recent deployment for some configuration changes, an
> incorrect version of a dovecot configuration file was deployed. This
> resulted in a weak Diffie-Hellmann parameter (1024 instead of 2048)
> to be used in our imaps and pops protocols, as well as some weaker
> ciphers to be available. We were notified by one of our subscribers
> and it has been corrected. We do not see evidence of any of our
> subscriber's email clients having selected a weaker cipher during
> this time, which could be an indication of a MITM attack on that
> subscriber. This did not affect webmail users.

-- 
There are 2 types of people in this world
1) Those who can extrapolate from incomplete data


      parent reply	other threads:[~2024-10-29  6:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-26 17:14 [gentoo-user] fetchmail: OpenSSL reported: error:0A00018A:SSL routines::dh key too small Walter Dnes
2024-10-26 17:47 ` Michael
2024-10-29  6:10 ` Walter Dnes [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=MTAwMDAzMC53ZG5lc2RheQ.1730182231@quikprotect \
    --to=waltdnes@waltdnes.org \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox