similar to: [Bug 485] scp doesn't preserve symbolic links

http://bugzilla.mindrot.org/show_bug.cgi?id=485 ------- Additional Comments From markus at openbsd.org 2003-02-07 07:51 ------- why don't you use sftp? i think skipping links is an option, but copying not. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

http://bugzilla.mindrot.org/show_bug.cgi?id=485 Summary: scp doesn't preserve symbolic links Product: Portable OpenSSH Version: -current Platform: All OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: scp AssignedTo: openssh-unix-dev at mindrot.org ReportedBy: jsk29

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

http://bugzilla.mindrot.org/show_bug.cgi?id=248 ------- Additional Comments From liug at mama.indstate.edu 2002-05-18 07:14 ------- I tried several different versions of openssh, and got the same problem with scp. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

http://bugzilla.mindrot.org/show_bug.cgi?id=882 Summary: Scp cannot copy self-referring directories Product: Portable OpenSSH Version: 3.8p1 Platform: All OS/Version: Linux Status: NEW Severity: major Priority: P2 Component: scp AssignedTo: openssh-bugs at mindrot.org ReportedBy:

http://bugzilla.mindrot.org/show_bug.cgi?id=88 ------- Additional Comments From markus at openbsd.org 2002-01-31 23:01 ------- this is an installation error on the target host, see: scp: warning: Executing scp1 compatibility. scp: FATAL: Executing ssh1 in compatibility mode failed (Check that scp1 is in your PATH). ------- You are receiving this mail because: ------- You are the assignee

Hi, Is there some know problem between the 'scp' client in OpenSSH 2.5.1p1 and F-Secure's SSH 2.4.0 server? The client is running on a Linux (2.2.17) box and server is running on Win2K. When I try to transfer files it asks me for the password (which I provide) then it hangs. Using 'scp -v' didn't provide any helpful info; it's as though the problem happened before

http://bugzilla.mindrot.org/show_bug.cgi?id=886 Summary: Unable to scp from OPenSSH to Commercial SSH Product: Portable OpenSSH Version: 3.8.1p1 Platform: Sparc OS/Version: Solaris Status: NEW Severity: major Priority: P2 Component: scp AssignedTo: openssh-bugs at mindrot.org ReportedBy:

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 >

Hello, For some time now, our users have been encountering a problem when using scp to overwrite files on our mass-storage system, which uses SGI's DMF product. I don't have any data as to whether or not any other HSMs would be similarly affected. The scenario is that a user is overwriting a file (via scp) that has previously been migrated to tape. The scp opens the file for writing, but

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

On Tue, 2020-06-23 at 08:06 +0200, Markus Friedl wrote: > I had something in mind like this for years, but with slightly > different steps: > My naive approach would be to keep the scp user interface and switch > to the sftp protocol internally. We could add a -M [scp|sftp] option > to scp and select the internal protocol. Later we switch the default > from scp to sftp. > No

I spent some time debugging a failing Scp that turned out to be caused by the remote shell producing messages on Standard Output that aren't part of the SCP protocol. Scp from a remote system works by running another Scp on the remote system. The remote Scp writes SCP protocol messages (and file data) to its Standard Output, which the local Scp sees as Standard Input. But it's

http://bugzilla.mindrot.org/show_bug.cgi?id=794 Summary: scp2 copy from machine A (openssh 3.5p1) to B (ssh 2.4.0) causes transferred file to be empty Product: Portable OpenSSH Version: -current Platform: ix86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: scp

This bug (Debian bug number 111692) occurs with filenames that have the character 0x0a in them (newline). This is how one repeats it: ming.empire.pick.ucam.org:~/ssh-test/ # [01/09/10.00:15:50] $ : bash[592] ; cat > 'x x' This is a test. ming.empire.pick.ucam.org:~/ssh-test/ # [01/09/10.00:16:17] $ : bash[593] ; scp 'x x' dorothee:ssh-test/

If the source and destination file are identical, the receiving scp truncates the file. On the sending end, read() returns 0, and garbage is sent instead of actual data, and the receiving end puts it into the file, which at least confuses the users. -- Florian Weimer Florian.Weimer at RUS.Uni-Stuttgart.DE University of Stuttgart http://cert.uni-stuttgart.de/

Hi, A couple of days ago I realized that 'scp' on the client-side requires 'scp' on the server-side as well. client:scp -> server:sshd -> server:scp It this really the way it should be? IMHO it seems like a bad design. I usually create a Solaris-package with prngd, sshd, ssh-keygen and name it OpenSSH-3.x.x-serveronly but now I have to also include 'scp'. Is it

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 @@

Has anyone had a problem with scp not retaining ACLs set on the original file under Solaris 8? When I have a file that has ACLs set and I use scp or rsync -e ssh to copy the file (local->local or local->remote) the ACLs are gone from the copied file(s). Is this a known issue or am I just missing something (a flag for instance) when performing the copy? Thanks in advance for your help.

As of Sunday evening, OpenSSH has an interactive sftp client. It should be in the more recent snapshots. It would be appreciated if you could test new client and find all the bugs :) Please also have a read of the manpage and ensure that it matches what is implemented. I am working on fixing the ones that I know about, so please try to stay up to date with the snapshots. Thanks, Damien