Re: apt-key says deprecated, but not saying what else to use
Gene Heskett wrote:
> On Sunday 20 June 2021 10:21:52 Dan Ritter wrote:
>
> > Gene Heskett wrote:
> > > I'd like to pleaed for a new apt-key, one that would survey the
> > > existing list, and on finding a key that is expired or is no longer
> > > associated, offer the option of removing it, or refreshiing it.
> > >
> > > I have up to 7 machines on my local network, usually accessed by
> > > some ssh/sshfs variation, but my current keyring since I'm first
> > > user, probably has 30 some keys, many of which are useless as the
> > > target machine has been changed by a new machine and a new bare
> > > metal install.
> >
> > This is ssh key management, not apt key management. apt key
> > things are for trusting package repositories.
>
> okay, but
> >
> > Here's what you should do:
> >
> > 1. create a new ssh keypair on your main machine:
> > ssh-keygen -t rsa -b 4096 -f gene2021
>
> Done. generated /home/gene/gene2021 and /home/gene/gene2021.pub
>
> > 2. for each $targetmachine in your 7 machines, do this:
> > - ssh $targetmachine
> > - mv ~/.ssh/authorized_keys ~/.ssh/authorized_keys_old
>
> 4 of the 6 machines have no .ssh directory in /home/gene. ssh may have
> had to be installed after the bare metal install of debian 10 using the
> linuxcnc install cd. sshfs and its deps sure had to be after the first
> reboot. I'll go bug the LinuxCNC install spinners, been meaning to do it
> for months.
>
> Is it sufficient to create that directory, and
> touch .ssh/authorized_keys?
The directory can just be created, and then the perms need to be
chmod 600 ~/.ssh
authorized_keys will be created by ssh-copy-id.
> Also, the main machine, this one is still on stretch. With 310 gb used of
All of these commands work on stretch and later.
-dsr-
Reply to: