It seems linphone can do push notifications, which is a compelling feature, but of *course* it means I have to compile my own builds and set up my own FCM project because Google FCM is hostile to open source deployment.
-
Show this thread
-
Fine. # emerge android-studio
3 replies 0 retweets 10 likesShow this thread -
Of course this is what a PHP developer would do.pic.twitter.com/NNuZsp0XXW
3 replies 2 retweets 18 likesShow this thread -
-
Looks like this is a cross-sig on the DigiCert root by the old Symantec one. So either the DigiCert root is not in the JRE shipped by android-studio, or Java's Symantec blacklist code is horribly broken and bans even valid root certs that just happen to have a Symantec cross.
2 replies 0 retweets 2 likesShow this thread -
Replying to @marcan42
…why is this site serving a copy of the root in its chain, and specifically a copy cross-signed by a CA that's no longer trusted like honestly I can't blame the client, if I walked the chain and the last thing on it contained a signature from a revoked root I'd probably bail too
1 reply 0 retweets 0 likes -
like, if you go an entirely normal 2 certs deep, you find an intermediate signed by a root that's probably in your trust store… but within the sent chain you can go 1 deeper, and then you get something signed by a cert you have listed as explicitly distrusted
1 reply 0 retweets 0 likes -
Replying to @11rcombs
Because legacy devices wouldn't have the new root in their trust store (and also wouldn't ban the old root).
1 reply 0 retweets 0 likes -
Replying to @marcan42
they apparently recommend that configuration only for "Non-browser with VeriSign G5 root only" clients, and for "Older browsers, smart phones, and feature phones including old versions" and "Java" suggest a root cross-signed by Baltimore CyberTrust
1 reply 0 retweets 0 likes -
(the Baltimore root has actually been supported in Java for longer than the Verisign one has)
1 reply 0 retweets 0 likes
This is cloudfront, so a generic Amazon thing!
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.