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

help-circle

  • Just a simple hole renders them useless. The only method to reconstruct them from there would be any kind of SEM or AFM which would still take weeks to months to years depending on the size/density of the drives.

    Even just opening them up and smacking the disks would be sufficient

    Next time just encrypt them.


  • ShortN0te@lemmy.mltoSelfhosted@lemmy.worldLatest Watchtower fork?
    link
    fedilink
    English
    arrow-up
    4
    ·
    edit-2
    1 month ago

    Just because there is no update does not mean there are security vulnerabilities to worry about, or do you have a specific one that is not fixed?

    The attack vector seems very narrow to me. It checks the container registry downloads the containers and runs some docker commands.

    It has no interface, so in order to attack it you either have to compromise the container registry (but then it would be easier to compromise the containers you download) the secure connection used to download the containers (https is quite stable) or something on the server side.

    Also the project does not really look that abundant to me.

    EDIT: So i have not checked this, but watchtower is probably using docker for most steps anyway? So basically the only thing that could be attacked is via the notifications watchtower is sending?




  • Most critical infrastructure like my mail i subscribe to the release and blog rss feed. My OSs send me Update notifications via Mail (apticron), those i handle manual. Everything else auto updates daily.

    You still need to check if the software you use is still maintained and receives security updates. This is mostly done by choosing popular and community drive options, since those are less likely to get abandoned.






  • Just subscribe to the release channel. That varies from OS to OS or Software, but is worth it.

    Use tools that are universal. For example, I have not used TrueNAS Scale because they did not support native docker at the time. OS specific solutions are more likely to break then universal once (truecharts vs docker)

    To get up and running again after a complete failure i can just download the latest config and data from my backup and set up any distro that supports docker and my system is running again.

    I do OS upgrades when they are available, usually within 1 or 2 days and containers are updated with watchtower daily.



  • Immich requires to be run on a server to function, but a lot of (or even all) of its functions are things that could reasonably done entirely on-device. Aves combined with some automatic backup solution such as Nextcloud gets (from what I can tell) most of the functionality Immich offers.

    How would you backup Immich on device?

    And if you backup to Nextcloud than you already have a served?

    So you are arguing that having a file server is enough? And processing is done on client side?

    That would be in this case very inefficient.

    1. You would need to have all the data on the Client or transfer all the data to the client once you load it.
    2. You device has to do all the processing which would lead to lower battery life.
    3. How do you handle multiple Users? Giving partially access to the Filesystem?

    I could come up with other points but this should give you an idea. Yes, for some use cases a server-client approach does not make sense but for a dedicated photo backup and indexer it absolutely does.