INTL 3:770/1 3:770/3
REPLYADDR Pancho.Jones@proton.me
REPLYTO 3:770/3.0 UUCP
MSGID: 6f5ff7ea
REPLY: f1693868
PID: SoupGate-Win32 v1.05
On 01/02/2024 21:19, druck wrote:
> On 01/02/2024 08:12, Pancho wrote:
>>> Generate a new key on each device with ssh-keygen and copy it to your
>>> primary machine with ssh-copy-id Then replicate the primary machines
>>> .ssh/authorized_keys file to all the others, so you can login from
>>> any machine to any other.
>>>
>>
>> Yes, but in practice that meant everytime I installed a new OS on an
>> experimental Orange Pi5 I had to alter the set up of seven or eight
>> machines. Sometimes I was doing this a few times a day.
>
> Not it you have a way of replicating the .ssh/authorized_keys file
> between machines. You can do it with a cron script that does a copy
> every few minutes if the master changes.
>
Yep replication seems a good idea, I'm a little scared of roll your own
security automation. It's a topic that is both boring and tricky, a bad
combination. I can't see anyting wrong with it, but that often isn't a
good guide.
For the moment I think I'll investigate Richard's certificate base
authority idea. Thanks.
--- 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
|
