• The Doctor@beehaw.org
      link
      fedilink
      arrow-up
      4
      ·
      1 year ago

      The drive wasn’t encrypted, a not-encrypted database dump was on the laptop when the raid happened. It might have had to do with gearing up for the Mastodon update that caused us a lot of grief across Fedi a couple of weeks back. Or it could have been database server debugging; the timing was incredibly bad.

      • dan@upvote.au
        link
        fedilink
        arrow-up
        2
        ·
        edit-2
        1 year ago

        But if the drive wasn’t encrypted, how is it “would be encrypted material”?

        I’m surprised that people are hosting Mastodon servers without full disk encryption given the overhead isn’t significant plus the fact that people have private messages in the DB.

        • wim@lemmy.sdf.org
          link
          fedilink
          arrow-up
          3
          ·
          1 year ago

          Just FYI, when your drive is encrypted, and the system is up and running, the keys for the encryption are in memory and thus recoverable. And even if they were magically protected by something like SGX or a some secure enclave, you can still interact with the machine and the filesystem while it is running.

          So full disk encryption is NOT a silver bullet to data protection when being raided.

          • Butters@lemmywinks.com
            link
            fedilink
            arrow-up
            2
            ·
            1 year ago

            Right, and then these comments about “encrypted database” the server application needs to be able to access that data, so it will have the key in its config somewhere right?

          • algebro@algebro.xyz
            link
            fedilink
            arrow-up
            1
            ·
            edit-2
            1 year ago

            AFAIK it’s not that easy to access data on the machine while it’s running unless they can bypass the lock screen. People pick stupid passwords for their user accounts so it’s totally possible to get in in those cases, but otherwise dont you need really sophisticated side channel attacks to get data out of memory on locked system? It’s not like there is some port on the MOBO you can just plug into to get access to RAM

            • HumbleFlamingo@beehaw.org
              link
              fedilink
              arrow-up
              1
              ·
              1 year ago

              I did some work on this a decade or so ago in college. Data stays in memory a lot longer than you’d think at room temp, like minutes, not seconds. If you spray the modules down with an upside down compressed air can, you have plenty of time to remove it, and plug it into some that can dump it to persistent storage.

          • dan@upvote.au
            link
            fedilink
            arrow-up
            1
            ·
            1 year ago

            Yeah I didn’t realise they’d capture the memory. I though they just unplug the server and take it.

            You could potentially have something that recognizes that the server is being tampered with and automatically shuts it down.

        • Em Adespoton@lemmy.ca
          link
          fedilink
          arrow-up
          1
          ·
          1 year ago

          The DB itself is encrypted (usually).

          And FDE wouldn’t have helped if the disk was currently mounted and the admin logged in; LEO attempts to preserve things as they are, they don’t just unplug the hardware and walk away with it.

          • dan@upvote.au
            link
            fedilink
            arrow-up
            3
            ·
            1 year ago

            The DB itself is encrypted (usually).

            Which DBs support encryption? Genuinely curious, since I usually use full-disk encryption and so often don’t have a need to configure encryption in individual services.

            they don’t just unplug the hardware and walk away with it.

            Huh, I thought that’s exactly what they do during a raid. TIL.