similar to: scp with different users

Hello, I would like to specify ports on both hosts to copy files between two remote computeres. Is there any way to do this with scp? The -P flag seems to apply to the port on the second host only. Regards, Miguel

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

Attached is a patch which adds a log= directive to authorized_keys. The text in the log="text" directive is appended to the log line, so you can easily tell which key is matched. For instance the line: log="hello world!",no-agent-forwarding,command="/bin/true",no-pty, no-user-rc,no-X11-forwarding,permitopen="127.0.0.1:7" ssh-rsa AAAAB3Nza....xcgaK9xXoU=

I have built the freshest CVS versions of openssh and still observe the same strangest behavior I encountered when trying to scp from a SuSE 7.2 to RedHat 7.1 system -- I built openssl-0.9.6e on RedHat as well-- and updated a lot of stuff; but still: ssh succeeds, and scp fails, leaving the following message in /var/log/secure: Aug 5 11:50:44 pdb-pc-6 sshd[4609]: fatal: buffer_get: trying to

https://bugzilla.mindrot.org/show_bug.cgi?id=1998 Bug #: 1998 Summary: Arbitrary command execution using SCP Classification: Unclassified Product: Portable OpenSSH Version: 5.8p1 Platform: All OS/Version: Linux Status: NEW Severity: security Priority: P2 Component: scp AssignedTo:

On 11/23/15 4:50 PM, Damien Miller wrote: > On Sun, 22 Nov 2015, David Ahern wrote: > >> Hi: >> >> The openssh suite of commands have an option to specify address (e.g, >> ListenAddress for sshd) but I do not see support for bind-to-interface. >> >> The motivating use case for me is using openssh commands (sshd, ssh, scp, >> sftp) with the recent VRF

Hello - I am trying to use scp (openssh_3.0), but every time I run it, I get the following error: stty: Not a typewriter When I run it with -v , it shows that authentication (pub key) succeeds, but it fails to read the file. If anybody has a clue as to what's going on here, any help will be appreciated. Thanks. Tariq tariq.lahyani at aa.com

https://bugzilla.mindrot.org/show_bug.cgi?id=1427 Summary: scp -q behavior different than documented Classification: Unclassified Product: Portable OpenSSH Version: 4.7p1 Platform: All OS/Version: All Status: NEW Severity: minor Priority: P3 Component: scp AssignedTo: bitbucket at mindrot.org

http://bugzilla.mindrot.org/show_bug.cgi?id=634 Summary: scp incompatibility with ssh.com scp Product: Portable OpenSSH Version: 3.6.1p2 Platform: All OS/Version: All Status: NEW Severity: major Priority: P2 Component: scp AssignedTo: openssh-bugs at mindrot.org ReportedBy: wgs3 at

http://bugzilla.mindrot.org/show_bug.cgi?id=959 Summary: enhancement: supporting a remote scp path option in scp Product: Portable OpenSSH Version: -current Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: scp AssignedTo: openssh-bugs at mindrot.org

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

When copying a file with an escaped character, scp removes the escaping character before sending to the host. Is there a way to circunvent this? Some examples follow (linux machines) A: touch file\(new\) B: scp user at A:file\(new\) . user at A password: bash: -c: line 1: syntax error near unexpected token `(' bash: -c: line 1: `scp -f (' A: touch file\ 1 B: scp user at A:file\ 1 .

I recently built openssh 2.1.1p1, under solaris. I noticed that I had problems running scp. It seems that it could not find the executable on the remote end. This was odd, becuase it existed in /usr/local/bin, publically executable, and /usr/local/bin/was in the users' normal PATH (exported, even). So finally, I twiddled the source to make it call /usr/local/bin/scp, instead of just

Hello, in order to use "scp", the scp binary has to be in the compile-time default path on the remote host. For some users (like root), we try to avoid this since scp may be on a network file system (AFS/NFS), and we don't want to hang root's session on network outages. Would a patch to scp be acceptable in the main tree that allows to set the path to remote scp explicity,

Hello All, As the release notes of SSH-4.7 version says that a new MAC algorithm (UMAC-64 - RFC4418) was introduced with OpenSSH-4.7 which gives much better performance, I was tempted to check out the enhanced speed provided with new version. So I downloaded OpenSSH-5.1p1 and build it on Solaris 10 with Sun Compiler CC. My test setup:- 1. Two Sunfire 440 with 2 CPU (1281 MHz) and 4GB RAM. 2.

Hi there, I've written some enhancements to scp.c and pathnames.h to enable the scp to arbitrarily set the remote scp path. (eg $ scp -e /usr/bin/scp foo user at bar:foo) I did read the "scp: command not found" FAQ entry but I'm not quite sure why we can't do this, unless it's because enhancements to scp are no longer a priority. Any other reason why it "is the

Hey. I'm also a bit concerned about this issue... On Tue, 2019-01-22 at 13:48 +1100, Damien Miller wrote: > Don't use > scp with untrusted servers. But that would effectively mean one has to toss scp. Reality is simply that most peers cannot be really trusted? just imagine all the administration work which is done from some user/admin's computer to countless servers (running

I almost never use bare 'scp' or 'sftp' anymore; I start with either 'rsync' or, if 'rsync' is not present and not installable on one end or the other, the "tar-over-bare-ssh" approach: ``` tar cf - localpath | ssh remote.host 'cd remotepath && tar xvf -' ``` I'd be in favor of one of the following: 1. 'scp' goes away, and

I'm a bit confused how scp works... could someone please explain the local/remote external calls that happen when scp is started... in particular how it relates to ssh on the remote site? To be more specific... I use Kerberos for authentication and I've been working on an ssh wrapper script that checks my Kerberos credentials before running the ssh command. If the credentials are

On Mon, 4 Nov 2019, David Newall wrote: > On 4/11/19 3:29 am, Demi M. Obenour wrote: > > 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 see something much worse: > > $ sudo sh > # echo