On Fri, Apr 06, 2007 at 09:57:50AM -0700, mmorg76114 wrote:
>
> Hey everyone,
>
> I have a bit of a strange error here, hoping someone has run into this
> before. I have two different machines with GPG on them, and recently (about
> a month ago) they started behaving differently. I used to have a
Charly Avital wrote:
> I installed 2.0.3 using a binary installer prepared by Ben Donnachie,
> because I didn't succeed to compile the code.
It's statically linked to libgcrypt-1.2.4
> I'm waiting for some feedback from Ben. He watches this list, but he
> also has a day job, so I'll have to wait.
Werner Koch wrote:
> You need to create an account first. Sorry for that but it avoids
> spam and helps to make people think before they use the tarcker as a
> help forum. I add a comment.
Yeah, understandable. I had created an account and still didn't see
any obvious way to add a comment. I m
On Mon, 16 Apr 2007 18:59, [EMAIL PROTECTED] said:
> I can't help with the translation, but I do know that when creating
> spec files for Fedora and Red Hat, the spec file is to be encoded in
> either ascii or utf8.
Okay.
> (I'd add this to the bug directly, but it's early for me and I'm not
> s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello gnupg-users,
keyserver-options auto-key-retrieve
I have this in my gpg.conf and it worked like a charm but it suddenly
stops???
- --
Henk M. de Bruijn
__
The Bat! Natural E-
On Mon, 16 Apr 2007 18:42, [EMAIL PROTECTED] said:
> gpg: WARNING: some OpenPGP programs can't handle a DSA key with this
> digest size
> dsa.c:187: failed assertion `nbits >= 512 && nbits <= 1024'
> Abort trap
It won't help to fix it right now because the stable libgcrypt has no
support for DSA-
On Mon, 16 Apr 2007 18:54, [EMAIL PROTECTED] said:
> Seems like this fixes the problem. mpi_write allocates 2 bytes less it
> should.
> It shouldn't be security relevant on usual architectures, but it is a bug for
> sure
Thanks. Fixed in SVN revision 4480.
Salam-Shalom,
Werner
_
Werner Koch wrote:
> Hi,
>
> we have this
>
>https://bugs.g10code.com/gnupg/issue676
>
> bug report in the tracker. I'd appreciate if someone else speaking
> Polish can check the supplied patch
>
> https://bugs.g10code.com/gnupg/file84/corrected-polish.diff.gz
>
> so that I can apply i
Am Montag 16 April 2007 schrieb Werner Koch:
> Hi,
>
> I think I found the problem: In g10/gpg.h you find
>
> /* Number of bits we accept when reading or writing MPIs. */
> #define MAX_EXTERN_MPI_BITS 16384
>
> when writing it out with build-packet.c:mpi_write, we use a buffer if
> that length
Werner Koch wrote:
> we have this
>
>https://bugs.g10code.com/gnupg/issue676
>
> bug report in the tracker. I'd appreciate if someone else speaking
> Polish can check the supplied patch
>
> https://bugs.g10code.com/gnupg/file84/corrected-polish.diff.gz
I can't help with the translation,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Alexander Feigl wrote the following on 4/16/07 6:15 PM:
[...]
>
> Can confirm this on x86-linux with libgcrypt 1.2.4 but the key is imported as
> 0xB61454A3 here (Gentoo Linux).
>
> Furthermore if I import the key with 1.4.x and use gpg --list-k
Hi,
I think I found the problem: In g10/gpg.h you find
/* Number of bits we accept when reading or writing MPIs. */
#define MAX_EXTERN_MPI_BITS 16384
when writing it out with build-packet.c:mpi_write, we use a buffer if
that length. It should error out for too long values but there might b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Werner Koch wrote the following on 4/16/07 6:07 PM:
> On Mon, 16 Apr 2007 16:10, [EMAIL PROTECTED] said:
>
>> So, I have to link gpg2, and try again - my problem is: I am not sure
>> how to do it.
>
> Running make in the build directory should do t
Am Montag 16 April 2007 schrieb Charly Avital:
> Werner Koch wrote the following on 4/16/07 2:48 PM:
> [...]
>
> > GPG 2.x uses libgcrypt for crypto operations and this includes keyid
> > calculations and converting of big integers. It really would make sense
> > to check again using the latest st
On Mon, 16 Apr 2007 16:10, [EMAIL PROTECTED] said:
> So, I have to link gpg2, and try again - my problem is: I am not sure
> how to do it.
Running make in the build directory should do the trick. If nothing
happens, remove gpg2 first. Then do a make install or test directly in
the build directo
Werner Koch wrote the following on 4/16/07 2:48 PM:
[...]
> GPG 2.x uses libgcrypt for crypto operations and this includes keyid
> calculations and converting of big integers. It really would make sense
> to check again using the latest stable libgcrypt (1.2.4). If libgcrypt
> has been statical
Hi,
we have this
https://bugs.g10code.com/gnupg/issue676
bug report in the tracker. I'd appreciate if someone else speaking
Polish can check the supplied patch
https://bugs.g10code.com/gnupg/file84/corrected-polish.diff.gz
so that I can apply it.
Salam-Shalom,
Werner
__
On Sun, 15 Apr 2007 16:28, [EMAIL PROTECTED] said:
> Thanks for helping work this out. It does indeed seem to be a GPG 2.x
> bug that does not happen in the GPG 1.4.x code. That simplifies where
GPG 2.x uses libgcrypt for crypto operations and this includes keyid
calculations and converting of
Stoddard Richard wrote the following on 4/16/07 1:10 PM:
> Thanks. I think I understand it all, and will tackle it this evening.
I am glad you do, thanks: I was not sure my explanations were clear enough.
> The problem I had when generating the key is that even though I
> checked 4096 as the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Stoddard Richard wrote the following on 4/16/07 1:10 PM:
> Thanks. I think I understand it all, and will tackle it this evening.
I am glad you do, thanks: I was not sure my explanations were clear enough.
> The problem I had when generating the k
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thanks. I think I understand it all, and will tackle it this evening.
The problem I had when generating the key is that even though I
checked 4096 as the size, only the subkey is 4096. I didn't have an
option for the primary key.
- --
Rick
On A
21 matches
Mail list logo
