- Aug 03, 2017
-
-
Daniel Gultsch authored
-
Daniel Gultsch authored
-
Daniel Gultsch authored
-
Daniel Gultsch authored
-
- Aug 02, 2017
-
-
Daniel Gultsch authored
-
Daniel Gultsch authored
-
- Aug 01, 2017
-
-
Daniel Gultsch authored
-
- Jul 30, 2017
-
-
Daniel Gultsch authored
-
Daniel Gultsch authored
-
Daniel Gultsch authored
-
- Jul 29, 2017
-
-
Daniel Gultsch authored
-
Daniel Gultsch authored
-
- Jul 28, 2017
-
-
Daniel Gultsch authored
-
Daniel Gultsch authored
-
- Jul 26, 2017
-
-
Daniel Gultsch authored
-
- Jul 25, 2017
-
-
Daniel Gultsch authored
Give up PGP decryption when intent is cancelled
-
yushijinhun authored
When receiving a PGP message which is not encrypted with YOUR key, OpenKeychain shows a dialog, which tells you the private key to decrypt the message is unavailable. However, Conversations won't give up decrypting the message. So whether the subsequent messages are decryptable or not, the decryption is blocked at the current message. The commit fixes the bug in this way: Give up the current message when the decryption intent is cancelled, so that subsequent messages can be handled.
-
- Jul 23, 2017
-
-
Daniel Gultsch authored
-
Daniel Gultsch authored
-
Daniel Gultsch authored
this undos 8a729061. as it turns out 4.1 and 4.0 only break when checking if a cert is self signed.
-
- Jul 21, 2017
-
-
Daniel Gultsch authored
-
- Jul 18, 2017
-
-
Daniel Gultsch authored
-
Daniel Gultsch authored
-
Daniel Gultsch authored
-
Daniel Gultsch authored
-
Daniel Gultsch authored
-
Daniel Gultsch authored
-
Daniel Gultsch authored
-
Daniel Gultsch authored
-
Daniel Gultsch authored
-
Daniel Gultsch authored
-
Daniel Gultsch authored
-
- Jul 17, 2017
-
-
Daniel Gultsch authored
-
Daniel Gultsch authored
-
Daniel Gultsch authored
-
Daniel Gultsch authored
-
- Jul 16, 2017
-
-
Daniel Gultsch authored
-
Daniel Gultsch authored
-
Daniel Gultsch authored
-
Daniel Gultsch authored
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())
-