macgpg2 update! gpg2 working under Mac OS X with smartcard support!

2006-07-14 Thread Benjamin Donnachie
Binary install packages are now available for Mac OS X; PowerPC only at this stage with Universal binaries to follow. Please follow the instructions at http://www.py-soft.co.uk/~benjamin/download/mac-gpg/MacOS%20gpg-agent%20and%20pinentry%20HOWTO.txt This package brings the power of gnupg v1.9.

Re: How to verify the file was successfully encrypted...

2006-07-14 Thread Samuel ]slund
On Thu, Jul 13, 2006 at 08:31:39PM -0400, Vladimir Doisan wrote: > The user base of GnuPG is huge, and any serious bugs in the code will > be weeded out very quickly by the beta testers and early adopters. > Invalid encryptions is a VERY serious bug. Sadly this is not true enough, as has been illu

Re: How to verify the file was successfully encrypted...

2006-07-14 Thread Benny Helms
On Thu, 2006-07-13 at 23:15 +0200, Samuel ]slund wrote: > If I read this thread right you actually wnt to make a decryption and > compare the results and you do _not_ want to keep the private key on > that machine. > > Could you do something creative with --show-session-key to be able to > dec

Re: How to verify the file was successfully encrypted...

2006-07-14 Thread Benny Helms
On Sat, 2006-07-15 at 00:05 +0930, Alphax wrote: > Better than that, if you get GPG to sign the file when it encrypts it > (using a passwordless key/subkey) and/or use the MDC option, you'll be > able to do this more reliably... Thank you, Alphax! I'll look into that. Benny ___

Re: Manual for GnuPG 1.4.4

2006-07-14 Thread Santiago José López Borrazás
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 El 14/07/06 19:58, John B escribió: > Thanks, Laurent! Idem... The manual is very compression ;-) - -- Slds de Santiago José López Borrazás. Admin de hackindex.com/.es Conocimientos avanzados en seguridad informática. Conocimientos avanzados en

Re: How to verify the file was successfully encrypted...

2006-07-14 Thread Benny Helms
On Fri, 2006-07-14 at 15:07 +0200, Janusz A. Urbanowicz wrote: > > Can you please explain what you mean by "check the gpg's rc after the > > encryption run?" I'm unfamilar with the meaning of "rc" in this case. > > return code > > every unix code returns an numerical code which by convention mea

Re: [Sks-devel] key too large?

2006-07-14 Thread Peter Palfrader
On Fri, 14 Jul 2006, David Shaw wrote: > On Fri, Jul 14, 2006 at 04:14:43PM +0200, Peter Palfrader wrote: > > On Thu, 13 Jul 2006, David Shaw wrote: > > > > > > gpg (GnuPG) 1.4.4-cvs, looks like a snapshot built around April 5th, > > > > probably r4114. > > > > > > > > I don't see the problem on

Re: Manual for GnuPG 1.4.4

2006-07-14 Thread John B
On Thursday 13 July 2006 04:15, Laurent Jumet wrote: > Hello ! > > Here, you can download the manual for GnuPG 1.4.4 formated in a > printable way, in 12 pages: > > http://users.skynet.be/laurent.jumet/MyMan_GnuPG-144.pdf Thanks, Laurent! ___ Gn

Re: Use of OpenPGP smartcard on MS Windows

2006-07-14 Thread John Clizbe
David Picon Alvarez wrote: > Hi, > > Is it possible to use the OpenPGP smartcard on a GnuPG version compiled for > MS Windows such as the ones available at gnupg.org? What should I know about > smart card readers, drivers, et al, before trying to do this? Pointers > appreciated. OpenPGP Smart car

Re: [Sks-devel] key too large?

2006-07-14 Thread David Shaw
On Fri, Jul 14, 2006 at 04:14:43PM +0200, Peter Palfrader wrote: > On Thu, 13 Jul 2006, David Shaw wrote: > > > > gpg (GnuPG) 1.4.4-cvs, looks like a snapshot built around April 5th, > > > probably r4114. > > > > > > I don't see the problem on a different host with what is quite likely > > > r418

Use of OpenPGP smartcard on MS Windows

2006-07-14 Thread David Picon Alvarez
Hi, Is it possible to use the OpenPGP smartcard on a GnuPG version compiled for MS Windows such as the ones available at gnupg.org? What should I know about smart card reders, drivers, et al, before trying to do this? Pointers appreciated. --David. ___

Re: How to verify the file was successfully encrypted...

2006-07-14 Thread Alphax
George Ross wrote: >>> BTW, why are you encrypting these files anyway? If someone broke into >>> your computer they could just steal the crypto key too. >> Excellent question! Truth be told, as soon as they are encrypted, >> they're being moved to another server in another location, and then are

Re: [Sks-devel] key too large?

2006-07-14 Thread Peter Palfrader
On Thu, 13 Jul 2006, David Shaw wrote: > > gpg (GnuPG) 1.4.4-cvs, looks like a snapshot built around April 5th, > > probably r4114. > > > > I don't see the problem on a different host with what is quite likely > > r4189. > > There are no meaningful changes in gpgkeys_hkp between those two > revi

Re: How to verify the file was successfully encrypted...

2006-07-14 Thread Janusz A. Urbanowicz
On Wed, Jul 12, 2006 at 10:59:52AM -0600, Benny Helms wrote: > On Wed, 2006-07-12 at 12:25 +0200, Janusz A. Urbanowicz wrote: > > On Tue, Jul 11, 2006 at 01:38:23PM -0600, Benny Helms wrote: > > > What is your actual threat model here? > > > > The simplest answer is to check gpg's rc after the en

Re: Calculating Buffer Size

2006-07-14 Thread David Shaw
On Wed, Jul 12, 2006 at 04:19:36PM -0400, Adam Schreiber wrote: > Is there a way to calculate the unencrypted or unsigned size of an ASCII > armored encrypted message given the size of the message and the length > of the key? Yes, but not if compression is turned on (as it is by default). Factors

Calculating Buffer Size

2006-07-14 Thread Adam Schreiber
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Is there a way to calculate the unencrypted or unsigned size of an ASCII armored encrypted message given the size of the message and the length of the key? Cheers, Adam Schreiber - -- Why isn't all of your email protected? http://gnupg.org http://eni

Re: How to verify the file was successfully encrypted...

2006-07-14 Thread George Ross
> > BTW, why are you encrypting these files anyway? If someone broke into > > your computer they could just steal the crypto key too. > > Excellent question! Truth be told, as soon as they are encrypted, > they're being moved to another server in another location, and then are > being burned to