Re: Manage ssh public keys?

[ludo@gnu.org (Ludovic Courtès)]

宋文武 <iyzsong@gmail.com> skribis:

> Ludovic Courtès <ludo@gnu.org> writes:
>
>> As discussed on IRC, there are several issues, such as the choice of the
>> SSH implementation (lshd uses ‘lsh-authorize’ to add authorized keys,
>> not ~/.ssh/authorized_keys.)  That complicates things.
>>
>> However, as David suggests, we could have a per-account list of files to
>> install.  I can imagine something like:
>>
>>   (user-account
>>     (name "joe")
>>     ;; ...
>>     (files `((".ssh/authorized_keys" ,(local-file "my-authorized-keys"))
>>              (".emacs.d/foo.el" ,(local-file "foo.el")))))
>>
>> Now, how should that be handled upon ‘reconfigure’?  By just overriding
>> those files?  Probably, I guess.
>>
>> Also, should they be symlinks to the store or copies?
> How about use symlinks, but:
>   - create them if they are not exists.
>   - update them if they are symlinks to /gnu/store.
>   - warn and do nothing about them if they aren't symlinks to store.

The problem is that that would be stateful, and thus not reproducible.
So I think conditionals like this are not desirable.

Ludo’.