• 1 Post
  • 250 Comments
Joined 3 years ago
cake
Cake day: June 30th, 2023

help-circle


    • 4 nm Snapdragon® 8 Gen 3 - ARM64
    • 16GB Unified LPDDR5X RAM
    • 256GB UFS storage, microSD card slot
    • Rechargeable 21.6 Wh Li-ion battery
    • 2160 x 2160 LCD (per eye)
    • 72-144Hz refresh rate (144Hz experimental)
    • Inside-out camera based tracking
    • Headset: Wi-Fi 7, 2x2, Dual Radios
    • Wireless Adapter Included (Wi-Fi 6E)
    • Bluetooth 5.4
    • Dual speaker drivers per ear, dual microphone array
    • SteamOS 3
    • Steam Frame Controllers – full 6-DOF and gamepad controls
    • Half-Life: Alyx included

    …so, how come the phone costs twice as much as the steam frame?












  • My devs prefer Docker, and don’t want Kubernetes! We have a fix for that: Portainer-D2K. Portainer-D2K is a Docker translator for Kubernetes

    As someone who was using mostly podman and is now switching to kubernetes I can confidently say that the cli interface was not what was holding me back. Instead it was the sheer amount of setup and complexity kubernetes can bring into an environment. Kubernetes is great when you want most or all the features it offers, it is horrible if you want to deploy 3 containers for your application on one host.

    Oh well, not like I have to care, I wasn’t interested in portainer to begin with.







  • There exists shims that are signed by Microsoft and were not revoked. Normally this would be fine but these shims had weaknesses that allowes hackers to load any code using them. Normally the shims should only run other signed/trusted code. These vulnerable shims can be used to bypass secure boot by replacing your existing bootloader with the shim and then running rootkits/hackerOS/whatever and bypass bitlocker using TPM or just running a level 0 virus that can’t be detected by the OS on any PC which trusts Microsoft’s keys (99% of all PCs)

    To prevent this you’d have to not trust the vulnerable shims by either adding them manually to the exclusions list or using your own secure boot keys which would only trust the few bootloader files your pc uses and no other files.

    Worst case: it behaves as if secure boot wasn’t on. Without secure boot you wouldn’t need this exploit cause then you can replace the bootloader with whatever you want anyways. With or without secure boot you need administrative permission to replace the bootloader so this is only an issue after your PC is already compromised or if someone had physical access to your PC.