Daniel Gultsch 8afe7efc2c workaround for OpenFire: check CN first in self signed certs ... The self signed certificates created by OpenFire (Not sure if other certs are affected as well) will crash the Java/Android TLS stack when accessing getSubjectAlternativeNames() on the the peer certificate. This usually goes unnoticed in other applications since the DefaultHostnameVerifier checkes the CN first. That however is a violation of RFC6125 section 6.4.4 which requires us to check for the existence of SAN first. This commit adds a work around where in self signed certificates we check for the CN first as well. (Avoiding the call to getSubjectAlternativeNames())		2017-07-16 11:05:25 +02:00
..
crypto	workaround for OpenFire: check CN first in self signed certs	2017-07-16 11:05:25 +02:00
entities	sync around Conversation.getLatestMessage()	2017-07-11 23:09:51 +02:00
generator	upgrade to signal-protocol-java. thanks @ysangkok	2017-06-18 16:36:30 +02:00
http	also check for hostname in in certs if hostname is from trusted source	2017-06-21 23:40:01 +02:00
parser	refactored retrieval of default preferences	2017-07-01 13:41:24 +02:00
persistance	more migration fixes for updating from 1.6.0 to 1.19.3	2017-07-14 10:34:01 +02:00
services	disable foreground service if all accounts are disabled	2017-07-12 11:03:32 +02:00
ui	show date separators. fixes #2271	2017-07-04 11:01:20 +02:00
utils	add reminder to remove minidns workarounds once those are fixed	2017-07-14 09:09:26 +02:00
xml	do not check if namespace equals prefix for attributes	2017-05-30 19:05:36 +02:00
xmpp	verify with hostname in direct tls connections	2017-07-13 19:27:43 +02:00
Config.java	omemo: put auth tag into key (verify auth tag as well)	2017-03-26 12:39:18 +02:00