Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

5
  • 2
    I don't quite understand the reason for moving around with private keys. It should be sufficient to copy the public key of you on the client machine to the server as authorized key for the root server, right? Commented Dec 2, 2012 at 18:11
  • I'm sure it's possible to create the key pair on the client machine and only move the public key from there to the server, but if I recall correctly I think there were some problems finding a format that BusyBox would accept. So reusing the keys that were already on the server was the only option I got working. Commented Dec 4, 2012 at 9:04
  • 1
    Any idea what I should do to get this working on Arch Linux? Commented Feb 9, 2014 at 6:17
  • 1
    @Gerhman Check out the dropbear_initrd_encrypt package in the AUR for early-ssh support on Archlinux. Commented Feb 3, 2015 at 10:27
  • 1
    @Gerhman archwiki page: Remote unlocking of the root or other partition Haven't done it yet, but it looks interesting. Will have to check it out :) Commented Mar 7, 2015 at 20:47