[CentOS] scp scripting question

Les Mikesell lesmikesell at gmail.com
Fri Oct 12 22:20:23 EDT 2012


On Fri, Oct 12, 2012 at 9:02 PM, Gordon Messmer <yinyang at eburg.com> wrote:
> On 10/12/2012 01:56 PM, Les Mikesell wrote:
>> On Fri, Oct 12, 2012 at 3:44 PM, Nux! <nux at li.nux.ro> wrote:
>>>
>>> Yep, exactly right. People in #openssh confirmed -i HAS to be a real
>>> path to a file.
>>
>> Not very unix-like behavior...
>
> Yes, it is.  The alternative is for -i to take a file or a key as an
> argument, and that leads to ambiguous behavior.

How so?   What's wrong with what behaves like a named pipe?   That is,
why does scp need to seek instead of just reading the contents?

> All the same, I keep my keys in
> an encrypted volume because they grant me access to my customer's
> systems.  The idea of writing them to a filesystem that's not encrypted
> is just creepy.

Sure, but who else can open your /dev/fd/##'s?

-- 
    Les Mikesell
      lesmikesell at gmail.com


More information about the CentOS mailing list