Re: Using "command" auth keys option to process scp operations

"tb" == tb <foxstore@xxxxxxxxxx> writes:

tb> Thanks for the feedback... Unfortunately, as I stated before,
tb> once the system call produces output, the scp client appears to
tb> terminate. This is with OpenSSH 3.6.1p2, as this is the version
tb> we're forced to use right now. However, this has also been tested
tb> on 4.2 with the same results.

tb> For example, put this line before the system call and it'll never
tb> get to the system call:

tb> print "Junk\n";

tb> Can someone verify this works (or doesn't)?

I don't understand; you said you wanted to do "postprocessing." This is
placing something *before* running scp.

tb> Thanks! Tom

tb> Richard E. Silverman wrote:
>> >>>>> "AMF" == all mail refused <elvis-85383@xxxxxxxxxxxxxx>
>> writes:
>>
AMF> On 2006-04-29, Richard E. Silverman <res@xxxxxxxx> wrote:
>> >> http://www.snailbook.com/faq/scp-wrapper.txt Change the final
>> line >> to: system("$scp_server @scp_argv"); ... place whatever
>> code you >> want after that.
>>
AMF> Did you have a reason for using the scalar version of system()
AMF> (that launches a shell) instead of the list version which would
AMF> be closer to the original script? system($scp_server,
AMF> @scp_argv); No shell => no scares if the arguments include shell
AMF> metacharacters.
>> Nope; it was just a quick example. This is of course a better
>> idea.
>>
>> -- Richard Silverman res@xxxxxxxx


--
Richard Silverman
res@xxxxxxxx

.