# Latest update **URL:** \ **Category:** meta\ **Created:** [April 15, 2015, 11:52pm UTC](https://cog.discourse.group/t/latest-update/986 "2015-04-15T23:52:50Z")\ **Posts on this page:** 20\ **Page:** 2
**Author:** ![Woodman](https://sea1.discourse-cdn.com/flex001/user_avatar/cog.discourse.group/woodman/32/24_2.png) [@Woodman](https://cog.discourse.group/u/Woodman)\ **Post date:** [April 20, 2015, 6:14pm UTC](https://cog.discourse.group/t/latest-update/986/21 "2015-04-20T18:14:26Z")
Yeah, but if it continues for more than 4 hours I need to talk to my doctor. ---
**Author:** ![ClockWorkXon](https://sea1.discourse-cdn.com/flex001/user_avatar/cog.discourse.group/clockworkxon/32/593_2.png) [@ClockWorkXon](https://cog.discourse.group/u/ClockWorkXon)\ **Post date:** [April 20, 2015, 6:26pm UTC](https://cog.discourse.group/t/latest-update/986/22 "2015-04-20T18:26:11Z")
You should have talked to your doctor first, before ordering from some fly-by-night online pharmacy. Aren’t you on medication for high blood pressure? ---
**Author:** ![Lee\_Ars](https://sea1.discourse-cdn.com/flex001/user_avatar/cog.discourse.group/lee_ars/32/2338_2.png) [@Lee\_Ars](https://cog.discourse.group/u/Lee_Ars)\ **Post date:** [April 20, 2015, 9:13pm UTC](https://cog.discourse.group/t/latest-update/986/23 "2015-04-20T21:13:21Z")
If you thought this broke stuff, wait until you see what I do next! (hint: trying to redirect all traffic to HTTPS and enable HSTS - that’s not actually a hint I guess but more of a full-on spoiler.) ---
**Author:** ![Lee\_Ars](https://sea1.discourse-cdn.com/flex001/user_avatar/cog.discourse.group/lee_ars/32/2338_2.png) [@Lee\_Ars](https://cog.discourse.group/u/Lee_Ars)\ **Post date:** [April 20, 2015, 11:40pm UTC](https://cog.discourse.group/t/latest-update/986/24 "2015-04-20T23:40:49Z")
…aaaaaaand boom. We are now all HTTPS, all the time. Probably. Unless I really screwed something up. The bigdino/cog web stack, for anyone curious, now looks like haproxy -\> varnish -\> nginx, with haproxy doing the SSL/TLS termination for everything. This lets me use varnish caching for ssl/tls. To REALLY go down the rabbit hole, Discourse adds like 2 more layers. haproxy -\> varnish -\> nginx -\> discourse nginx -\> discourse unicorn. /inception noise ---
**Author:** ![Nabiki](https://sea1.discourse-cdn.com/flex001/user_avatar/cog.discourse.group/nabiki/32/935_2.png) [@Nabiki](https://cog.discourse.group/u/Nabiki)\ **Post date:** [April 21, 2015, 1:33am UTC](https://cog.discourse.group/t/latest-update/986/25 "2015-04-21T01:33:25Z")
Seems to be working so far… 😉 ---
**Author:** ![Lee\_Ars](https://sea1.discourse-cdn.com/flex001/user_avatar/cog.discourse.group/lee_ars/32/2338_2.png) [@Lee\_Ars](https://cog.discourse.group/u/Lee_Ars)\ **Post date:** [April 21, 2015, 2:08am UTC](https://cog.discourse.group/t/latest-update/986/26 "2015-04-21T02:08:45Z")
Sometimes I can computer good! But sometimes I can not. ---
**Author:** ![Road\_Rash](https://sea1.discourse-cdn.com/flex001/user_avatar/cog.discourse.group/road_rash/32/147_2.png) [@Road\_Rash](https://cog.discourse.group/u/Road_Rash)\ **Post date:** [April 21, 2015, 11:06am UTC](https://cog.discourse.group/t/latest-update/986/27 "2015-04-21T11:06:28Z")
I’m just happy it’s fixed. I was going crazy having to manually scroll to the indicated number of new posts in a thread. Oh, the horror! 😃 ---
**Author:** ![Woodman](https://sea1.discourse-cdn.com/flex001/user_avatar/cog.discourse.group/woodman/32/24_2.png) [@Woodman](https://cog.discourse.group/u/Woodman)\ **Post date:** [April 21, 2015, 11:45am UTC](https://cog.discourse.group/t/latest-update/986/28 "2015-04-21T11:45:37Z")
If you hit the green button on the side it gave you the option of hitting “bottom” to go to the bottom. ---
**Author:** ![Road\_Rash](https://sea1.discourse-cdn.com/flex001/user_avatar/cog.discourse.group/road_rash/32/147_2.png) [@Road\_Rash](https://cog.discourse.group/u/Road_Rash)\ **Post date:** [April 21, 2015, 12:11pm UTC](https://cog.discourse.group/t/latest-update/986/29 "2015-04-21T12:11:51Z")
Yeah, I knew that but I had forgotten about it until a couple of days ago. ---
**Author:** ![Nabiki](https://sea1.discourse-cdn.com/flex001/user_avatar/cog.discourse.group/nabiki/32/935_2.png) [@Nabiki](https://cog.discourse.group/u/Nabiki)\ **Post date:** [April 21, 2015, 12:36pm UTC](https://cog.discourse.group/t/latest-update/986/30 "2015-04-21T12:36:46Z")
I did get an error from my tablet last night, however, saying that a secure connection couldn’t be established. I will have to try playing with some other browsers. ---
**Author:** ![Road\_Rash](https://sea1.discourse-cdn.com/flex001/user_avatar/cog.discourse.group/road_rash/32/147_2.png) [@Road\_Rash](https://cog.discourse.group/u/Road_Rash)\ **Post date:** [April 21, 2015, 12:48pm UTC](https://cog.discourse.group/t/latest-update/986/31 "2015-04-21T12:48:26Z")
The site is working fine using Chrome on my PC and Android phone. ---
**Author:** ![Lee\_Ars](https://sea1.discourse-cdn.com/flex001/user_avatar/cog.discourse.group/lee_ars/32/2338_2.png) [@Lee\_Ars](https://cog.discourse.group/u/Lee_Ars)\ **Post date:** [April 21, 2015, 1:26pm UTC](https://cog.discourse.group/t/latest-update/986/32 "2015-04-21T13:26:28Z")
> [@Nabiki](#): > > I did get an error from my tablet last night, however, saying that a secure connection couldn’t be established. I will have to try playing with some other browsers. I’m trying to be a responsible webmaster, so I pulled support for SSLv3 and TLS 1.0 in order to to be [POODLE](http://en.wikipedia.org/wiki/POODLE)-proof, and that means shutting the door on older browser/OS combos that don’t support TLS 1.1 or 1.2. Here’s the SSL Labs report showing what’s failing: In other words, upgrade your android tablet to 4.4 or later if it isn’t! ---
**Author:** ![ClockWorkXon](https://sea1.discourse-cdn.com/flex001/user_avatar/cog.discourse.group/clockworkxon/32/593_2.png) [@ClockWorkXon](https://cog.discourse.group/u/ClockWorkXon)\ **Post date:** [April 21, 2015, 4:04pm UTC](https://cog.discourse.group/t/latest-update/986/33 "2015-04-21T16:04:55Z")
> [@Lee\_Ars](#): > > In other words, upgrade your android tablet to 4.4 or later if it isn’t! Nice to know that before I try to access the site on my phone. (vers. 3.4.5 - no, not kidding) Interesting that is is failing the operating system and not the browser. ---
**Author:** ![RoadRunner](https://sea1.discourse-cdn.com/flex001/user_avatar/cog.discourse.group/roadrunner/32/63_2.png) [@RoadRunner](https://cog.discourse.group/u/RoadRunner)\ **Post date:** [April 21, 2015, 4:08pm UTC](https://cog.discourse.group/t/latest-update/986/34 "2015-04-21T16:08:20Z")
> [@ClockWorkXon](#): > > my phone. (vers. 3.4.5 I thought Android 3.x was for tablets only. As I recall, they didn’t merge the phone & tablet versions until v4. Maybe CWX is master haxor 😉😃 ---
**Author:** ![ClockWorkXon](https://sea1.discourse-cdn.com/flex001/user_avatar/cog.discourse.group/clockworkxon/32/593_2.png) [@ClockWorkXon](https://cog.discourse.group/u/ClockWorkXon)\ **Post date:** [April 21, 2015, 4:20pm UTC](https://cog.discourse.group/t/latest-update/986/35 "2015-04-21T16:20:35Z")
This is what I’ve got. ![](http://cog.discourse.group/uploads/cog/671/74590459234b27ff.png) ---
**Author:** ![dakboy](https://sea1.discourse-cdn.com/flex001/user_avatar/cog.discourse.group/dakboy/32/68_2.png) [@dakboy](https://cog.discourse.group/u/dakboy)\ **Post date:** [April 21, 2015, 4:26pm UTC](https://cog.discourse.group/t/latest-update/986/36 "2015-04-21T16:26:48Z")
Kernel version isn’t what matters, it’s the Firmware version (in your case; on other phones, it’s Android version and that’s a more correct way to refer to it). ---
**Author:** ![ClockWorkXon](https://sea1.discourse-cdn.com/flex001/user_avatar/cog.discourse.group/clockworkxon/32/593_2.png) [@ClockWorkXon](https://cog.discourse.group/u/ClockWorkXon)\ **Post date:** [April 21, 2015, 4:42pm UTC](https://cog.discourse.group/t/latest-update/986/37 "2015-04-21T16:42:21Z")
Okay, that’s odd. I would expect the opposite. ---
**Author:** ![RoadRunner](https://sea1.discourse-cdn.com/flex001/user_avatar/cog.discourse.group/roadrunner/32/63_2.png) [@RoadRunner](https://cog.discourse.group/u/RoadRunner)\ **Post date:** [April 21, 2015, 4:57pm UTC](https://cog.discourse.group/t/latest-update/986/38 "2015-04-21T16:57:50Z")
Oh, yeah, it does look misleading. And, since you’re at 4.2.2, you’re probably still going to get blocked. I do wonder, though, if you use Chrome or Firefox instead of the OS browser, will it still block you? Hmmm My primary phone is running 4.4.2, so I can’t test the theory. ---
**Author:** ![Lee\_Ars](https://sea1.discourse-cdn.com/flex001/user_avatar/cog.discourse.group/lee_ars/32/2338_2.png) [@Lee\_Ars](https://cog.discourse.group/u/Lee_Ars)\ **Post date:** [April 21, 2015, 5:46pm UTC](https://cog.discourse.group/t/latest-update/986/39 "2015-04-21T17:46:09Z")
> [@ClockWorkXon](#): > > Okay, that’s odd. I would expect the opposite. Right—firmware is what matters, because “firmware” == the actual Android operating system packages. The dependency that matters here is the version of OpenSSL that’s baked into the firmware, since OpenSSL is the component that the browsers lean on to do SSL/TLS. Typically switching to a different browser doesn’t matter because the browsers use the operating system’s libraries to provide SSL/TLS. Versions of OpenSSL with support for TLS 1.1 and 1.2 have been around for literally years, but they have dependencies and I suppose until Android 4.4 it wasn’t possible (or easy or otherwise practical) to pull a new OpenSSL version into the AOSP core. Bottom line, if you’re using a version of Android that allows TLS 1.0 ciphers (or, God help you, SSLv3 or lower), you’re vulnerable to being Man-In-The-Middle’d and having your personal information lifted directly off your phone by unskilled skript kiddies literally any time you use wifi. Upgrade now because your house isn’t just unlocked—you’ve put your valuables out on your lawn with a “Take what you want!” sign on them. tl;dr - everything is terrible, throw your electronics away and live in caves. ---
**Author:** ![ClockWorkXon](https://sea1.discourse-cdn.com/flex001/user_avatar/cog.discourse.group/clockworkxon/32/593_2.png) [@ClockWorkXon](https://cog.discourse.group/u/ClockWorkXon)\ **Post date:** [April 21, 2015, 6:05pm UTC](https://cog.discourse.group/t/latest-update/986/40 "2015-04-21T18:05:12Z")
If my carrier actually allowed upgrades, I would. And I don’t know enough to trust myself in “rooting” my phone. [Previous page](https://cog.discourse.group/t/latest-update/986.md?page=1) [Next page](https://cog.discourse.group/t/latest-update/986.md?page=3)