You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It looks like a lot of PRs and issues aren't processed yet. I see that contributors or Smack XMPP client, DAVx5 and Conversations all used the MTM but switched to own solutions
The Smack is used by the Yaxim, Xabber, aTalk but also the Spark client for a desktop. And the Spark has a very extended settings for certs including mutual auth. But it's outdated and has a bug which not fails the LetsEncrypt cert chain.
So I decided to find some trust manager with similar features that already in production use and came to your repo.
So my question is: could you check PRs and collect all the changes to make the MTM to be the "standard" trust manager? The current situation is dangerous because due to fragmentation we have to fix bugs, add features, translate and reinvent the wheel again and again. Having the same lib for both Java and Android would be also great.
The text was updated successfully, but these errors were encountered:
It looks like a lot of PRs and issues aren't processed yet. I see that contributors or Smack XMPP client, DAVx5 and Conversations all used the MTM but switched to own solutions
So I decided to find some trust manager with similar features that already in production use and came to your repo.
So my question is: could you check PRs and collect all the changes to make the MTM to be the "standard" trust manager? The current situation is dangerous because due to fragmentation we have to fix bugs, add features, translate and reinvent the wheel again and again. Having the same lib for both Java and Android would be also great.
The text was updated successfully, but these errors were encountered: