Re: No supported cipher suites have been found.

On 12/1/24 05:50, Sam Varshavchik wrote:
> Mike Wright writes:
> 
>> Thanks for the quick response.
>>
>> I never mess with this setup and the system lives on a remote server 
>> (rented service).
>>
>> Here's what esmptd-ssl says about DHPARAMS:
>>     TLS_DHPARAMS=/etc/courier/dhparams.pem
>>
>> ls -l /etc/courier/dhparams.pem
>>     -rw------- 1 courier root 3535 Oct 14 08:21 dhparams.pem
>>
>> I checked all my certs with openssl and got some strange results:
>>
>> /etc/letsencrypt/archive/a.mx.hostisimo.com/ \
>>   {cert,chain,fullchain,privkey}X.pem and found the complete history 
>> validated using "openssl x509 -in PATH_TO_CERT -noout -text and 
>> everything checked out EXCEPT privkeyX.pem. NONE of the were readable,
>> throwing "Could not read certificate from privkeyX.pem".
>>
>> On to /etc/courier and found dhparams.pem threw the same error.  ls -l 
>> dhparams.pem -rw------- 1 courier root 3535 Oct 14 08:21 dhparams.pem. 
>> That cert was auto-generated mid October by /usr/lib/courier/mkdhparams.
>>
>> The debian o/s is up to date, all upgrades applied.  This is acting 
>> like the openssl package has become corrupted (my best guess).  Could 
>> memory be a culprit?
>>
>> The question is why certs are OK but keys and dhparams are not.
> 
> One common denominator is that these files have restricted permissions, 
> because they are secrets. Note that they are not world-readable.
> 
> Didn't you say that you updated and/or replaced packages. If you 
> replaced Debian's native packages with the ones that are built from the 
> source, they're configured differently, using differed userids.
> 
> Run "courierauthconfig --configfiles" and the shown mailuser and 
> mailgroup should correspond to the ownership of the secret files.
> 

Sorry to be a pain.

courierauthconfig is not part of the .deb packages so I decided to wade 
into territory I haven't visited in decades and compile the whole 
shebang. I started by installing "build-essential".

courier-unicode built without a hitch.  courier-authlib isn't going so 
well.  So far it has required libtool, expect, libgdbm-dev, and now 
libidn2.  Finding it was problematic ( it's at ftp.gnu.org ).  It built 
cleanly.

Back at courier-authlib ./configure stops here:

     libidn2:checking for libidn2 >= 2.0.5... no
     configure: error: libidn2 not found
     configure: error: ./configure failed for libs/rfc822

/usr/local/bin/idn2 --version is 2.3.7. /usr/local/{include,lib} has the 
.h .a .la and .so files.  How do I proceed from here?

Thanks



_______________________________________________
courier-users mailing list
[email protected]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users