Hi,
if you compile from git repo as Josef said it will work 100% with 4096
bit RSA keys.
Regards,
Marcos A. Lenharo
On 28-02-2013 22:08, Josef Schneider wrote:
> On Thu, Feb 28, 2013 at 10:34 PM, Peter Lebbing
> wrote:
>> On 27/02/13 22:58, Anonymous wrote:
>>> So I should be able to import t
On Thu, Feb 28, 2013 at 10:34 PM, Peter Lebbing wrote:
> On 27/02/13 22:58, Anonymous wrote:
>> So I should be able to import the key...but not use it unless it is
>> 3072 bits or less?
>
> If we're all talking about RSA here, I think so.
Using an 4096 bit RSA key _should_ work if you compile the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 02/28/2013 09:33 AM, Kristian Fiskerstrand wrote:
| for a service that specifically targets the OpenPGP community, I
| consider using the OpenPGP WoT more appropriate than any CA
| Corporation.
Kristian,
I certainly understand that perspective,
On 27/02/13 22:58, Anonymous wrote:
> So I should be able to import the key...but not use it unless it is
> 3072 bits or less?
If we're all talking about RSA here, I think so.
> I run gpg2 --card-status, and I get a lot of information, but I don't
> see an entry "OpenPGP version." What I do see
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Mark,
A belated answer to this email, as I'm reading through the backlog of
emails.
On 02/26/2013 03:43 PM, Mark H. Wood wrote:
> On Mon, Feb 25, 2013 at 05:54:34PM -0500, Peter Loshin wrote:
>> 3. On using a keyserver with HKPS support: when I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Doug,
On 02/28/2013 06:35 PM, Doug Barton wrote:
> Phil,
>
> Could this curl issue be the cause of this error that I've been
> seeing the last few days:
>
> gpg: sending key 1A1ABC84 to hkp server pool.sks-keyservers.net
> gpgkeys: HTTP post
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 02/28/2013 10:23 AM, Kristian Fiskerstrand wrote:
| On 02/28/2013 07:01 PM, Doug Barton wrote:
|> On 02/28/2013 09:44 AM, Kristian Fiskerstrand wrote: | Hi Doug,
|> |
|
|
| ...
|
|> Yes, I'm talking to different servers (as would be expected).
|>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 02/28/2013 07:01 PM, Doug Barton wrote:
> On 02/28/2013 09:44 AM, Kristian Fiskerstrand wrote: | Hi Doug, |
>
...
> Yes, I'm talking to different servers (as would be expected). Just
> tried it a few times ...
>
At least that explains it. Fo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 02/28/2013 09:44 AM, Kristian Fiskerstrand wrote:
| Hi Doug,
|
|
| On 02/28/2013 06:35 PM, Doug Barton wrote:
|> Phil,
|
|> Could this curl issue be the cause of this error that I've been
|> seeing the last few days:
|
|> gpg: sending key 1A1ABC8
Phil,
Could this curl issue be the cause of this error that I've been seeing
the last few days:
gpg: sending key 1A1ABC84 to hkp server pool.sks-keyservers.net
gpgkeys: HTTP post error 22: The requested URL returned error: 417
Expectation Failed
gpg: sending key D5B2F0FB to hkp server pool.s
On Wed, 27 Feb 2013 12:03:22 +0100
Josef Schneider wrote:
> Hello,
> with the current version of GPG 2 you can import 4096bit keys to a
> OpenPGP smartcard version 2.0.
> There is a bug in GPG2 that prevents it from decrypting data with a
> key longer than 3072bit on a OpenPGP smartcard. This sho
On 2013-02-28 at 09:12 +0100, Niels Laukens wrote:
> On 2013-02-28 00:50, Phil Pennock wrote:
> > The best fix is to use gpg with a real cURL library.
>
> I'm currently using a downloaded binary from gpgtools.org. I don't see
> libcurl in the list of shared objects used by the binary (otool -L,
>
On 2013-02-27 at 10:57 +0100, Niels Laukens wrote:
> Apologies for cross-posting to both mailing lists, but since I got
> replies via both ways I feel this is the easiest way to sync them.
Current status: Kristian and I have debugged and he found the core
issue. If I load down my server, we can s
On 2013-02-28 09:36, Phil Pennock wrote:
> On 2013-02-28 at 09:12 +0100, Niels Laukens wrote:
>> On 2013-02-28 00:50, Phil Pennock wrote:
>>> The best fix is to use gpg with a real cURL library.
>>
>> I'm currently using a downloaded binary from gpgtools.org. I don't see
>> libcurl in the list of s
Thanks Phil for the very clear summary of the problem!
On 2013-02-28 00:50, Phil Pennock wrote:
> The best fix is to use gpg with a real cURL library.
I'm currently using a downloaded binary from gpgtools.org. I don't see
libcurl in the list of shared objects used by the binary (otool -L,
Mac's e
15 matches
Mail list logo
