From: Chris Roehrig <croehrig@house.org>
To: cygwin@cygwin.com
Subject: Re: scp and ssh 'cat' stalls at 64k bytes
Date: Sat, 24 Jun 2023 00:47:09 -0700 [thread overview]
Message-ID: <052a88cd-7a5f-ced2-70bf-faa1a3c90e2c@house.org> (raw)
In-Reply-To: <837e1b67-4847-b324-6472-3a6ff69bb709@Shaw.ca>
On 2023-06-23 22:35, Brian Inglis wrote:
> On 2023-06-23 20:19, Dan Harkless via Cygwin wrote:
> Before you resort to trawling through source, did you try a fresh
> Cygwin install (either to a different directory, or after temporarily
> moving your current tree)? Sometimes, e.g. if you use the same
> "packages" directory between two different versions of Windows, I've
> found that Cygwin can get screwed up in strange ways.
Good thought. Yes, one of my machines is a new Win11 with a fresh Cygwin.
> On each system have you run /usr/bin/ssh-user-config, and run
> /usr/bin/ssh-host-config from an elevated admin account, customized or
> added host keys appropriately to /etc/sshd_config, /etc/ssh_config,
> ~/.ssh/{config,known_hosts,authorized_keys}, /etc/ssh/ssh_host_*_key.pub?
>
I think they're all set up correctly. ssh/slogin/rsync/scp all work
great and have been for years. It's only this weird issue in specific
cases with files > 64K.
next prev parent reply other threads:[~2023-06-24 7:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-23 6:26 Chris Roehrig
2023-06-23 15:28 ` Brian Inglis
2023-06-23 19:41 ` Chris Roehrig
2023-06-23 23:07 ` Voris, Ben
[not found] ` <bced83bb-58c5-f2a8-bc03-578d6d9fd749@house.org>
[not found] ` <MW4PR84MB1684E6210C73D34ED2223319FE23A@MW4PR84MB1684.NAMPRD84.PROD.OUTLOOK.COM>
2023-06-24 0:19 ` Chris Roehrig
2023-06-24 1:26 ` Dan Harkless
2023-06-24 1:59 ` Chris Roehrig
2023-06-24 2:19 ` Dan Harkless
2023-06-24 5:35 ` Brian Inglis
2023-06-24 6:16 ` Dan Harkless
2023-06-24 7:47 ` Chris Roehrig [this message]
2023-06-24 7:12 ` Kevin Schnitzius
2023-06-24 8:45 ` Chris Roehrig
2023-07-05 19:20 ` Andrey Repin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=052a88cd-7a5f-ced2-70bf-faa1a3c90e2c@house.org \
--to=croehrig@house.org \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).