Re: cyradm and TLS 1.2

[John Widera <jwidera@xxxxxxxxxx>]

Turns out imclient (at least in the latest RHEL7 pkg) is hardcoded to use TLSv1.  Since we're building binary RPMs from Source RPMs anyway we modified imclient.c, rebuilt the RPMs, reinstalled the cyrus-imapd-utils package:  Here's the patch we used:

----------------------------------------------------

--- imclient.c.orig 2012-12-01 13:57:54.000000000 -0600
+++ imclient.c 2019-10-03 14:40:11.254566297 -0500
@@ -1695,7 +1695,7 @@
return -1;
}

- imclient->tls_ctx = SSL_CTX_new(TLSv1_client_method());
+ imclient->tls_ctx = SSL_CTX_new(TLSv1_2_client_method());
if (imclient->tls_ctx == NULL) {
return -1;
};

-------------------------------------------

Maybe this helps someone else.

Regards,

 

Hi All,

We're hoping to find some help on the list...

We are running Cyrus-IMAP on RHEL7, using an RPM pkg (cyrus-imapd-2.4.17-13.el7) built from the Red Hat SRC RPM.  We also have SASL, Utils, devel etc pkgs all from RH.

Now we're looking to finally move Cyrus completely off insecure TLS versions.  But now there is a lingering issue...

We removed tls1_0 from impad.conf, and the CYRADM shell stopped working.  We can no longer connect at all:

cyradm -u cyrus <server>
[ SSL_connect error -1 ]
[ SSL session removed ]
[ TLS negotiation did not succeed ]
cyradm: cannot authenticate to server with as cyrus

cyradm -u cyrus --notls <server>
[ SSL_connect error -1 ]
[ SSL session removed ]
[ TLS negotiation did not succeed ]
cyradm: cannot authenticate to server with as cyrus

The presumption is (as cyradm is just a wrapper script) any PERL scripts calling Cyrus::IMAP::Admin over a STARTTLS connection could likewise be broken (?) if we block TLS 1.0. 

cyradm is using TLSv1 per maillog:

imaps[14096]: starttls: TLSv1 with cipher <snip>

Our MAN page for cyradm shows a "--notls" option, which does not work/changes nothing.  Oddly, the cyradm help flag does NOT show this option, yet cyradm doesn't bark when it's passed:

Usage: cyradm [args] server
--user <user> Connect as <user> (authentication name)
--authz <user> Authorize as <user>
--[no]rc (Do not) load the configuration files
--systemrc <file> Use system-wide configuration <file>
--userrc <file> Use user configuration <file>
--port <port> Connect to server on <port>
--auth <mechanism> Authenticate with <mechanism>

A web search reveals the MAN page for cyradm in Cyrus v.3, and it shows notls as an option to AUTHENTICATE, after a server connection is made, so its unclear to me what's going on... 

Does anyone have cyradm working with TLS1.2?

 

Regards & THANKS in advance for any assistance or suggestions offered.

 

--

John

----
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus

----
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus