From: "Caduff Claudio DFRKSTA" <claudio.caduff@ag.ch>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Cryptic characters at 4kboundary after ssh transfer
Date: Sat, 09 Dec 2017 15:24:00 -0000 [thread overview]
Message-ID: <7E58E0C408F8B34EA21B64036E63EAFE50398E3E@SPWEX006> (raw)
Hi
We use cygwin for an encrypted transfer between network zones.
- used Servers: mixed (all 64-bit): Windows 2008 R2 Enterprise / Windows 2012 R2 Standard
- used Cygwin package version: mixed: 2.774 / 2.877
- used cygwin1.dll version: mixed 1.7.17 / 1.7.32 / 1.7.33 / 2.7.0
- used sshd version (info from sshd_config): mixed: 1.87 / 1.93
Since about one year we observe the following situation:
In some (about 1 of 100) of the transferred files there are cryptic characters (always 8 Bytes), always at an address which begins after 4k.
- This (as far as we know) did never happen with files smaller than 5MB
- There are no error messages
- we don't know if there were such 'miss-transfers' earlier and we suppose that we don't find all of these files because an automated process is analyzing thes files and the effect ist depending on the logical position of these 8 Bytes.
- we cannot reproduce the error: if we transfer the same original file again it is transferred correctly.
Does anybody know such an issue or even a solution?
Best Regards,
Claudio
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next reply other threads:[~2017-12-08 13:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-09 15:24 Caduff Claudio DFRKSTA [this message]
2017-12-09 22:51 ` Richard H Lee
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=7E58E0C408F8B34EA21B64036E63EAFE50398E3E@SPWEX006 \
--to=claudio.caduff@ag.ch \
--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).