Hello,
I use this syntax to sign files in a script--it works without problems,
but when trying to manually sign a file, I'm receiving the following
result:
gpg --batch --armor -keyring /Publib/.../ARP_pubring.gpg
--secret-keyring /Prodlib/.../ARP_secring.gpg --local-user 55EC3D41\!
--output
Michael Quigley/TheWay wrote on 08/23/2011 09:51:59 AM:
Hello,
I use this syntax to sign files in a script--it works without
problems, but when trying to manually sign a file, I'm receiving the
following result:
gpg --batch --armor -keyring /Publib/.../ARP_pubring.gpg --secret-
On Tue, Aug 23, 2011 at 11:15:27AM -0400, michaelquig...@theway.org wrote:
gpg: conflicting commands
$
I'm sure I'm overlooking something simple, but I'm just not seeing it
today.
Okay -- I found the dash in clear-sign--which should read clearsign.
Of course I find it shortly after
On Tue Aug 23, 2011 at 09:51:59 -0400, michaelquig...@theway.org wrote:
Hello,
I use this syntax to sign files in a script--it works without problems,
but when trying to manually sign a file, I'm receiving the following
result:
gpg --batch --armor -keyring /Publib/.../ARP_pubring.gpg
On Tue, 23 Aug 2011 15:51, michaelquig...@theway.org said:
gpg --batch --armor -keyring /Publib/.../ARP_pubring.gpg
This is the same as -k -e -y -r -i -n -g - thus you are asking for a key
lising and encryption ... - Use two dashes.
Back to the fingerprint
