scp of sysfs file repeats data
Craig McQueen
craig.mcqueen at innerrange.com
Wed Jun 24 12:52:19 AWST 2015
> From: Reimar Döffinger [mailto:Reimar.Doeffinger at gmx.de]
>
> On 24.06.2015, at 01:49, Craig McQueen <craig.mcqueen at innerrange.com>
> wrote:
> >> From: Peter Korsgaard [mailto:jacmet at gmail.com] On Behalf Of Peter
> >>
> >>>>>>> "Peter" == Peter Korsgaard <peter at korsgaard.com> writes:
> >>
> >>>>>>> "Matt" == Matt Johnston <matt at ucc.asn.au> writes:
> >>>> I see what you mean. I'll update scp to OpenSSH's latest - >> there are
> a
> >> few changes to be merged.
> >>
> >>> FYI, openssh scp has a similar problem here:
> >>
> >>> open("vendor", O_RDONLY|O_NONBLOCK) = 3
> >>> fstat(3, {st_mode=S_IFREG|0444, st_size=4096, ...}) = 0
> >>> fcntl(3, F_GETFL) = 0x8800 (flags
> >> O_RDONLY|O_NONBLOCK|O_LARGEFILE)
> >>> fcntl(3, F_SETFL, O_RDONLY|O_LARGEFILE) = 0
> >>> write(6, "C0444 4096 vendor\n", 18) = 18
> >>> read(3, "0x8086\n", 4096) = 7
> >>> read(3, "", 4089) = 0
> >>> write(6,
> >> "0x8086\n\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 4096)
> =
> >> 4096
> >>
> >>> This is with openssh 6.7p1-6.
>
> Looking at the source code, the protocol should have sent an EIO error, so
> the user/programs checking the exit code should be able to see something
> went wrong...
> Is that somehow not working?
Yes, with openssh scp, I get a "Broken pipe" error. That's good under the circumstances.
With dropbear scp, I don't get any error.
--
Craig McQueen
More information about the Dropbear
mailing list