• 9 Posts
  • 26 Comments
Joined 2 years ago
cake
Cake day: June 18th, 2023

help-circle






  • I don’t think is is a backdoor. At the moment I wouldn’t consider this article any more than FUD.

    It’s unclear to me if the security company has actually said what the vuln is or not, but if it’s what was presented in the slides linked in the article this is at worst something that can be “attacked” from a computer connected via USB (and I’m pretty sure it would also require special software already on the ESP32), where the attack is sending out possibly invalid bluetooth messages to try to attack other devices or flashing new firmware to the ESP itself. It’s not a general “backdoor” in the ESP32 itself. At least that’s the best interpretation I’ve been able to make. Happy to be corrected if anyone finds more info.





  • I am still interested to know the details of how they came to this decision. Why Signal instead of Matrix.

    AFAIK, signal doesn’t federate, There is no “signal server-to-server” protocol. When people say “The Signal Protocol”, they are talking about a cryptographic protocol, not a network protocol.

    As for why they wouldn’t use Matrix, I would assume it’s just too heavy of a protocol for the scale they operate at. IIRC, Matrix isn’t just a chat protocol. It’s a multi-peer cryptographic state synchronization protocol. Chat is (was?) just the first “easy” application they were going to apply it to. (Now I’m curious if they still have plans for that at some point.) They’ve been making great strides in improving the efficiency, at least in the client-server API (I haven’t been paying attention to the server-server API at all), but it’s still going to be a heck of a lot more compute heavy than whatever custom API they’re providing.






  • IMO, yes. Docker (or at least OCI containers) aren’t going anywhere. Though one big warning to start with, as a sysadmin, you’re going to be absolutely aghast at the security practices that most docker tutorials suggest. Just know that it’s really not that hard to do things right (for the most part[1]).

    I personally suggest using rootless podman with docker-compose via the podman-system-service.

    Podman re-implements the docker cli using the system namespacing (etc.) features directly instead of through a daemon that runs as root. (You can run the docker daemon rootless, but it clearly wasn’t designed for it and it just creates way more headaches.) The Podman System Service re-implements the docker daemon’s UDS API which allows real Docker Compose to run without the docker-daemon.


    1. If anyone can tell me how to set SELinux labels such that both a container and a samba server can have access, I could fix my last remaining major headache. ↩︎









  • That’s not really possible with docker TBH, and I say that as a diehard Podman advocate. Docker, the tooling that you install with your package manager, is open source. Sure they have windows and mac desktop stuff that isn’t open, but it’s not like you’re self-hosting with that, right?

    Plus there’s always Podman to switch to, which can be a (mostly) drop-in replacement, if you want something with a more trustworthy provenience.