From mboxrd@z Thu Jan  1 00:00:00 1970
From: =?utf-8?B?5a6L5paH5q2m?= <iyzsong@gmail.com>
Subject: Re: Manage ssh public keys?
Date: Fri, 10 Apr 2015 17:28:18 +0800
Message-ID: <87wq1ks571.fsf@gmail.com>
References: <CANJQ5C70ZNtVtjZZ0G0TC1L2J3A254dpwpY2mECLCSxrNLmvyw@mail.gmail.com>
	<87oamxpl4o.fsf@gnu.org>
	<CANJQ5C7QR7PicV6ra1Lv6xoia=HtE7Adb4fSCJYxyganvS4maA@mail.gmail.com>
	<877ftlnlr1.fsf@gnu.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:42702)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <iyzsong@gmail.com>) id 1YgVEA-0004tb-9i
	for guix-devel@gnu.org; Fri, 10 Apr 2015 05:27:55 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <iyzsong@gmail.com>) id 1YgVE9-0007h0-Eo
	for guix-devel@gnu.org; Fri, 10 Apr 2015 05:27:54 -0400
In-Reply-To: <877ftlnlr1.fsf@gnu.org>
List-Id: "Development of GNU Guix and the GNU System distribution."
	<guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/guix-devel>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
Sender: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
To: Ludovic =?utf-8?Q?Court=C3=A8s?= <ludo@gnu.org>, Joe Hillenbrand <joehillen@gmail.com>
Cc: guix-devel@gnu.org

Ludovic Court=C3=A8s <ludo@gnu.org> writes:

> As discussed on IRC, there are several issues, such as the choice of the
> SSH implementation (lshd uses =E2=80=98lsh-authorize=E2=80=99 to add auth=
orized 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 =E2=80=98reconfigure=E2=80=99?  By j=
ust 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.

So users won't lost the changes they made.
>
> Ludo=E2=80=99.