• 4 Posts
  • 602 Comments
Joined 2 years ago
cake
Cake day: August 11th, 2023

help-circle

  • Rice cooker with a scheduable cooker. I can get it ready the night before or right before i need. Then i take some of it and throw it in the fridge to have it ready for fried rice through out the week. The rest I chow with sauerkraut throught the day.

    I try to do laundry every day, easier to match and put stuff away. I hang every thing besides socks witch can be stuff in a drawer or bag.

    Ive been trying to move to more fermented, shelf stable or frozen foods too. Just to reduce the complixity of tracking when stuff is going bad as much.

    I’ve been slowly moving the yard to a food forest managment style. This has been a lot of help personally too. So it gets wild its ok, i pick what i want when it makes sense or process stuff like apples when if I have free time and theyre ready, but its no loss to just put them in a pile to fertilize.














  • They are basically the exclusive target for GrapheneOS for their feature set:

    Non-exhaustive list of requirements for future devices, which are standards met or exceeded by current Pixel devices:
    
        Support for using alternate operating systems including full hardware security functionality
        Complete monthly Android Security Bulletin patches without any regular delays longer than a week for device support code (firmware, drivers and HALs)
        At least 5 years of updates from launch for device support code with phones (Pixels now have 7) and 7 years with tablets
        Device support code updated to new monthly, quarterly and yearly releases of AOSP within several months to provide new security improvements (Pixels receive these in the month they're released)
        Linux 6.1, 6.6 or 6.12 Generic Kernel Image (GKI) support
        Hardware accelerated virtualization usable by GrapheneOS (ideally pKVM to match Pixels but another usable implementation may be acceptable)
        Hardware memory tagging (ARM MTE or equivalent)
        Hardware-based coarse grained Control Flow Integrity (CFI) for baseline coverage where type-based CFI isn't used or can't be deployed (BTI/PAC, CET IBT or equivalent)
        PXN, SMEP or equivalent
        PAN, SMAP or equivalent
        Isolated radios (cellular, Wi-Fi, Bluetooth, NFC, etc.), GPU, SSD, media encode / decode, image processor and other components
        Support for A/B updates of both the firmware and OS images with automatic rollback if the initial boot fails one or more times
        Verified boot with rollback protection for firmware
        Verified boot with rollback protection for the OS (Android Verified Boot)
        Verified boot key fingerprint for yellow boot state displayed with a secure hash (non-truncated SHA-256 or better)
        StrongBox keystore provided by secure element
        Hardware key attestation support for the StrongBox keystore
        Attest key support for hardware key attestation to provide pinning support
        Weaver disk encryption key derivation throttling provided by secure element
        Insider attack resistance for updates to the secure element (Owner user authentication required before updates are accepted)
        Inline disk encryption acceleration with wrapped key support
        64-bit-only device support code
        Wi-Fi anonymity support including MAC address randomization, probe sequence number randomization and no other leaked identifiers
        Support for disabling USB data and also USB as a whole at a hardware level in the USB controller
        Reset attack mitigation for firmware-based boot modes such as fastboot mode zeroing memory left over from the OS and delaying opening up attack surface such as USB functionality until that's completed
        Debugging features such as JTAG or serial debugging must be inaccessible while the device is locked
    

    From https://grapheneos.org/faq#device-support






  • Definitely overkill lol. But I like it. Haven’t found a more complete solutions that doesn’t feel like a comp sci dissertation yet.

    The goal is pretty simple. Make as much as possible, helm values, k8s manifests, tofu, ansible, cloud init as possible and in that order of preference because as you go up the stack you get more state management for “free”. Stick that in git and test and deploy from that source as much as possible. Everything else is just about getting to there as fast as possible, and keeping the 3-2-1 rule alive and well for it all (3 backups, 2 different media, 1 off-site).