Help!!
Steve Butler
sbutler@fchn.com
Wed Mar 27 17:52:01 2002
I wish I knew! So far it is happening only with one client. But it =
appears
to happen every time they need to send the file. So far they can resend =
it
up to four times before all the bytes show up.=20
I'm pointing the finger at the client's software. So far they are =
unwilling
to take my suggestion and attempt to a UNIX to Linux FTP so see if that =
is
more reliable. Every so often they don't spot the size discrepancy and =
my
automated script emails me that gpg returned a status of '2'. Hand =
attempts
to decrypt usually so that problem that started this thread (zlib =
inflate)
but have shown various other errors. =20
So, if in doubt, have the client verify the length of the file!
Stephen M Butler
Oracle Administrator
First Choice Health Network
206-268-2309
sbutler@fchn.com GnuPG: 8B17 7384 AB86 D67F 7612 3587 5715 C880 1B32 =
D54B=20
kg7je@attbi.com GnuPG: 8A25 9726 D439 758D D846 E5D4 282A 5477 0385 =
81D8=20
-----Original Message-----
From: Oyvind A. Holm [mailto:sunny@sunbase.org]
Sent: Wednesday, March 27, 2002 8:23 AM
To: gnupg-users@gnupg.org
Subject: RE: Help!!
On 2002-03-27 07:27-0800 Steve Butler wrote:
> 2. The file was sent in Binary mode from a WSFTP client to a Linux
> host. One or more (but not all) <CR> characters where dropped. The
> file is at least one byte short.
In _binary_ mode??? Sheesh, that's an ugly one! Is this a common flaw
with the WSFTP clients, or a specific version? Bugs like that cannot be
accepted, it has to be corrected ASAFP.
=D8yvind
+-------------------------------------------------------------------+
| OpenPGP: 0x629022EB 2002-02-24 =D8yvind A. Holm <sunny@sunbase.org> |
| Fingerprint: DBE9 8D44 67F7 42AC 2CA1 7651 724E 9D53 6290 22EB |
+----------| En dag uten Cola er som en hund uten svane. |----------+
_______________________________________________
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users
CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, =
is for the sole use of the intended recipient(s) and may contain =
confidential and privileged information. Any unauthorized review, use, =
disclosure or distribution is prohibited. If you are not the intended =
recipient, please contact the sender by reply e-mail and destroy all =
copies of the original message.