Bug 315841 - SFTP-Copying a binary file via Dolphin enlarges the file
Summary: SFTP-Copying a binary file via Dolphin enlarges the file
Status: RESOLVED DUPLICATE of bug 312320
Alias: None
Product: kio
Classification: Unmaintained
Component: sftp (show other bugs)
Version: 4.8
Platform: Debian testing Linux
: NOR major
Target Milestone: ---
Assignee: Andreas Schneider
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-02-27 10:43 UTC by schaise
Modified: 2013-02-28 11:46 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description schaise 2013-02-27 10:43:30 UTC
I copied a binary file via Dolphin using sftp://path/to/file to my local filesystem. Compared to copying the file via scp using a shell, the file is slightly larger afterward. 

-rwxr-xr-x 1 user user 7434240 Feb 27 11:32 filename - USING DOLPHIN: Wrong size
-rwxr-xr-x 1 user user 7372800 Feb 27 11:31 filename - USING SCP: right size, same as source

This behaviour is absolutely reproducable.

Reproducible: Always

Steps to Reproduce:
1. Copy file using sftp:// to local filesystem
2. Compare size of copy to size of source file
3.
Comment 1 Frank Reininghaus 2013-02-27 10:59:16 UTC
Thanks for the bug report! Might be a problem with the sftp kioslave, so I'll reassign (even though I'm not sure how much a bug report for such an old version is worth now).
Comment 2 schaise 2013-02-27 12:11:56 UTC
Further investigation shows that the file is being extended by plain zeros when copied using dolphin
Comment 3 schaise 2013-02-27 16:20:48 UTC
(In reply to comment #1)
> Thanks for the bug report! Might be a problem with the sftp kioslave, so
> I'll reassign (even though I'm not sure how much a bug report for such an
> old version is worth now).

Well it might be old but this is the version that is supposed to be used in the upcoming debian stable ;)
Comment 4 Andreas Schneider 2013-02-28 11:46:18 UTC

*** This bug has been marked as a duplicate of bug 312320 ***