Apr
21
2022
CVE-2022-21449, UI enhancements
<ul>
<li>Display the used TLS security provider in the connection test dialog</li>
<li>Updated the BC crypto provider to v171 and added the BC JSSE provider</li>
<li>(CVE-2022-21449): Currently it looks as if this is a problem of the security provider. The bouncycastle security provider seems not to have this problem. The mendelson AS2 uses the BC security provider for data encryption and data signature but the jre default security provider for TLS related operations.
As this release includes the BC JSSE provider for TLS operations (see above) it is possible to switch the jres default security provider for TLS operations to the BC JSSE provider.
Please contact the mendelson support if you need instructions regarding this issue.</li>
<li>The UI notifications have been reworked</li>
<li>Every server setting change now shows up a UI notification on each connected client</li>
<li>The certificate manager now allows to show references to the partners that use the certifciates. This makes it easy to find out what to change in the partner configuration once a certifcate has been expired</li>
</ul>