Re: scp in unattended batch mode
From: Jack Moe (mojorisin_at_bigmailbox.net)
Date: 06/17/04
- Previous message: LRW: "Re: scp in unattended batch mode"
- In reply to: Richard E. Silverman: "Re: scp in unattended batch mode"
- Next in thread: LRW: "Re: scp in unattended batch mode"
- Reply: LRW: "Re: scp in unattended batch mode"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: 17 Jun 2004 13:06:08 -0700
Richard E. Silverman <res@qoxp.net> wrote in message news:<m2wu269s8v.fsf@darwin.oankali.net>...
> >>>>> "LRW" == LRW <deja@celticbear.com> writes:
>
> LRW> I know it's not good security, but just to make sure I had it
> LRW> covered I chmod 777 recursively the entire user's directory on
>
> That would ensure that it *not* work -- ~, ~/.ssh/, and
> ~/.ssh/authorized_keys must normally be writable only by the owner or
> root.
Verify that your public key should be in 'authorized_keys2' or in
'authorized_keys'. This information will be in the SSH sever's
'sshd_config' file.
Check the target system's pemission on the home directory. There
should be no write permissions on group or other. Having write
permissions on group or other will also break SSH public key
authentication.
Jack Moe
- Previous message: LRW: "Re: scp in unattended batch mode"
- In reply to: Richard E. Silverman: "Re: scp in unattended batch mode"
- Next in thread: LRW: "Re: scp in unattended batch mode"
- Reply: LRW: "Re: scp in unattended batch mode"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]