-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Install openssh-server by default #31
Comments
My initial motivation of the whole disk how-to was to provide a streamline alternative to zfs ubuntu wiki, that seemed to loose focus on the zfs setup. SSH seemed like one of those extraneous steps not REALLY related to rpool creation that was easy enough for a knowledgeable person wanting this service to adlib. But since this has been scripted, it is harder to go "off-script" and not doing this "optional step" could render a system inaccessible after reboot. So, it sounds like a good idea for the script. However, this will be complicated when I wrap in native encryption. In order to have ssh start early enough to allow passphrase entry, some additional steps will need to be done. I'll need to do more searching into the best way to do this, but top google result makes it look possible. While we are accommodating this service, please create additional issues for other services that need to be considered prior to dataset export and livecd reboot that would hinder access to system after initial reboot. |
thanks for the extensive answer! I totally agree with you. We shouldn't strive to bloat your script. Maybe the SSH server could (for now) just be mentioned in the README as "suggested next steps".
Wdyt? |
Notifications would be a good stopgap measure. I was contemplating having a selection for the existing freeform (with defaults) entries and a guided (with explanations) option-by-option mode. I think this could go a long way to educating within the script. |
Not sure about your intended use case but it might be reasonable to automatically or optionally install and activate an SSH server.
The text was updated successfully, but these errors were encountered: