[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Putting a file into system image ~user/ but not on reconfigure

From: Hartmut Goebel
Subject: Re: Putting a file into system image ~user/ but not on reconfigure
Date: Thu, 17 Aug 2023 21:30:24 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.12.0

Hello Efraim,

Am 13.08.23 um 16:58 schrieb Efraim Flashner:
I feel compelled to ask if the key must be in
~vagrant/.ssh/authorized_keys or if /etc/ssh/authorized_keys.d/vagrant
is acceptable.

I'm afraid it needs to be in ~vagrant/.ssh/authorized_keys: When first booting the machine, Vagrant logs into it and replaces the key. Thus the user vagrant must be allowed to change the respective file.

Why are you asking? What would be easier (in respect of not re-installing the key), if putting the key into /etc/ssh/authorized_keys.d/vagrant would work?

Also, could you use /etc/services or another file in /etc/static as a
marker that the system has been booted at least once before?

Such a marker would be okay. Anyhow to make this work, some respective new service would need to detect this quite early, before /etc/service gets linked. Otherwise the service could not distinguish between "first" and "at least once"- Or did I misse something?

Is there some means of ordering service execution/start?

Hartmut Goebel

| Hartmut Goebel          |                |
|  | compilers which you thought are impossible |

reply via email to

[Prev in Thread] Current Thread [Next in Thread]