depenguin-me / depenguin-installer Goto Github PK

The following forks have code committed which may be useful in improving this fork.

• mmatuska/mfsbsd@master...azet:trusted-mfsbsd:master
• mmatuska/mfsbsd@master...BadRabbitCode:mfsbsd:master
• mmatuska/mfsbsd@master...bjoernfan:mfsbsd:master
• mmatuska/mfsbsd@master...corv89:mfsbsd:master
• mmatuska/mfsbsd@master...DavMig:mfsbsd:master
• mmatuska/mfsbsd@master...hybridlogic:mfsbsd:master
• mmatuska/mfsbsd@master...johnko:mfsbsd:master
• mmatuska/mfsbsd@master...KaanUz:mfsbsd:master
• mmatuska/mfsbsd@master...MerlinDMC:mfsbsd-mibe:mibe
• mmatuska/mfsbsd@master...NJoyX:mfsbsd:master
• mmatuska/mfsbsd@master...Pricetx:mfsbsd:master
• mmatuska/mfsbsd@master...skunkwerks:mfsbsd:master
• mmatuska/mfsbsd@master...theforeman:mfsbsd:foreman
• mmatuska/mfsbsd@master...TritonDataCenter:mfsbsd:master
• mmatuska/mfsbsd@master...Unity-Technologies:mfsbsd:master

It would be nice if this fork included options for Vagrant, importing ssh authorized_keys on first boot, setting IP access etc

It might make sense to maintain this more as a consumer of mfsbsd instead of a fork. This would mean that we store custom configs and the scriptwork required to build the mfsbsd images here (probably locked to a specific upstream commit we can then adjust as we evolve with mfsbsd). This would allow to keep this very small and avoid constant merging/rebasing. It would also force us to get required changes in mfsbsd into upstream over time (while we can also patch locally to bridge gaps).

Currently an image can be built by adding conf/authorized_keys with a public key for access.

However, a new image needs to be built for different users. Or updated keys.

How can this be fixed in customfiles or customscripts to append the pubkey from the rescue system, or a web link, as the install ISO is booting?

i.e. we don't want to add keys then build, rather we want to build and retrieve keys as part of boot process.

For hetzner it may be possible to retrieve keys with

curl --netrc-file /path/to/credentials https://robot-ws.your-server.de/key

and incorporate this somehow, but then the credentials file has to be included in the build step.

It would be better to do a combination of

• add vagrant key to authorized_keys
• append user(s) keys to authorized_keys with fetch http://my.host/keys.txt -o /tmp/authorized_keys && cat /tmp/authorized_keys >> /root/.ssh/authorized_keys