[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug#38478] [PATCH 4/4] machine: ssh: <machine-ssh-configuration> can in
From: |
Ludovic Courtès |
Subject: |
[bug#38478] [PATCH 4/4] machine: ssh: <machine-ssh-configuration> can include the host key. |
Date: |
Sat, 07 Dec 2019 01:04:42 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux) |
Ludovic Courtès <address@hidden> skribis:
> address@hidden (Jakob L. Kreuze) skribis:
>
>> Ludovic Courtès <address@hidden> writes:
>
> [...]
>
>>> BTW, I’m wondering if we should go further and deprecate missing/#f
>>> ‘host-key’ fields altogether. WDYT?
>>>
>>> To me it just seems wiser to have that info within the deploy config
>>> rather than out-of-band in ~/.ssh/known_hosts.
>>
>> I feel that's more in-line with the goals of Guix -- implicitly reading
>> ~/.ssh/known_hosts doesn't seem declarative to me. What's our means for
>> deprecating features like that? A warning message when omitted? If
>> that's the case, I'm definitely on board.
>
> Yup, we can emit a deprecation warning when the key is #f.
>
> So let’s take that route if nobody objects. It’s easier to deprecate it
> now that “guix deploy” is still very new.
Done in commit 2617d956d8ae122128a1ba2cc74983cbd683b042!
Ludo’.