On 05/07/2016 03:41 AM, Mike Ingle wrote:
> I tried my inputs with eddsa instead of ecdsa and it worked. Not sure if
> there is still a bug to report?
> Thank you for the workaround.
No, it's not a workaround. It is the correct way to specify the
algorithm. Well, my description in the previous m
I sent the following message several days ago and am not sure it actually went.
I am, therefore, sending it again.
Thanks.
It appears that I made a mess of my new install.
I am on a Mac, running OS 10.11.4.
I had been using PGP ( v9.7.1?) on a previous older Mac but, of course, that
will not
> Could anyone please help.
Probably not. You're using a version of GnuPG that's 14 years old with
many known bugs. Please upgrade to at least GnuPG 1.4. If the problem
persists, we can probably help track down what's happening -- but our
ability to help with GnuPG 1.2.1 is pretty minimal.
___
On Friday, May 6, 2016, Werner Koch wrote:
>
>
> Not my quote; I can't remember its origin, though.
>
Takeoff of Monty Python & Spanish Inquisition, perhaps?
Avi
--
Sent from Gmail Mobile
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lis
I tried my inputs with eddsa instead of ecdsa and it worked. Not sure if
there is still a bug to report?
Thank you for the workaround.
On 5/6/2016 1:58 AM, NIIBE Yutaka wrote:
On 05/06/2016 05:59 AM, Mike Ingle wrote:
Key-Type: ecdsa
Name-Real: t 6
Subkey-Curve: Curve25519
Subkey-Usage: enc
On Fri, 6 May 2016 16:12, youcanli...@gmail.com said:
> proprietary and/or non-free/non-libre software. I feel people can
> discuss almost anything if handled in a thoughtful, respectful manner.
Take care ... Nobody expects the Free Software police!
SCNR,
Werner
p.s
Not my quote; I can't
Hi,
We all know that generating new keys currently takes a lot of time,
especially on headless environments. There are several suggestions
on the internet about how to improve this, but most of them are criticized
for making the security weaker (by lowering the quality of randomness
that they gene
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 05/06/2016 09:57 AM, flapflap wrote:
> flapflap:
>> Peter Lebbing:
>>> On 05/05/16 17:17, Werner Koch wrote:
Well, this is not an FSF sponsored list. I never received
any money or other resources from the FSF.
>>>
>>> gnu.org lists Gnu
On 06/05/16 15:22, flapflap wrote:
> Previously, I believed to have read these rules in the "Information for
> Maintainers of GNU Software" [0] but could not find it any more.
Perhaps chapter 13: [1]
> A GNU package should not recommend use of any non-free program, nor should
> it require a non-
flapflap:
> Peter Lebbing:
>> On 05/05/16 17:17, Werner Koch wrote:
>>> Well, this is not an FSF sponsored list. I never received any money or
>>> other resources from the FSF.
>>
>> gnu.org lists GnuPG as a "GNU package", a part of the GNU Project. I
>> kinda assumed that that would imply some fo
Peter Lebbing:
> On 05/05/16 17:17, Werner Koch wrote:
>> Well, this is not an FSF sponsored list. I never received any money or
>> other resources from the FSF.
>
> gnu.org lists GnuPG as a "GNU package", a part of the GNU Project. I
> kinda assumed that that would imply some form of involvement
On Fri, 6 May 2016 10:58, gni...@fsij.org said:
> I got success with this:
>
> Key-Type: eddsa
To make this more clear: This is e*d*dsa and not e*c*dsa. The names are
very similar but they are different algorithms.
Salam-Shalom,
Werner
--
Die Gedanken sind f
On 05/06/2016 05:59 AM, Mike Ingle wrote:
> Key-Type: ecdsa
> Name-Real: t 6
> Subkey-Curve: Curve25519
> Subkey-Usage: encrypt
> Subkey-Type: ecdh
> Name-Email: t@6
> Key-Curve: Ed25519
> Key-Usage: sign
> Key-Length: 255
> %commit
I got success with this:
Key-Type: e
Am 05.05.2016 um 22:59 schrieb Mike Ingle:
> If I create a key manually I get:
> GOOD
> pub ed25519/C850D9A5 2016-05-05 [SC]
> uid [ultimate] test 3
> sub cv25519/22967908 2016-05-05 [E]
> which works, as the roles are properly assigned to the main and sub key.
>
> If I create one in
14 matches
Mail list logo
