Please describe the problem.
Entering a jabber address which's server got a selfsigned certificate, the process just fails, without asking for acceptance for that certificate. This is quite a showstopper. (for example: jabber.ccc.de)
What steps will reproduce the problem?
Try with an account from e.g. jabber.ccc.de
What version of git-annex are you using? On what operating system?
Arch Linux, aur/git-annex-standalone 4.20130709-1
Please provide any additional information below.
There is no logoutput to add... I'm sorry.
# If you can, paste a complete transcript of the problem occurring here.
# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
# End of transcript or log.
Hmm, actually the XMPP library it's using does not fail on an invalid or self-signed cert. This is something that SSL using libraries sadly often get wrong, and yeah, I see I contacted the library author a while ago, and a "sessionIsSecure" has been added to it, which can be used to check if the cert was valid.
This leaves open the question of what's happening with you on the CCC server. Did you get an error message?
When will this issue be fixed? Currently my Jabber account is on jabber.ccc.de.
This is the error message:
Can you advise me another trustworthy non-profit and free (free as in free beer" as well as "free as in free speech") jabber server?
AFAIKS, this is not a failure from a self-signed certificate. git-annex contacted the jabber server, accepted its certificate, and tried to log in. The jabber server rejected the login.
This kind of problem has in the past turned out to involve incompatabilities in SASL authentication using some newish authentication schemes. Often it's been a bug in the XMPP server that's tickled by the haksell TLS library. See for example http://bugs.debian.org/717463
So, what XMPP server is used by CCC?