When using the scheduler certificate, it would be convenient the tool would warn of incompatible md5 hash and recommend the course of action (update iminds password, get new cert, submit fingerprint).
Alternatively, configure openssl with tls-cipher "DEFAULT:@SECLEVEL=0", but the security implications of doing this should be considered (there's a reason why md5 is disabled...).
commandline checking can be done using
openssl x509 -text -in ~/.monroe/mnrCrt.pem
and find the "Signature Algorithm" line.
When using the scheduler certificate, it would be convenient the tool would warn of incompatible md5 hash and recommend the course of action (update iminds password, get new cert, submit fingerprint).
Alternatively, configure openssl with tls-cipher "DEFAULT:@SECLEVEL=0", but the security implications of doing this should be considered (there's a reason why md5 is disabled...).
commandline checking can be done using
and find the "Signature Algorithm" line.