On Sat, Jul 30, 2005 at 02:20:35PM -0400, Jason Harris wrote:
> On Wed, Jul 27, 2005 at 09:53:27AM +0200, Werner Koch wrote:
>
> > We are pleased to announce the availability of a new stable GnuPG
> > release: Version 1.4.2
>
> > What's New
> > ===
>
> > * New experimental HKP keyse
Hi,
I'm trying to send my keys to the Tor pgp-keyservers.
For that I use:
gpg --keyserver=x-hkp://yod73zr3y6wnm2sw.onion
--keyserver-options=honor-http-proxy,broken-http-proxy,http-proxy=http://192.168.64.1:8118/
--send-key 1f28d8ae
but that doesn't work!
I then get:
gpg: sending
Hi,
I propose the following:
split-up gpg into a front-end and a shared library. The shared library
then contains all code for handling the keyring-files, doing the
crypto-stuff, etc. while the front-end (just a normal executable)
contains the code for parsing commandlines and calling the shared
l
On Wed, Jul 27, 2005 at 09:53:27AM +0200, Werner Koch wrote:
> We are pleased to announce the availability of a new stable GnuPG
> release: Version 1.4.2
> What's New
> ===
> * New experimental HKP keyserver helper that uses the cURL
> library. It is enabled via the configure
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Timo Schulz wrote:
> Patrick Dickey wrote:
>
>> into the Windows\system32 directory. When I tried to do regsvr,
>> I had to move the gpgexch.dll file to the Windows\System32 folder
>> also.
>
>
> What Windows version do you use? I've never seen that
Version 1.1.2 of GPGee has been released. This release fixes a newly
identified security issue.
In previous versions of GPGee, the mechanism that was intended to
overwrite passphrases after they were used had a flaw that prevented
this from occuring. This makes is more likely (though still not v
Patrick Dickey wrote:
into the Windows\system32 directory. When I tried to do regsvr, I had
to move the gpgexch.dll file to the Windows\System32 folder also.
What Windows version do you use? I've never seen that this step is
needed and I tested it on 98 and XP.
What is the error or why do
On Fri, 29 Jul 2005 20:56:58 -0400, David Shaw said:
> cat /good/random/source | gpg --enarmor
There is even an easier way:
gpg --gen-random -a 1 12
Returns 16 bytes of armored random; i.e. actual 12 bytes. This uses
the same algorithm gpg uses for session keys. By using 2 instead of 1
gpg w
