(GnuPG) 1.4.2 - Signature Verification Issue
VINEETA DESHMUKH (CRGL-THIRDPARTY.COM)
VINEETA_DESHMUKH at CRGL-THIRDPARTY.COM
Fri Oct 25 16:53:05 CEST 2013
Thank you for your prompt response. The files which are sent by JP Morgan are using ascii mode of transfer and the files are ascii armored as well.
Let me know if you have any other questions.
From: David Shaw [mailto:dshaw at jabberwocky.com]
Sent: Thursday, October 24, 2013 7:11 PM
To: VINEETA DESHMUKH (CRGL-THIRDPARTY.COM)
Cc: gnupg-users at gnupg.org; Kari Ingebritsen
Subject: Re: (GnuPG) 1.4.2 - Signature Verification Issue
On Oct 24, 2013, at 4:47 PM, "VINEETA DESHMUKH (CRGL-THIRDPARTY.COM)" <VINEETA_DESHMUKH at CRGL-THIRDPARTY.COM> wrote:
> I am facing an issue with the Signature verification from one of our clients - JP Morgan. We currently have FTP+encryption+signature of all the files which they send to us. However, they recently have migrated their FTP servers to connect through secure FTP with SSH keys. This is where we are facing problems when it comes to signature verification to a few files which are placed through their automated process. I am pasting successful and failed logs for your reference.
The first thing to ask whenever people put FTP and signatures together is whether the files are transferred via ascii or binary mode in FTP, and the related question of whether the files you are transferring are in ascii armor or not. Transferring non-armored files via ascii mode in FTP can cause various corruption problems.
More information about the Gnupg-users