Eric Dorland (Fr 04 Jan 2013 08:05:32 CET):
> Control: tags -1 fixed-upstream
…
> > Is there still time to do get a new release into Wheezy?
>
> Unfortunately it's been too late for Wheezy for a while. But if anyone
> feels strongly they can appeal to the release managers that this
> should be i
Control: tags -1 fixed-upstream
* Werner Koch (w...@gnupg.org) wrote:
> On Tue, 6 Nov 2012 22:50, h...@schlittermann.de said:
>
> > Before I started exploring how to run full tests … what is the supposed
> > procedure?
>
> Viewing the decrypted text. I was able to see that the ciphertext was
>
On Wed, 7 Nov 2012 10:18, h...@schlittermann.de said:
> Meanwhile I gave it a try, but wasn't successful. Could be because of
> some interferences with the installed 2.0, or some scdaemon was still
> running, or because it just didn't work. So I'll stop investing time into the
> master branch?
O
On Wed, 7 Nov 2012 10:16, cor...@debian.org said:
> --with-agent-pgm=/home/yaperez/tmp/gnupg/bin/gpg-agent
> --with-scdaemon-pgm=/home/yaperez/tmp/gnupg/bin/scdaemon
> --with-pinentry-pgm=/usr/bin/pinentry-gtk-2 && make
For scdaemon and pinentry I usually do it at runtime in gpg-agent.conf
pine
On mer., 2012-11-07 at 10:18 +0100, Heiko Schlittermann wrote:
> > Is there still time to do get a new release into Wheezy?
> This I can't answer, it depends on Yves-Alexis, I think.
I don't have any word on this. I'm just a gnupg2 user here.
--
Yves-Alexis
--
To UNSUBSCRIBE, email to debian
Hello,
Werner Koch (Mi 07 Nov 2012 09:24:54 CET):
> On Tue, 6 Nov 2012 22:50, h...@schlittermann.de said:
>
> > Before I started exploring how to run full tests … what is the supposed
> > procedure?
>
Ah, I thought there is some more extensive testing procedure.
> > I just built the stable-2
On mer., 2012-11-07 at 09:24 +0100, Werner Koch wrote:
> On Tue, 6 Nov 2012 22:50, h...@schlittermann.de said:
>
> > Before I started exploring how to run full tests … what is the supposed
> > procedure?
>
> Viewing the decrypted text. I was able to see that the ciphertext was
> correctly sent
On Tue, 6 Nov 2012 22:50, h...@schlittermann.de said:
> Before I started exploring how to run full tests … what is the supposed
> procedure?
Viewing the decrypted text. I was able to see that the ciphertext was
correctly sent to the card and then card returned an error because it is
one of the
Hello Werner,
Werner Koch (Di 06 Nov 2012 15:01:42 CET):
> Hi,
>
> I just pushed fixes to master and stable 2.0.
>
> Allow decryption with card keys > 3072 bit
>
> * scd/command.c (MAXLEN_SETDATA): New.
> (cmd_setdata): Add option --append.
> * g10/call-agent.c (agent_scd_p
On Tue, 6 Nov 2012 12:24, cor...@debian.org said:
> Hmh, I didn't have any problem generating keys on-card nor moving keys
> to card on Debian sid. The only thing I needed to check is to
> use /usr/bin/gpg2 and not /usr/bin/gpg, since /u/b/gpg is unfortunately
Generating keys worked for me using
Hi,
I just pushed fixes to master and stable 2.0.
Allow decryption with card keys > 3072 bit
* scd/command.c (MAXLEN_SETDATA): New.
(cmd_setdata): Add option --append.
* g10/call-agent.c (agent_scd_pkdecrypt): Use new option for long data
* scd/app-openpgp.c (struct
On mar., 2012-11-06 at 11:21 +0100, Werner Koch wrote:
> On Tue, 6 Nov 2012 10:24, cor...@debian.org said:
>
> > For gnupg2 maintainers: this is about an issue with gnupg2 not beeing
> > able to decrypt stuff encrypted for 4096b keys on OpenPGP smartcards.
>
> If you look at the back of the card
On Tue, 6 Nov 2012 10:24, cor...@debian.org said:
> For gnupg2 maintainers: this is about an issue with gnupg2 not beeing
> able to decrypt stuff encrypted for 4096b keys on OpenPGP smartcards.
If you look at the back of the cards you will notice a limit of 3072
;-). To stop people complaining
Control: reassign -1 gnupg2
Control: retitle -1 fixed length for assuan messages is too short for 4096
decryption keys
For gnupg2 maintainers: this is about an issue with gnupg2 not beeing
able to decrypt stuff encrypted for 4096b keys on OpenPGP smartcards.
This is caused by messages sent over a
Hi,
thank you for responding :)
Yves-Alexis Perez (Mo 05 Nov 2012 18:45:00 CET):
> On mar., 2012-10-23 at 13:12 +0200, Heiko Schlittermann wrote:
> > Package: libassuan0
> > Version: 2.0.3-1
> > Severity: important
> > Tags: upstream patch
> >
> > I used a 4096bit key for encryption (using the
On mar., 2012-10-23 at 13:12 +0200, Heiko Schlittermann wrote:
> Package: libassuan0
> Version: 2.0.3-1
> Severity: important
> Tags: upstream patch
>
> I used a 4096bit key for encryption (using the GnuPG crypto-stick).
> Encryption worked, but decryption didn't work (gpg2 didn't find
> the secre
Package: libassuan0
Version: 2.0.3-1
Severity: important
Tags: upstream patch
I used a 4096bit key for encryption (using the GnuPG crypto-stick).
Encryption worked, but decryption didn't work (gpg2 didn't find
the secret key.)
gpg2 uses libassuan to talk to some daemons/agents.
gpg (1.x) worked,
17 matches
Mail list logo
