similar to: [Bug 882] Scp cannot copy self-referring directories

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

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/

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

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

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.

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

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

I have not been able to get scp(1) to download a file with a newline in its name. I know that scp(1) requires that remote filenames be escaped for the shell, but that leads to protocol errors. I am also unable to get sftp(1) to handle such files. It fails with an ?unterminated quoted argument? error, no matter how I try to quote the newline. Furthermore, the SFTP CLI is not well-suited to

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 was just curious how come there is no interactive option available for scp? A -i option is available for cp and rm, etc which prompts you before overwriting existing files. Was there a special reason why a similar option was not made available for scp? Thanks, Umar

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=828 Damien Miller <djm at mindrot.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #588| |ok+ Flag| | --- Comment #2 from Damien Miller <djm at mindrot.org>

http://bugzilla.mindrot.org/show_bug.cgi?id=298 ------- Additional Comments From sshbugs at wayne47.com 2002-06-26 11:05 ------- Problem appears to be that setusercontext is being called after a chroot. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

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/

hey all 'scp -r ' follows symlinks. IMO this is a bug and should be changed - it: a) hampers the use of scp. As it stands, I cannot use 'scp -r' because of this behavior. If someone links to '/', or if I hit a recursive symlink, I'm screwed. b) It is inconsistant with cp. When you 'cp -r' on a file, it does NOT follow the symlink. When you scp

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.

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

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