David Shaw wrote the following on 6/27/05 12:32 AM:
[...]
> I'm afraid I don't know what this means. GnuPG has no such 'long
> headers', so I assume you're calling it from some front end.
Indeed, because 'long headers' has nothing to do with GnuPG per se, it
is a MUA viewing option that displays
On Sun, Jun 26, 2005 at 11:55:52PM -0400, Charly Avital wrote:
> According to man gpg:
> ---
> Set the `for your eyes only' flag in the message. This
> causes GnuPG to refuse to save the file unless the --output
> option is given, and PGP to use the "secure viewer" with
According to man gpg:
---
Set the `for your eyes only' flag in the message. This
causes GnuPG to refuse to save the file unless the --output
option is given, and PGP to use the "secure viewer" with a
Tempest-resistant font to display the message. This option
override
New keyanalyze results are available at:
http://keyserver.kjsl.com/~jharris/ka/2005-06-26/
Signatures are now being checked using keyanalyze+sigcheck:
http://dtype.org/~aaronl/
Earlier reports are also available, for comparison:
http://keyserver.kjsl.com/~jharris/ka/
Even earlier month
On Fri, Jun 24, 2005 at 05:52:07PM +0200, Alain Bench wrote:
> [copy to libiconv author]
>
> Hello,
>
> On Saturday, May 21, 2005 at 9:21:01 AM +0200, [EMAIL PROTECTED] wrote:
>
> > when setting utf-8 for cmd.exe, gpg switches back to its default
> > character set. In cmd.exe I do the follw
On Jun 26, 2005, at 5:15 PM, Tom McCune wrote:
[...]
I don't know about Macs, but on Windows, the option is there when
using
Current Window usage from PGPtray.
I have found how to do it, it requires to "force" PGP to display the
window where encryption key(s) can be selected manually to
While carrying out some tests with GnuPG and the options
--for-our-eyes-only and --output [filename], within the macgpg-users list,
I tried to decrypt a test message composed with MacGPG (GnuPG for the Mac)
1.4.2rc2 configured with these two options.
The received message could be decrypted usi
