INTL 3:770/1 3:770/3
REPLYADDR Pancho.Jones@proton.me
REPLYTO 3:770/3.0 UUCP
MSGID: a32713da
REPLY: e9fdea0a
PID: SoupGate-Win32 v1.05
On 30/01/2024 23:39, Scott Alfter wrote:
> In article ,
> Pancho wrote:
>> On 30/01/2024 23:16, Scott Alfter wrote:
>>> For remote access (to a headless box or otherwise), you should be using
>>> key-based authentication anyway and should disable password authentication
>>> in sshd.
>>
>> What is the usuaL set up for a home LAN, one key to rule them all, or a
>> key for each machine?
>
> One key for each host that needs to connect. That way, if one of your
> computers gets stolen or is lost, you can revoke its access.
>
Yes, I understand the need for unique keys for clients which operate
outside the home, like a laptop, but what about for the LAN only
devices? For instance, a rPi using scp to another rPi. I have quite a
few Pis.
When I set up a new machine, it is often easier to use an existing key
which already has been installed on all SSH servers, so I use a single
one. Often, I just copy the ~/.ssh folder. I suppose I could reuse a
currently unused key from a pool of configured keys, but it seems like a
lot of work.
--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
SEEN-BY: 10/0 1 15/0 90/1 103/705 105/81 106/201 128/260 129/305 135/225
SEEN-BY: 153/757 7715 218/0 1 601 700 840 870 930 220/70 221/1 6 226/17
SEEN-BY: 226/30 100 227/114 229/110 112 113 200 206 307 317 400 426
SEEN-BY: 229/428 470 550 616 664 700 240/1120 266/512 267/800 282/1038
SEEN-BY: 291/111 292/854 301/1 113 812 310/31 320/219 322/757 335/364
SEEN-BY: 341/66 342/200 396/45 460/58 633/280 712/848 770/1 3 100
SEEN-BY: 770/330 340 772/210 220 230 5020/400 1042 5058/104 5075/35
PATH: 770/3 1 218/840 221/6 301/1 218/700 229/426
|
