Infrastructure nerd, gamer, and Lemmy.ca maintainer

  • 98 Posts
  • 1.39K Comments
Joined 2 years ago
cake
Cake day: June 22nd, 2023

help-circle









  • Shadow@lemmy.catoLinux@lemmy.worldSSH backdoor infection
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    15 days ago

    Most don’t create new keys per server machine but that’s not the issue. I don’t bother, I create a key per client machine on my side.

    Server gets compromised once, admin logs in and fixes it, admin logs in next time and the backdoor compromises it again.

    That’s all this is. If you can get in once, it’s a spot you can leave a backdoor that many admins will miss. That’s it.

    Admins don’t generally copy that whole file around, they usually copy and paste the lines they want. Also I generally copy and paste it from my workstation, not another server.



  • Shadow@lemmy.catoLinux@lemmy.worldSSH backdoor infection
    link
    fedilink
    English
    arrow-up
    15
    arrow-down
    1
    ·
    edit-2
    16 days ago

    If your hosting is a bad actor, you’re screwed no matter what. Why bother with this when they have direct access to your disk and ram

    You could turn off authorized key files, or lock them down. This isn’t really a big security risk though, there’s countless ways to backdoor a system once you have access to do this.

    This just targets a remote account, not your local pc.