Hello,
I'm just trying GnuPG 1.4.10 for Windows now, and I'm seeing this odd
problem.
When I try to do gpg --edit-key mykeyid, I see something like the following:
gpg (GnuPG) 1.4.10; Copyright (C) 2008 Free Software Foundation, Inc.
This is free software: you are free to change and redistribute
And here's screenshot just in case:
http://www.facebook.com/photo.php?pid=2627732l=0243cc15e8id=661728650
Another thing I've tested was to rollback 1.4.9 to recreate problem, with no
luck, and replacing iconv.dll from 1.4.9 didn't help either, so it seems
like definitely problem started happening
Hi,
GnuPG 1.4.10 has been announced yesterday, including a binary for
Microsoft windows:
gnupg-w32cli-1.4.10.exe (1531k)
gnupg-w32cli-1.4.10.exe.sig
GnuPG compiled for Microsoft Windows and OpenPGP signature.
This is a command line only version; the source files are the
Just thought of something here...
$ gpg --version
gpg (GnuPG) 1.4.10rc1
NOTE: THIS IS A DEVELOPMENT VERSION!
It is only intended for test purposes and should NOT be
used in a production environment or with production keys!
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+:
On Thu, 3 Sep 2009 08:36, hide...@gmail.com said:
Doesn't this (C) 2008 supposed to say (C) 2009?
Good catch but too late for 1.4.10.
Shalom-Salam,
Werner
--
Die Gedanken sind frei. Auschnahme regelt ein Bundeschgesetz.
___
Gnupg-users
Hi,
the broken binary build of GnuPG 1.4.10 for Microsoft Windows has been
fixed. The new installer has a new file name and includes a small
source patch to document the applied fix.
It can be downloaded from ftp://ftp.gnupg.org/gcrypt/binary/
gnupg-w32cli-1.4.10a.exe (1539k)
Good afternoon all,
A business partner is asking us to encrypt and sign our files with PGP
before uploading it on their server.
I decided to use GnuPG as it is said to be compatible.
After having generated keys and added their key to our keyring, I used,
as said in the man page :
gpg -se -r
However, it doesn't seem to meet their requirements. Here's the reply of
our partner :
The file is first encrypted and then signed. Not encrypted and signed
in the same run.
It's possible that your partner has phrased things poorly. It may be
your partner meant to say, We want the file to
Here is a UI enhancement request: In the edit-key menu, typing uid *
selects all UID's. Currently, I have to type uid # for every UID
individually. Typing uid by itself currently deselects all UID's.
___
Gnupg-users mailing list
After my prior note, I tried updating the libassuan package from 1.0.4 to
1.0.5 using the entire ftp'd from the gnupg site.
With the environment set as follows:
export CC=gcc
export LIBPATH=/usr/lib:/usr/ccs/lib:/usr/local/lib
export
When I run configure, I now have in my environment:
export CC=gcc
export CFLAGS=-g -O2 -mcpu=powerpc
export LIBPATH=/usr/lib:/usr/ccs/lib:/usr/local/lib
When running the configure for GnuPG, I execute:
./configure
2009/9/3 Bob Wyatt bwyatt_...@comcast.net:
What am I missing? Any advice?
Please don't keep starting new threads - just post a reply to your
existing message.
What options did you use to compile pth?
Ben
___
Gnupg-users mailing list
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Joseph Oreste Bruni wrote:
Here is a UI enhancement request: In the edit-key menu, typing uid *
selects all UID's. Currently, I have to type uid # for every UID
individually. Typing uid by itself currently deselects all UID's.
I just
13 matches
Mail list logo
