Re: Manage ssh public keys?

[David Thompson]

Ludovic Courtès <address@hidden> writes:

> 宋文武 <address@hidden> skribis:
>
>> Ludovic Courtès <address@hidden> 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.

+1

-- 
David Thompson
Web Developer - Free Software Foundation - http://fsf.org
GPG Key: 0FF1D807
Support the FSF: https://fsf.org/donate