similar to: [Bug 828] date overflow with scp -p

http://bugzilla.mindrot.org/show_bug.cgi?id=828 Summary: date overflow with scp -p Product: Portable OpenSSH Version: 3.7.1p2 Platform: ix86 OS/Version: Linux Status: NEW Severity: minor Priority: P3 Component: scp AssignedTo: openssh-bugs at mindrot.org ReportedBy: throw_away_2002 at

I don't know if anyone would be interested in this but I'm including a patch to allow for offsets when transferring files with SCP. It's pretty simple and assumes the user knows what they are doing (for example, if transferring with a wild card the offset would apply to all files). -A is the number of bytes offset from the beginning of the files. -Z is the number of bytes inset

Hello, I would like to request an update of the progress regarding fixes for the recently disclosed SCP vulnerability (CVE-2018-20685, CVE-2019-6111, CVE-2019-6109, CVE-2019-6110) It has been stated that CVE-2018-20685 has been patched in november but there are currently no information available on the progress of patches regarding the other CVEs. Will there be a patched release any time soon?

Dear developers, I discovered that directories created by scp when recursive copying into a sgid directory do not inherit the sgid bit. I believe this is a bug. A patch to fix this is attached. Regards, Petr Skovron -------------- next part -------------- --- scp.c.orig 2005-10-11 16:50:17.000000000 +0200 +++ scp.c 2005-10-11 16:57:25.000000000 +0200 @@ -876,8 +876,12 @@

Hi All, I am looking for SCP or RCP standards. I searched on the web but I am not able to find the standards. Please mail me the link where I can find the standards for SCP or RCP. Thanks, Abhijeet

On Wed, 15 Jul 2020, Red Cricket wrote: > I have had this in my .bashrc for years: > > alias scp='rsync -avzP' Similar, though I named it rcp because nobody has the real rcp installed any more, but sometimes I need scp to connect to systems that lack rsync. https://evolvis.org/plugins/scmgit/cgi-bin/gitweb.cgi?p=shellsnippets/shellsnippets.git;a=blob;f=mksh/rcp;hb=HEAD >

Why can the local and remote paths be sanitized? Regards, Uri > On Jul 31, 2020, at 19:57, Ethan Rahn <ethan.rahn at gmail.com> wrote: > > ?I wanted to bring this up again due to: > https://github.com/cpandya2909/CVE-2020-15778/. This showcases a clear > issue with scp which it sounds like cannot be fixed without breaking scp. > This seems like it would lend some impetus

When you require a scp copy of more than 1 file to a destination that is not a directory, scp copy the last input file to the destination (version openssh-3.8.1p1). Thus if you forget to specify the destination, the last file is _silently destroyed_. I know that rcp exhibits the same behaviour but cp and rsync don't do anything in that case and _kindly_ warn you that you made a mistake:

http://bugzilla.mindrot.org/show_bug.cgi?id=485 djm at mindrot.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX ------- Additional Comments From djm at mindrot.org 2003-06-04 23:28

I've run into a situation where we'd like to replace rcp with rsync, but we've run into a difference in interface, which is causing us problems. Here's the problem. If we run this in rsync: > mkdir tmpdir; cd tmpdir > mkdir a; touch a/b > rsync -r a b/ > ls b a/ But for all the other programs, we get something different: > cp -r a c/ > ls c foo > cp

When copying from a remote host to a local filesystem with a strange block size, allocbuf() in scp.c seems to calculate an incorrect buffer size, causing the copy loop in sink() to write past the end of the buffer. For example, with smbfs, the optimal block size is negotiated when the client connects to the server, and is rarely a power of two. In my case it is 64560. This loop in sink() keeps

I'm fond of the "-a" (archive) option of cp, and I'm a heavy user of scp, so I guess it's inevitable that I would eventually add support for "-a" to scp. :-) Actually, it's a "-L" flag for preserving symlinks, and a "-a" flag that is shorthand for "-Lpr". Please let me know if I'm not doing this right.... I made a great

http://bugzilla.mindrot.org/show_bug.cgi?id=801 Summary: Improve usability of scp by adding a "make path" option Product: Portable OpenSSH Version: -current Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P3 Component: scp AssignedTo: openssh-bugs at mindrot.org

I'd like to know a little about the internals of RSYNC. I am a little confused as to why RSYNC is using both the simple 32 bit algorithm and the MD4 checksum function on the same files. From my testing this causes a vast overhead that is clearly not represented by RCP (fairly obvious!). Removing checksumming from a secure whole-file LAN transfer brings RSYNC in line with the general

https://bugzilla.mindrot.org/show_bug.cgi?id=1436 Summary: scp -p does not preserve sticky bit (01000) Classification: Unclassified Product: Portable OpenSSH Version: 4.7p1 Platform: All OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: scp AssignedTo: bitbucket at

Hi, I have made a patch which improves scp utility. It adds two new features: rate limit and resume support. With rate limit it's possible to limit transfer speed. Resume allows to continue file transfer where it was last interrupted. Also the progress meter was improved. Here is my patch, please send comments about it and what I can do better if there is something to fix. ---

Hi, using both OpenSSH_2.5.1p1 (compiled myself) and openssh-2.9p1-23.i386.rpm from ftp.suse.com 7.2_update I get the following "leak" : using `scp' I tried to copy a file from a local floppy disk to a remote system, but the disk had an read error and scp didn't get any real data from floppy: turtle koenig > scp /media/floppy/file.c harald:file.c

http://bugzilla.mindrot.org/show_bug.cgi?id=1337 Summary: SCP performance twice as slow as RCP Product: Portable OpenSSH Version: 3.8.1p1 Platform: Other OS/Version: AIX Status: NEW Severity: enhancement Priority: P3 Component: scp AssignedTo: bitbucket at mindrot.org ReportedBy:

Hi, The following patch does two things (which you may choose to take separatly if you don't like one or t'other). Firstly, I add a -1 and -2 option, since a) it's convenient b) people keep asking for it c) it's hardly a big fix, nor does it break backwards compatibility and d) I don't accept any slippery slope arguments. Secondly, I check for and ignore filenames with \n in

IF ssh is a replacement for rlogin,rsh etc I can accept it respecting rlogin=false as rlogin does and rsh does not, however scp is a replacement for rcp, and rcp does NOT use rlogin attribute, so the implementation is NOT standard as scp fails if rlogin=false, but rcp succeeds, as documented. thanks mark