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

help-circle


  • LUKS may not make your server meaningfully more secure. Anyone who can snapshot your server while it’s running or modify your unencrypted kernel or initrd files before you next unlock the server will be able to access your files.

    This is a little oversimplified. Hardware vendors have done a lot of work in the last 10-20 years to make it hard to impossible to obtain data this way. AMD-SEV for example.

    There are other more realistic attacks like simply etrackt the ssh server signature and MITM the ssh connection and extract the LUKS password.







  • It is less intuitive to set up, but it is extremely lightweight and very fast. That is the one I recommend.

    I highly question the decision process to only include the lightweight and speed. There are much more important criterias to consider, like for example stability, maintainability, support etc.

    I do not need yet another service that gets abonded 1-2 years after launch or goes subscription only etc.


  • While lots of ppl will hate on Nextcloud, its pretty good. When you do the setup right, with cache and so on set up it’s fast and serves its purpose not only as cloud storage but as a collaboration platform where you can edit files with other ppl and much more.

    If you only want a simple Web App to up and download files there are probably other solutions for that.



  • To achieve a compromised update you either need to compromise the update infrastructure AND the key or the infratstructure AND exploit the local updater to accept the invalid or forged signature.

    As i said, to compromise a signature checked update over the internet you need to compromise both, the distributing infrastructure AND the key. With just either one its not possible. (Ignoring flaws in the code ofc)