Just a geek, finding my way in the fediverse.

  • 3 Posts
  • 40 Comments
Joined 2 years ago
cake
Cake day: June 11th, 2023

help-circle



  • clif@lemmy.worldtoSelfhosted@lemmy.worldAWS is having a bad day
    link
    fedilink
    English
    arrow-up
    13
    ·
    edit-2
    8 days ago

    One of our client support people told an angry client to open a Jira with urgent priority and we’d get right on it.

    … the client support person knew full well that Jira was down too : D

    At least, I think they knew. Either way, not shit we could do about it for that particular region until AWS fixed things.




  • I’d imagine that if you have physical access and don’t mind plugging in a USB then that’s the easier route.

    My personal goal is to be able to unlock it remotely in two main scenarios :

    1. I’m lazy and don’t want to have to awkwardly fumble at plugging in something. So, SSH to it from the same room and unlock it from my desktop.
    2. Server got rebooted while I’m away from home but I would really like it to be up and running again for something I need but I don’t have physical access at the time.

    Both of those situations lean towards a remote unlock with no USB. The first one is absolutely doable because I have local access and could plug a device in, it’s just awkward. On the second, physical access is impossible so it must be done remotely.

    I mentioned it in another comment but the remote unlock while away from home presents extra challenges for me because I access my server externally via Tailscale. Since Tailscale isn’t available at boot (pre-decrypt), then I’ll have to tailnet+ssh to another machine on the LAN (that doesn’t require a boot password/unlock) and then SSH from that machine to the server to enter the LUKS password to allow boot to continue. Sounds feasible, though perhaps a little clunky. That’s my current plan and hoping to try it out this weekend if time permits.



  • If I’m reading the docs correctly, Clevis can rely on a separate Tang server for retrieving the decryption key, right? So in that scenario I’d need to have another machine for Tang that can also auto-boot without entering a boot/LUKS password. Otherwise, if both machines (server+clevis and Tang server) were in the same room and restarted due to power loss, neither would be able to boot if both were encrypted… or did I misunderstand something important?

    And I don’t think I actually want “automatic” unlocking. I just want to be perform the unlock (enter LUKS password) remotely. I realize that comes with manual intervention (entering the password remotely) but I’m okay with that. I should probably have clarified that by “home server” I mean a machine the serves nice to have stuff, nothing mission critical. Plus I’m really the only one who uses it currently so I’ll notice it’s down when something doesn’t work and can then initiate the remote unlock/boot : D

    Clevis is interesting but I don’t think it matches my specific situation. Glad I know about it now though, thanks for the info.



  • This is interesting, another one I hadn’t heard of yet. And, the server is running Debian : )

    I enjoy the intro too :

    You know how it is. You’ve heard of it happening. The Man comes and takes away your servers, your friends’ servers, the servers of everybody in the same hosting facility. The servers of their neighbors, and their neighbors’ friends. The servers of people who owe them money. And like that, they’re gone. And you doubt you’ll ever see them again. That is why your servers have encrypted root file systems












  • Mine are named after the penguins from the Madagascar movie : Skipper, Private, Kowalski, and Rico.

    Unfortunately there’s only four so I often supplement with a suffix. For example, I’ve got an old windows laptop kicking around that is “rico-w”

    … I should really commit to a naming scheme with a wider array of options.