Handle bad SSL cert case w/ better error thrown to user or acting like Element

[krille-chan]

Description

A clear and concise description of what the issue is about.

When connecting to a Matrix server w/ a bad SSL cert wherein the domain names listed don't match the actual domain, FluffyChat throws an error about a "bad password" to the end user. This obfuscates info that a user could then take to the Homeserver admins to be acted on and can cause user frustration over entering the correct password multiple times. It instead should either handle the issue as Element does or otherwise throw an error about conflicting domains in the SSL cert to the user instead of bad password.

For example, someone may have the SSL cert for abc.social have the listed domain be matrix.abc.social instead of abc.social.

Element seems to be the outlier in ignoring(?) this cert conflict and connects users as NeoChat also currently has login issues for this case

To Reproduce

If this issue is describing a bug, include some steps to reproduce the behaviour.

1. Try to connect to Homeserver instance w/ a SSL cert that lists a different domain. At time of writing monero.social is one such site w/ a cert domain of matrix.monero.social. If you are unsure if the site has a conflictive cert, you can use: https://www.ssllabs.com/ssltest/analyze.html
2. Verify that you get a 'Bad Password' error thrown

Additional information:

• Device: Fedora 34 KDE, Android 11
• OS and OS version: N/A
• Installed version of FluffyChat: Flathub 2021/05/26 release, Android 0.31.1
• (Android only) Which store are you using: F-droid
• (Android only) Are Google Services available: Yes

/issue fluffy

[github-actions]

This issue is stale because it has been open for 120 days with no activity.

[github-actions]

This issue was closed because it has been inactive for 14 days since being marked as stale.