• 0 Posts
  • 66 Comments
Joined 3 years ago
cake
Cake day: June 16th, 2023

help-circle


  • Most of my infra is Debian, and I did it without serious incident:

    #Update everything to latest
    apt update && apt upgrade && apt full-upgrade && apt --purge autoremove
    reboot
    
    #Verify that debian_version is 12.x (STOP IF NOT 12!)
    cat /etc/debian_version
    
    #Check for any pinned or held packages
    apt list '?narrow(?installed, ?not(?origin(Debian)))'
    apt-mark showhold
    
    #Swap bookworm for trixie in repo files
    sed -i 's/bookworm/trixie/g' /etc/apt/sources.list
    sed -i 's/bookworm/trixie/g' /etc/apt/sources.list.d/*
    
    #Carry out update
    apt update
    apt upgrade --without-new-pkgs -y
    apt full-upgrade -y
    reboot
    
    #Verify that debian_version is 13.x
    cat /etc/debian_version
    
    #Modernize apt sources to v3
    apt modernize-sources -y
    

    And then maybe apt update to make sure the updates still work OK.

    Sometimes you have to make changes to certain repos that don’t have Trixie manifests, but that’s easy enough to roll back.




  • Sure, that may be true. But I am not an international lawyer, so I can’t really speak to that point.

    CVEs should be taken with an approach that the cve does matter, but that adding your own exposure to it is the only way to measure its impact on you.

    This is a PXE boot environment vuln, so most of the self-hosting community itself probably doesn’t have this enabled at all. A person who does is likely very aware that PXE is already dangerously easy to misconfigure, especially in the days of remote init methods over https, which can at least be layered with other security solutions.










  • Your said you were going to use the cloud services, so even if you self-host, using a cloud service api carries the same risk as using their apps. This is an app to unify all the remote storage things.

    However, after looking at the code, I retract my comment and caution you not to use Drivebase:

    [crypto]
    # Generate: openssl rand -base64 32
    masterKeyBase64 = "<base64-encoded-32-byte-key>"
    

    If this is a salt or a seed, the documentation is wrong. But it looks like they’re using this base64 value as the actual key for whatever encryption Claude has vibe-coded into it.

    base64 values can be reversed very trivially.

    Don’t use this.



  • Pirate library

    Sure, yes. Acknowledged.

    It is true that the referenced information is present in libgen, but it is not succinctly summarized for consumption, and that is the function Wikipedia fulfills for most users.

    I can understand the pitfalls of allowing updates from the public, but I think it’s widely accepted that Wikipedia does more good than bad.

    It’s really difficult to understand your point of view on this, especially when you indulge in semantics arguments.