summaryrefslogtreecommitdiffstats
path: root/scp.1 (follow)
Commit message (Collapse)AuthorAgeFilesLines
* upstream: sync -o option lists with ssh.1; requested jmc@djm@openbsd.org2024-12-071-10/+49
| | | | OpenBSD-Commit-ID: a7ac295b444da7b2ca7a33a52370594f6897f6bb
* upstream: Mention that scp uses the SFTP protocol and removedjm@openbsd.org2023-01-031-7/+6
| | | | | | reference to legacy flag. Spotted by, feedback and ok jmc@ OpenBSD-Commit-ID: 9dfe04966f52e941966b46c7a2972147f95281b3
* upstream: add a -X option to both scp(1) and sftp(1) to allowdjm@openbsd.org2023-01-031-2/+16
| | | | | | | | | | | | | | control over some SFTP protocol knobs: the copy buffer length and the number of inflight requests, both of which are used during upload/download. Previously these could be controlled in sftp(1) using the -b/-R options. This makes them available in both SFTP protocol clients using the same option character sequence. ok dtucker@ OpenBSD-Commit-ID: 27502bffc589776f5da1f31df8cb51abe9a15f1c
* upstream: add RequiredRSASize to the list of keywords accepted bydjm@openbsd.org2022-09-271-2/+3
| | | | | | -o; spotted by jmc@ OpenBSD-Commit-ID: fe871408cf6f9d3699afeda876f8adbac86a035e
* upstream: list the correct version numbertj@openbsd.org2022-04-161-4/+4
| | | | | | | for when usage of the sftp protocol became default and fix a typo from ed maste OpenBSD-Commit-ID: 24e1795ed2283fdeacf16413c2f07503bcdebb31
* upstream: put back the scp manpage changes for SFTP mode toodjm@openbsd.org2022-02-231-10/+14
| | | | OpenBSD-Commit-ID: 05dc53921f927e1b5e5694e1f3aa314549f2e768
* upstream: revert for imminent OpenSSH release, which wil ship withdjm@openbsd.org2022-02-101-14/+10
| | | | | | | | | | | | | scp in RCP mode. > revision 1.106 > date: 2021/10/15 14:46:46; author: deraadt; state: Exp; lines: +13 -9; commitid: w5n9B2RE38tFfggl; > openbsd 7.0 release shipped with the (hopefully last) scp that uses RCP > protocol for copying. Let's get back to testing the SFTP protocol. This will be put back once the OpenSSH release is done. OpenBSD-Commit-ID: 0c725481a78210aceecff1537322c0b2df03e768
* upstream: switch scp(1) back to sftp protocol.deraadt@openbsd.org2021-10-221-10/+14
| | | | | | | openbsd 7.0 release shipped with the (hopefully last) scp that uses RCP protocol for copying. Let's get back to testing the SFTP protocol. OpenBSD-Commit-ID: 9eaa35d95fd547b78b0a043b3f518e135f151f30
* upstream: fix missing -s in SYNOPSYS and usage() as well as adjm@openbsd.org2021-09-211-3/+3
| | | | | | capitalisation mistake; spotted by jmc@ OpenBSD-Commit-ID: 0ed8ee085c7503c60578941d8b45f3a61d4c9710
* upstream: Switch scp back to use the old protocol by default, ahead ofdjm@openbsd.org2021-09-201-14/+10
| | | | | | | | release. We'll wait a little longer for people to pick up sftp-server(8) that supports the extension that scp needs for ~user paths to continue working in SFTP protocol mode. Discussed with deraadt@ OpenBSD-Commit-ID: f281f603a705fba317ff076e7b11bcf2df941871
* upstream: Clarify which file's attributes -p preserves, and thatdtucker@openbsd.org2021-09-101-5/+5
| | | | | | | it's specifically the file mode bits. bz#3340 from calestyo at scientia.net, ok djm@ jmc@ OpenBSD-Commit-ID: f09e6098ed1c4be00c730873049825f8ee7cb884
* upstream: - move CAVEATS to its correct order - use the termjmc@openbsd.org2021-09-101-10/+10
| | | | | | | | | "legacy" protocol rather than "original", as the latter made the text misleading - uppercase SCP ok djm OpenBSD-Commit-ID: 8479255746d5fa76a358ee59e7340fecf4245ff0
* upstream: Use the SFTP protocol by default. The original scp/rcpdjm@openbsd.org2021-09-091-20/+22
| | | | | | | | | | | protocol remains available via the -O flag. Note that ~user/ prefixed paths in SFTP mode require a protocol extension that was first shipped in OpenSSH 8.7. ok deraadt, after baking in snaps for a while without incident OpenBSD-Commit-ID: 23588976e28c281ff5988da0848cb821fec9213c
* upstream: scp: tweak man page and error message for -3 by defaultnaddy@openbsd.org2021-08-121-5/+5
| | | | | | | | | Now that the -3 option is enabled by default, flip the documentation and error message logic from "requires -3" to "blocked by -R". ok djm@ OpenBSD-Commit-ID: a872592118444fb3acda5267b2a8c3d4c4252020
* upstream: Prepare for a future where scp(1) uses the SFTP protocol bydjm@openbsd.org2021-08-101-13/+21
| | | | | | | | | | default. Replace recently added -M option to select the protocol with -O (olde) and -s (SFTP) flags, and label the -s flag with a clear warning that it will be removed in the near future (so no, don't use it in scripts!). prompted by/feedback from deraadt@ OpenBSD-Commit-ID: 92ad72cc6f0023c9be9e316d8b30eb6d8d749cfc
* upstream: make scp -3 the default for remote-to-remote copies. Itdjm@openbsd.org2021-08-101-5/+15
| | | | | | | | | | | | | provides a much better and more intuitive user experience and doesn't require exposing credentials to the source host. thanks naddy@ for catching the missing argument in usage() "Yes please!" - markus@ "makes a lot of sense" - deraadt@ "the right thing to do" - dtucker@ OpenBSD-Commit-ID: d0d2af5f0965c5192ba5b2fa461c9f9b130e5dd9
* upstream: support for using the SFTP protocol for file transfers indjm@openbsd.org2021-08-031-2/+19
| | | | | | | | | | | | | scp, via a new "-M sftp" option. Marked as experimental for now. Some corner-cases exist, in particular there is no attempt to provide bug-compatibility with scp's weird "double shell" quoting rules. Mostly by Jakub Jelen in GHPR#194 with some tweaks by me. ok markus@ Thanks jmc@ for improving the scp.1 bits. OpenBSD-Commit-ID: 6ce4c9157ff17b650ace571c9f7793d92874051c
* Sync remaining ChallengeResponse removal.Darren Tucker2021-07-031-3/+2
| | | | These were omitted from commit 88868fd131.
* upstream: move HostbasedAcceptedAlgorithms to the right place innaddy@openbsd.org2021-01-271-2/+2
| | | | | | alphabetical order OpenBSD-Commit-ID: d766820d33dd874d944c14b0638239adb522c7ec
* upstream: Rename HostbasedKeyTypes (ssh) anddtucker@openbsd.org2021-01-261-3/+3
| | | | | | | | | HostbasedAcceptedKeyTypes (sshd) to HostbasedAcceptedAlgorithms, which more accurately reflects its effect. This matches a previous change to PubkeyAcceptedAlgorithms. The previous names are retained as aliases. ok djm@ OpenBSD-Commit-ID: 49451c382adc6e69d3fa0e0663eeef2daa4b199e
* upstream: Rename PubkeyAcceptedKeyTypes keyword todtucker@openbsd.org2021-01-221-3/+3
| | | | | | | | | | PubkeyAcceptedAlgorithms. While the two were originally equivalent, this actually specifies the signature algorithms that are accepted. Some key types (eg RSA) can be used by multiple algorithms (eg ssh-rsa, rsa-sha2-512) so the old name is becoming increasingly misleading. The old name is retained as an alias. Prompted by bz#3253, help & ok djm@, man page help jmc@ OpenBSD-Commit-ID: 0346b2f73f54c43d4e001089759d149bfe402ca5
* upstream: tweak the description of KnownHostsCommand in ssh_conf.5,jmc@openbsd.org2020-12-291-2/+3
| | | | | | | | and add entries for it to the -O list in scp.1 and sftp.1; ok djm OpenBSD-Commit-ID: aba31ebea03f38f8d218857f7ce16a500c3e4aff
* upstream: split introductory paragraph, and insert ominous words aboutderaadt@openbsd.org2020-10-031-4/+8
| | | | | | | | the glob issue, which cannot be fully fixed and really requires completely replacing scp with a completely different subsystem. team effort to find the right words.. OpenBSD-Commit-ID: 58e1f72d292687f63eb357183036ee242513691c
* upstream: allow -A to explicitly enable agent forwarding in scp anddjm@openbsd.org2020-08-031-3/+8
| | | | | | | sftp. The default remains to not forward an agent, even when ssh_config enables it. ok jmc dtucker markus OpenBSD-Commit-ID: 36cc526aa3b0f94e4704b8d7b969dd63e8576822
* upstream: tweak previous; ok markusjmc@openbsd.org2020-05-011-3/+3
| | | | OpenBSD-Commit-ID: 41895450ce2294ec44a5713134491cc31f0c09fd
* upstream: run the 2nd ssh with BatchMode for scp -3markus@openbsd.org2020-05-011-3/+6
| | | | OpenBSD-Commit-ID: 77994fc8c7ca02d88e6d0d06d0f0fe842a935748
* upstream: tweak the Nd lines for a bit of consistency; ok markusjmc@openbsd.org2019-12-111-3/+3
| | | | OpenBSD-Commit-ID: 876651bdde06bc1e72dd4bd7ad599f42a6ce5a16
* upstream: Hostname->HostName cleanup; from lauri tirkkonen okjmc@openbsd.org2019-06-141-3/+3
| | | | | | dtucker OpenBSD-Commit-ID: 4ade73629ede63b691f36f9a929f943d4e7a44e4
* upstream: check in scp client that filenames sent duringdjm@openbsd.org2019-01-261-3/+13
| | | | | | | | | | | | | | | | remote->local directory copies satisfy the wildcard specified by the user. This checking provides some protection against a malicious server sending unexpected filenames, but it comes at a risk of rejecting wanted files due to differences between client and server wildcard expansion rules. For this reason, this also adds a new -T flag to disable the check. reported by Harry Sintonen fix approach suggested by markus@; has been in snaps for ~1wk courtesy deraadt@ OpenBSD-Commit-ID: 00f44b50d2be8e321973f3c6d014260f8f7a8eda
* upstream: tweak previous;jmc@openbsd.org2019-01-221-4/+4
| | | | OpenBSD-Commit-ID: d2a80e389da8e7ed71978643d8cbaa8605b597a8
* upstream: Forgot to add -J to the synopsis.tb@openbsd.org2019-01-221-1/+2
| | | | OpenBSD-Commit-ID: 26d95e409a0b72526526fc56ca1caca5cc3d3c5e
* upstream: Add a -J option as a shortcut for -o Proxyjump= to scp(1)tb@openbsd.org2019-01-221-2/+15
| | | | | | | | and sftp(1) to match ssh(1)'s interface. ok djm OpenBSD-Commit-ID: a75bc2d5f329caa7229a7e9fe346c4f41c2663fc
* upstream: reorder CASignatureAlgorithms, and add them to thejmc@openbsd.org2018-09-211-2/+3
| | | | | | various -o lists; ok djm OpenBSD-Commit-ID: ecb88baecc3c54988b4d1654446ea033da359288
* upstream: Deprecate UsePrivilegedPort now that support for runningdtucker@openbsd.org2018-07-191-3/+2
| | | | | | | | | | | | | ssh(1) setuid has been removed, remove supporting code and clean up references to it in the man pages We have not shipped ssh(1) the setuid bit since 2002. If ayone really needs to make connections from a low port number this can be implemented via a small setuid ProxyCommand. ok markus@ jmc@ djm@ OpenBSD-Commit-ID: d03364610b7123ae4c6792f5274bd147b6de717e
* upstream: sort previous;jmc@openbsd.org2018-06-111-2/+2
| | | | OpenBSD-Commit-ID: 27d80d8b8ca99bc33971dee905e8ffd0053ec411
* upstream: add a SetEnv directive to ssh_config that allows settingdjm@openbsd.org2018-06-091-2/+3
| | | | | | | | | | | environment variables for the remote session (subject to the server accepting them) refactor SendEnv to remove the arbitrary limit of variable names. ok markus@ OpenBSD-Commit-ID: cfbb00d9b0e10c1ffff1d83424351fd961d1f2be
* upstream: some cleanup for BindInterface and ssh-keyscan;jmc@openbsd.org2018-02-261-2/+3
| | | | OpenBSD-Commit-ID: 1a719ebeae22a166adf05bea5009add7075acc8c
* upstream commitjmc@openbsd.org@openbsd.org2017-10-301-11/+12
| | | | | | | | | tweak the uri text, specifically removing some markup to make it a bit more readable; issue reported by - and diff ok - millert OpenBSD-Commit-ID: 8b56a20208040b2d0633536fd926e992de37ef3f
* upstream commitmillert@openbsd.org2017-10-231-19/+22
| | | | | | | | | | Add URI support to ssh, sftp and scp. For example ssh://user@host or sftp://user@host/path. The connection parameters described in draft-ietf-secsh-scp-sftp-ssh-uri-04 are not implemented since the ssh fingerprint format in the draft uses md5 with no way to specify the hash function type. OK djm@ Upstream-ID: 4ba3768b662d6722de59e6ecb00abf2d4bf9cacc
* upstream commitnaddy@openbsd.org2017-05-081-2/+3
| | | | | | | restore mistakenly deleted description of the ConnectionAttempts option ok markus@ Upstream-ID: 943002b1b7c470caea3253ba7b7348c359de0348
* upstream commitjmc@openbsd.org2017-05-081-8/+2
| | | | | | | remove now obsolete protocol1 options from the -o lists; Upstream-ID: 828e478a440bc5f9947672c392420510a362b3dd
* upstream commitdjm@openbsd.org2017-05-011-11/+3
| | | | | | | | exterminate the -1 flag from scp ok markus@ Upstream-ID: 26d247f7065da15056b209cef5f594ff591b89db
* upstream commitjmc@openbsd.org2016-07-171-2/+3
| | | | | | | | | - add proxyjump to the options list - formatting fixes - update usage() ok djm Upstream-ID: 43d318e14ce677a2eec8f21ef5ba2f9f68a59457
* upstream commitjmc@openbsd.org2016-07-081-3/+3
| | | | | | sort the -o list; Upstream-ID: 1a97465ede8790b4d47cb618269978e07f41f8ac
* upstream commitmarkus@openbsd.org2016-05-191-2/+3
| | | | | | add IdentityAgent; noticed & ok jmc@ Upstream-ID: 4ba9034b00a4cf1beae627f0728da897802df88a
* upstream commitjmc@openbsd.org2015-10-061-2/+3
| | | | | | some certificatefile tweaks; ok djm Upstream-ID: 0e5a7852c28c05fc193419cc7e50e64c1c535af0
* upstream commitmarkus@openbsd.org2015-07-151-2/+3
| | | | | | | | Turn off DSA by default; add HostKeyAlgorithms to the server and PubkeyAcceptedKeyTypes to the client side, so it still can be tested or turned back on; feedback and ok djm@ Upstream-ID: 8450a9e6d83f80c9bfed864ff061dfc9323cec21
* upstream commitdjm@openbsd.org2015-01-301-2/+3
| | | | | | | | | | Add a ssh_config HostbasedKeyType option to control which host public key types are tried during hostbased authentication. This may be used to prevent too many keys being sent to the server, and blowing past its MaxAuthTries limit. bz#2211 based on patch by Iain Morgan; ok markus@
* upstream commitjmc@openbsd.org2015-01-271-2/+2
| | | | sort previous;
* upstream commitdjm@openbsd.org2015-01-261-2/+3
| | | | | correct description of UpdateHostKeys in ssh_config.5 and add it to -o lists for ssh, scp and sftp; pointed out by jmc@
generated by cgit v1.2.3 (git 2.39.1) at 2025-01-18 08:40:51 +0100