The 8232 Project

I trust code more than politics.

  • 76 Posts
  • 464 Comments
Joined 1 year ago
cake
Cake day: February 25th, 2024

help-circle
  • There are plenty of options:

    • You can carry around a spare burner phone that is powered off. These are relatively cheap ($30 + the cost of your cell plan), and has the benefit of working even when your main phone dies. You can leave it charging in your car.
    • You can carry around a cellular hotspot, such as one from the Calyx Institute. This also helps fund a pro-privacy organization, and this hotspot can be used to provide internet for multiple devices. See this video for more information.
    • You can still call emergency services even without a SIM card.
    • If there are public Wi-Fi networks nearby, you can connect to those in order to get in touch with people you need.
    • You can ask anyone nearby for help. Whether it be borrowing their phone to make a phone call, using their phone as a hotspot, or having them help you directly.
    • Hike to the nearest civilization for help.
    • Wait for a bus to pass by, if they are in your area.
    • Some smart cars have the option to call for help built-in.
    • Use GrapheneOS with a carrier. It will still be much more private than using iOS, and you can disable the cellular radios when they are not in use by enabling Airplane Mode.

    Even without any of those, the chances that you will be completely stranded with no one to help and no way to call emergency services are very, very slim. Privacy protects you from more likely scenarios, such as data breaches or identity theft.



  • secureblue has native support for containers, although it uses the more modern Distrobox rather than Toolbx. I tried installing VSCodium in this way, but I couldn’t get it to start due to some windowing system issue. Even if I could, it comes at the cost of security. Firstly, user namespaces need to be enabled. Secondly, the app would have less granular permission control (e.g. full access to the home directory). For those reasons, it’s better to avoid using containers unless explicitly required. This method works fine, so there’s no need.


  • This guide is actually only 3 steps:

    1. Install VSCodium
    2. Install the Rust SDK
    3. Enable permissions

    The rest is just extras, like installing rust-analyzer, which you would need to do on any distribution. The reason it’s so long is because I wanted to make it painstakingly simple for anyone to be able to do it, regardless of using the command-line, user-interface, mouse, or keyboard. Depending on how hardened you’ve made your secureblue system, you really could just install everything with one command:

    flatpak install -y com.vscodium.codium org.freedesktop.Sdk.Extension.rust-stable/x86_64/24.08 && flatpak override -u --env=FLATPAK_ENABLE_SDK_EXT=rust-stable com.vscodium.codium
    

    secureblue isn’t designed to be fast, easy, or simple. It’s designed to be secure.

    Hope this helps!





  • Both of which also appear (looking at this on mobile) to require compiling by the user.

    Vanadium comes preinstalled on GrapheneOS, and Trivalent comes preinstalled on Trivalent. Compatible Linux distros can add the Trivalent repo to install it without building.

    Show me something Windows based that can be as secure as LibreWolf along with the appropriate extensions for blocking ads, fingerprinting, CDNs, and other spyware-like content.

    LibreWolf is far from secure, as it is based on Firefox and so comes with the same security issues. If you meant to say privacy and not security, the reason nobody makes high threat model browsers for Windows is because Windows itself is not private and it would be a losing battle.








  • An issue arises with that. Linux is fundamentally insecure, as you are likely well aware if you use secureblue. secureblue is designed to be as secure as possible while still being Linux, and so is still bound by the same constraints. Qubes OS is not a distro, so it (should be) more secure, but it is an absolute pain to use. Furthermore, Qubes OS emulates Linux distros, so the question becomes “Why not just emulate the most secure Linux distro?” which is either Whonix or secureblue depending on who you ask. Is that more secure than running secureblue on bare metal? What about GrapheneOS used in desktop mode? And what about emulating Linux inside of GrapheneOS using the Linux terminal? There are plans to use multiple distros inside of the terminal, so what about secureblue inside of GrapheneOS?

    The whole situation spirals out of control. I know this iceberg chart isn’t ranking security, it’s ranking what software people generally use for each experience level, but neither secureblue nor Qubes OS would fit nicely in any category. You can read this post for more of my thoughts about this mess.