[vox-tech] crontab and scp puzzle

[Harold Lee]

Are you passing your public or private key filename via -i?

These lines imply that scp tried to use the file as a private key but
failed because it couldn't figure out what kind of file (rsa/dsa) it
was. That happens if you use the id_dsa.pub instead of the id_dsa
file.

debug1: PEM_read_PrivateKey failed
debug1: read PEM private key done: type <unknown>

Harold

On Wed, Mar 16, 2011 at 5:37 PM, Bruce Wolk <bawolk at ucdavis.edu> wrote:
> I tried -B as well.
>
> On 03/16/2011 05:36 PM, Michael Wenk wrote:
>> I was going to suggest the -B option, but that should be the same as
>> -o BatchMode=yes ...
>>
>> Mike
>>
>> On Wed, Mar 16, 2011 at 5:09 PM, Kyle Ambroff<kyle at ambroff.com>  wrote:
>>> On Wed, Mar 16, 2011 at 5:06 PM, Kyle Ambroff<kyle at ambroff.com>  wrote:
>>>>
>>>> I know I've used this answer before on this list, and I'm sure it's annoying, but if your solution involves passphraseless ssh keys, you're doing it wrong.
>>>> That being said, since cron is a daemon, it is not attached to a controlling terminal. That means that a script that expects to be able to read input from the user is going to fail. You can probably force it to bypass this code with BatchMode.
>>>>      ssh -o BatchMode=yes ...
>>>> For good measure, you could even set TERM if it's not being set.
>>>>      env TERM=dumb ssh -o BatchMode=yes ...
>>>
>>> Replace "ssh" with "scp" and that still works.
>>> _______________________________________________
>>> vox-tech mailing list
>>> vox-tech at lists.lugod.org
>>> http://lists.lugod.org/mailman/listinfo/vox-tech
>>>
>>
>>
>>
> _______________________________________________
> vox-tech mailing list
> vox-tech at lists.lugod.org
> http://lists.lugod.org/mailman/listinfo/vox-tech
>