Re: Algorithm 11

-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 Charly Avital wrote: >> I built it from source from gnupg.org. No SHA224, no bzip2. > I believe it is because the src that is posted does not include > libgcrypt 1.3.0 It doesn't include any libgcrypt. The configure script said I didn't have it,

Re: algortihm 11

On Tue, 3 Jul 2007 19:03, [EMAIL PROTECTED] said: > I should add, though, that this bug is fixed and will be in the next > gpg2 release. I hope to get it out this week but I need to sort out some license problems first. Salam-Shalom, Werner ___

Re: Algorithm 11

Andrew Berg wrote the following on 7/3/07 7:30 PM: [...] > I built it from source from gnupg.org. No SHA224, no bzip2. I believe it is because the src that is posted does not include libgcrypt 1.3.0 Charly ___ Gnupg-users mailing list Gnupg-users@

Re: algortihm 11

On Tue, Jul 03, 2007 at 12:18:36PM -0400, David Shaw wrote: > On Tue, Jul 03, 2007 at 08:41:09AM -0500, Andrew Berg wrote: > > John Clizbe wrote: > > > Also, this is a *known error*, see this thread, 'Algorithm 11 not > > > available', > > > http://lists.gnupg.org/pipermail/gnupg-users/2007-April/0

Re: Algorithm 11

-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 Charly Avital wrote: > Under MacOS 10.4.9, I run gpg2 from a binary installer compiled by > Ben Donnachie: > > item > 'mac-gpg 2.0.4-2.zip that uses libgcrypt 1.3.0 with support for > SHA224:

Re: Algorithm 11

On Tue, 3 Jul 2007 16:30, [EMAIL PROTECTED] said: > Hash: MD5 (H1), SHA1 (H2), RIPEMD160 (H3), TIGER192 (H6), SHA256 (H8), > SHA384 (H9), SHA512 (H10), SHA224 (H11) ^^ It depends on the installed version of libgcrypt. 1.3.x comes with SHA224.

Re: algortihm 11

On Tue, Jul 03, 2007 at 08:41:09AM -0500, Andrew Berg wrote: > John Clizbe wrote: > > Also, this is a *known error*, see this thread, 'Algorithm 11 not > > available', > > http://lists.gnupg.org/pipermail/gnupg-users/2007-April/030974.html > > > > > > It stems from the fact that the cipher library

Algorithm 11 [was: FireGPG (correction)]

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 John Clizbe wrote the following on 7/3/07 2:55 AM: [...] > It stems from the fact that the cipher library in gpg2 does not have SHA-224 > (hash algorithm 11) enabled. Under MacOS 10.4.9, I run gpg2 from a binary installer compiled by Ben Donnachi

Re: algortihm 11

-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 John Clizbe wrote: > Also, this is a *known error*, see this thread, 'Algorithm 11 not > available', > http://lists.gnupg.org/pipermail/gnupg-users/2007-April/030974.html > > > It stems from the fact that the cipher library in gpg2 does not > hav

Re: Ownership of usb device with udev.

> SYSFS{idProduct}=="5115", SYSFS{idVendor}=="04e6", MODE="660", > GROUP="myspecialgroup" In fact, what puzzled me is that I already had all this written down. The problem was that there was some \newline between two of the keys. This splitted off the line in two, and it was not parsed correctly

Re: Ownership of usb device with udev.

Werner Koch a écrit : > On Tue, 3 Jul 2007 11:30, [EMAIL PROTECTED] said: > >> My main problem is that I do not really understand how udev works. I >> understood there was lots of renaming involved. And with all these >> renamings, I do not really know how to make ownership changes. > > Nor do I

Re: Ownership of usb device with udev.

Guillaume Yziquel wrote: > Werner Koch a écrit : >> On Fri, 29 Jun 2007 11:38, [EMAIL PROTECTED] said: >> >>> Visibly, purging pcscd does not solve the problem. Concerning >>> permissions, I guess I have some work to do: >> Indeed. That is your problem. Use lsusb to figure out where the SCR335 >>

Re: Ownership of usb device with udev.

On Tue, 3 Jul 2007 11:30, [EMAIL PROTECTED] said: > My main problem is that I do not really understand how udev works. I > understood there was lots of renaming involved. And with all these > renamings, I do not really know how to make ownership changes. Nor do I. The whole hotplug stuff just w

Ownership of usb device with udev.

Werner Koch a écrit : > On Fri, 29 Jun 2007 11:38, [EMAIL PROTECTED] said: > >> Visibly, purging pcscd does not solve the problem. Concerning >> permissions, I guess I have some work to do: > > Indeed. That is your problem. Use lsusb to figure out where the SCR335 > is attached and the manually

Re: Broken pipe?

Hi, Werner Koch schrieb: > On Fri, 29 Jun 2007 12:07, [EMAIL PROTECTED] said: > >> I apologize for the weight of this message. > > As I alrady said: You have no permission to write to the USB device. This seems to be the result of several half-correct howtos for installing the cardreader. Recent