similar to: small addition to the scp man page

second time, is there anybody that can tell me where I can send contributions to the man pages? Dom <<small addition to the scp man page>> -------------- next part -------------- An embedded message was scrubbed... From: "Cressatti, Dominique" <Dominique.Cressatti at lansa.co.uk> Subject: small addition to the scp man page Date: Mon, 9 Sep 2002 13:37:41 +0100 Size:

https://bugzilla.mindrot.org/show_bug.cgi?id=1451 Summary: Slight addition to the "scp" man page Classification: Unclassified Product: Portable OpenSSH Version: 4.7p1 Platform: Other

Hi. This functionality was just added in 2.2.0p1. The patch is self-explanatory. Charles --- scp.c.orig-2.2.0p1 Tue Aug 29 19:11:30 2000 +++ scp.c Sat Sep 2 15:14:58 2000 @@ -262,7 +262,7 @@ extern int optind; fflag = tflag = 0; - while ((ch = getopt(argc, argv, "dfprtvBCc:i:P:q46S")) != EOF) + while ((ch = getopt(argc, argv, "dfprtvBCc:i:P:q46S:")) != EOF)

Hello, I noticed: 20030124 - (djm) OpenBSD CVS Sync - markus at cvs.openbsd.org 2003/01/23 14:01:53 [scp.c] bandwidth limitation patch (scp -l) from niels@; ok todd@, deraadt@ [...]

https://bugzilla.mindrot.org/show_bug.cgi?id=1600 Summary: scp(1) man page feedback Product: Portable OpenSSH Version: 5.2p1 Platform: Other OS/Version: All Status: NEW Severity: enhancement Priority: P2 Component: scp AssignedTo: unassigned-bugs at mindrot.org ReportedBy: dgatwood at

I miss the stars when doing scp. My suggestion for progressmeter.c makes scp to display different fields on different terminal widths. Maybe this is useful for you. Once in "start_progress_meter()" the outlook of the progressline is calculated. In "draw_progress_meter()" sprintf() instead of snprintf() together with some strlen()'s can be used, because the buffersize has

As a fairly experienced Unix user, it's obvious to me that scp copies files from left to right -- that is, that the last [host:]file on the command line is the destination. However, this might not be so obvious to users with less experience. It pains me to suggest this, but perhaps the scp man page should be edited to make this more obvious. For example, from the [Free]BSD cp(1) man

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

>> I understand that that is not how scp works today.>And it will likely never change. Why not? Just because "That's how we've always not done it" doesn't sound like a very good reason to me. >> I'm suggesting that we make a minor change to how it works.>scp is maintained for compatibility reasons only, as I've understood>things. That's still

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