BLU Discuss list archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Discuss] rsync issue
- Subject: [Discuss] rsync issue
- From: richard.pieri at gmail.com (Rich Pieri)
- Date: Tue, 1 Nov 2022 17:18:49 -0400
- In-reply-to: <f6fc8bf44efa2721d6589c4d73eb574f.squirrel@mail2.ihtfp.org>
- References: <Y2GBemiowKtvxJow@alphacent.localdomain> <f6fc8bf44efa2721d6589c4d73eb574f.squirrel@mail2.ihtfp.org>
On Tue, 1 Nov 2022 16:39:26 -0400 "Derek Atkins" <derek at ihtfp.com> wrote: > Hi, > > Have you tried running ssh with -v? > > Going out on a limb, what do you get from: > > ls -la $HOME/.ssh > > Initial guess is that .ssh dir is not mode 0700, and SSH doesn't like > that. This is the first thing to check. Also check the permissions all the way up to the root of the file system. $HOME/.ssh and $HOME must be owned by you, and $HOME must be no more open than mode 755. /home and / must be owned by root and no more open than mode 755. OpenSSH will reject keys if the file system permissions do not meet this minimum. If permissions are good then check your key types. DSA keys are dead and are rejected by OpenSSH. Generate and use ED25519 or RSA keys. If key types are good then check key lengths. Too-short keys may be rejected. If this is the case then you will need to generate new keys of sufficient length. -- \m/ (--) \m/
- References:
- [Discuss] rsync issue
- From: jdm at moylan.us (dan moylan)
- [Discuss] rsync issue
- From: derek at ihtfp.com (Derek Atkins)
- [Discuss] rsync issue
- Prev by Date: [Discuss] rsync issue
- Next by Date: [Discuss] Music Server/Player
- Previous by thread: [Discuss] rsync issue
- Next by thread: [Discuss] rsync issue
- Index(es):