Hacker Newsnew | past | comments | ask | show | jobs | submit | rew0rk's commentslogin

either you used http, self signed if you did not mind the warning, and i remember there being one company that did offer free certificates that validated, but cant remember the name of it


> i remember there being one company that did offer free certificates that validated, but cant remember the name of it

You're probably thinking of StartSSL, and it was a bit of a pain to get it done.


I believe it was StartSSL and/or WoSign back then


While the information leakage/disclosure is a big issue, It feels like its still a big jump to get users to install off-Play Store APKs?


Considering there was a whole hubbub starting from late Aug 2025 RE: Certification of ALL Android apps/.apks: https://android-developers.googleblog.com/2025/08/elevating-...

Followed by a partial walk-back from Google in mid Nov 2025: https://android-developers.googleblog.com/2025/11/android-de...

I would say there is a substantial amount of users willing to install off-play Store .APKs. Substantial enough they're also willing to take a 'jump' and accept the risks/errors displayed


Does this mean that MagSafe-like magnetic connectors can/will be more common out there?


Before the GCP Console stopped loading, it looks like they were pushing an update to all my nodes in kubernetes engine


> Available until December 31, 2023

Meaning that controllers that have the old firmware will be unable to switch after that date? This seems like a weird restriction to have if this is a firmware update?


I assume it requires something hosted, and can't be open sourced due to licensing restrictions*. Hopefully it can be reverse engineered.

*I've heard from firmware engineers inside and outside of Google that licensing is the biggest reason why stuff isn't open sourced.


I mean, that's absolutely true for Android hardware. If MediaTek or Qualcomm or any other supplier for the various parts open sourced their drivers we would be able to port any new version of AOSP to basically everything that has enough juice to run it and then some.

Unfortunately these companies control the drivers and have the strictest licenses imaginable, so even companies like Samsung or Google can only offer updates as long as their suppliers allow them, after that it's just waiting for the ABI to break and the old drivers to stop working


I am beyond grateful for Bluetooth functionality on a free controller, but the greedy part of me was half-hoping Google would unlock the device and open source the gamepad-over-ip code. My wish is selfish: I wasn't play Steam games that are on a gaming PC in a different room to my TV, the PC is well outside of bluetooth range, but both areas have WiFi coverage. I acknowledge that this is a first-world problem, but regardless, I hope someone will be able to reverse-engineer the firmware and come up with an open-version.


Presumably there's some server side component that Google wants to turn off


Maybe a code signing certificate (or some boot ticket signing backend) for the firmware will expire at that date?


It's all part of the gamepads-as-a-service business plan :P


Google must kill everything. EVERYTHING.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: