jntass

> I still wonder what the use case for this is? I find this option useful when clients have different algorithm preferences. Part of the algorithm may have been disabled...

> If a device cannot do certain signatures, then the same is true for the CA signing the server cert and you would need also need a different CA. And...

> Part of the algorithm may have been disabled when the client compiled, especially if hardware algorithms are used through the engine configure. This is my current scenario. If only...

Scenario as follows  > "some clients fail" All of my clients use device through the engine option. Due to device limitations, some of them support only the ECDSA signature...

Sorry for not telling the whole story. What I really need is to configure both SM2 certificate(Actually dual SM2 certificates) and RSA certificate, SM2 algorithm is a kind of ECC...

The real scenario is to replace the ECDSA in the image above with SM2. SM2 is necessary in some cases in China.

Most scenarios are one port, and it is difficult to open a new port on the cloud. Some of the other open source projects(nginx, httpd etc) I've used with support...

TLCP中GCM相关套件正在开发中

使用这个脚本需要先make install，脚本中一些变量依赖安装路径

请更新到tassl-1.1.1b_R_0.8版本测试一下，看是否还存在问题？