Re: GPA - import keys more easily?..

[Peter Lebbing]

On 10/12/15 21:00, Dark Penguin wrote:
> (or not even seeing it, because I think it would normally close
> immediately after the program has finished running).

Oh, okay, I misunderstood your request. I thought you wanted to invoke
GPA from the command line, since you called it a command line option.

But I suppose you want a file association so GPA is launched on an .asc
or .gpg file, and subsequently takes the most logical action for the
actual content of the file (show key info with an option to import for
keys, decrypt and verify for encrypted/signed data).

Cheers,

Peter.

-- 
I use the GNU Privacy Guard (GnuPG) in combination with Enigmail.
You can send me encrypted mail if you want some privacy.
My key is available at 

___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: GPA - import keys more easily?..

[Peter Lebbing]

On 10/12/15 21:00, Dark Penguin wrote:
> And I usually import the keys from email attachments, which I know
> are correct, because I've helped them set up PGP and I've created
> their email account. I just want to be able to have them imported
> with simply opening them with GPA and not have to save them
> somewhere, then look for them in the "Import keys..." dialog, and
> then delete them.

Since I'm constantly making wrong assumptions on implied contexts here,
just let me make this explicit: we are talking about e-mail clients for
which no OpenPGP plugins/extensions/etc. exist, like webmail and such,
right? Because I just have Enigmail handling keys in e-mail, in my
Icedove (Thunderbird).

HTH,

Peter.

-- 
I use the GNU Privacy Guard (GnuPG) in combination with Enigmail.
You can send me encrypted mail if you want some privacy.
My key is available at 

___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: Error message "gpg: Can't check signature: Broken public key"

[Brian Minton]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

I got the following message:
rejected by import screener

Here's more detail (gpg 2.1.8 on Windows 8):

C:\Users\mintonb>gpg -vvv --recv 0x1712BC461AF778E4
gpg: using character set 'CP437'
gpg: data source: http://pgp.mit.edu:80
gpg: armor: BEGIN PGP PUBLIC KEY BLOCK
gpg: armor header: Version: SKS 1.1.5
gpg: armor header: Comment: Hostname: pgp.mit.edu
# off=0 ctb=99 tag=6 hlen=3 plen=269
:public key packet:
version 4, algo 1, created 1415500876, expires 0
pkey[0]: [2048 bits]
pkey[1]: [17 bits]
keyid: 251BCCEB547B7194
# off=272 ctb=b4 tag=13 hlen=2 plen=4
:user ID packet: "MFPA"
# off=278 ctb=89 tag=2 hlen=3 plen=322
:signature packet: algo 1, keyid 251BCCEB547B7194
version 4, created 1415582356, md5len 0, sigclass 0x13
digest algo 10, begin of digest 24 eb
hashed subpkt 27 len 1 (key flags: 01)
hashed subpkt 11 len 10 (pref-sym-algos: 13 9 8 12 7 3 11 10 4 2)
hashed subpkt 21 len 6 (pref-hash-algos: 10 9 8 11 3 2)
hashed subpkt 22 len 4 (pref-zip-algos: 3 2 1 0)
hashed subpkt 30 len 1 (features: 01)
hashed subpkt 23 len 1 (key server preferences: 80)
hashed subpkt 2 len 4 (sig created 2014-11-10)
hashed subpkt 25 len 1 (primary user ID)
subpkt 16 len 8 (issuer key ID 251BCCEB547B7194)
data: [2048 bits]
# off=603 ctb=89 tag=2 hlen=3 plen=322
:signature packet: algo 1, keyid 251BCCEB547B7194
version 4, created 1441185092, md5len 0, sigclass 0x13
digest algo 10, begin of digest f2 40
hashed subpkt 27 len 1 (key flags: 01)
hashed subpkt 11 len 10 (pref-sym-algos: 13 9 8 12 7 3 11 10 4 2)
hashed subpkt 21 len 6 (pref-hash-algos: 10 9 8 11 3 2)
hashed subpkt 22 len 4 (pref-zip-algos: 3 2 1 0)
hashed subpkt 30 len 1 (features: 01)
hashed subpkt 23 len 1 (key server preferences: 80)
hashed subpkt 2 len 4 (sig created 2015-09-02)
hashed subpkt 25 len 1 (primary user ID)
subpkt 16 len 8 (issuer key ID 251BCCEB547B7194)
data: [2042 bits]
# off=928 ctb=b4 tag=13 hlen=2 plen=18
:user ID packet: "0x251BCCEB547B7194"
# off=948 ctb=89 tag=2 hlen=3 plen=319
:signature packet: algo 1, keyid 251BCCEB547B7194
version 4, created 1416188694, md5len 0, sigclass 0x13
digest algo 10, begin of digest a3 61
hashed subpkt 27 len 1 (key flags: 01)
hashed subpkt 30 len 1 (features: 01)
hashed subpkt 23 len 1 (key server preferences: 80)
hashed subpkt 2 len 4 (sig created 2014-11-17)
hashed subpkt 11 len 10 (pref-sym-algos: 13 9 8 12 7 3 11 10 4 2)
hashed subpkt 21 len 6 (pref-hash-algos: 10 9 8 11 3 2)
hashed subpkt 22 len 4 (pref-zip-algos: 3 2 1 0)
subpkt 16 len 8 (issuer key ID 251BCCEB547B7194)
data: [2048 bits]
# off=1270 ctb=89 tag=2 hlen=3 plen=319
:signature packet: algo 1, keyid 251BCCEB547B7194
version 4, created 1441185086, md5len 0, sigclass 0x13
digest algo 10, begin of digest 58 9d
hashed subpkt 27 len 1 (key flags: 01)
hashed subpkt 30 len 1 (features: 01)
hashed subpkt 23 len 1 (key server preferences: 80)
hashed subpkt 11 len 10 (pref-sym-algos: 13 9 8 12 7 3 11 10 4 2)
hashed subpkt 21 len 6 (pref-hash-algos: 10 9 8 11 3 2)
hashed subpkt 22 len 4 (pref-zip-algos: 3 2 1 0)
hashed subpkt 2 len 4 (sig created 2015-09-02)
subpkt 16 len 8 (issuer key ID 251BCCEB547B7194)
data: [2045 bits]
# off=1592 ctb=89 tag=2 hlen=3 plen=319
:signature packet: algo 1, keyid 251BCCEB547B7194
version 4, created 1416145056, md5len 0, sigclass 0x13
digest algo 10, begin of digest 30 1c
hashed subpkt 2 len 4 (sig created 2014-11-16)
hashed subpkt 27 len 1 (key flags: 01)
hashed subpkt 11 len 10 (pref-sym-algos: 13 9 8 12 7 3 11 10 4 2)
hashed subpkt 21 len 6 (pref-hash-algos: 10 9 8 11 3 2)
hashed subpkt 22 len 4 (pref-zip-algos: 3 2 1 0)
hashed subpkt 30 len 1 (features: 01)
hashed subpkt 23 len 1 (key server preferences: 80)
subpkt 16 len 8 (issuer key ID 251BCCEB547B7194)
data: [2044 bits]
# off=1914 ctb=b4 tag=13 hlen=2 plen=81
:user ID packet: "2014-667rhzu3dc-lists-gro...@riseup.net <2014-667rhzu3dc-lists
- -gro...@riseup.net>"
# off=1997 ctb=89 tag=2 hlen=3 plen=319
:signature packet: algo 1, keyid 251BCCEB547B7194
version 4, created 1441159293, md5len 0, sigclass 0x13
digest algo 10, begin of digest 96 2d
hashed subpkt 27 len 1 (key flags: 01)
hashed subpkt 11 len 10 (pref-sym-algos: 13 9 8 12 7 3 11 10 4 2)
hashed subpkt 21 len 6 (pref-hash-algos: 10 9 8 11 3 2)
hashed subpkt 22 len 4 (pref-zip-algos: 3 2 1 0)
hashed subpkt 30 len 1 (features: 01)
hashed subpkt 23 len 1 (key server preferences: 80)
hashed subpkt 2 len 4 (sig 

Re: Error message "gpg: Can't check signature: Broken public key"

[MFPA]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi


On Thursday 10 December 2015 at 9:46:31 AM, in
, Brad Rogers
wrote:




> GnuPG v1.4.19

1.4.x should verify the signature from my RSA subkey but report "Can't
check signature: unknown pubkey algorithm" for the signature from my
EDDSA subkey.


> There's also one
> other difference; The signature is no longer inline,
> but attached.  Not that I expect that is relevant.


Yes, I accidentally used PGP/MIME instead of inline.



- --
Best regards

MFPA  

Vegetarian: Indian word for lousy hunter!!!
-BEGIN PGP SIGNATURE-

iQF8BAEBCgBmBQJWa0INXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRCM0FFN0VDQTlBOEM4QjMwMjZBNUEwRjU2
QjdDNzRDRUIzMUYyNUYwAAoJEGt8dM6zHyXwtWsH/0pus4Fby0eWHiXwRMKeUStc
UiTWl/rE/w6wmnDA6gTqUuDZQSQoiJxS37xJjAHJmE0OESC/1IjUA1pTLsq+Hdwh
UkXUerOPjazzJhoLhMxAhCXshzxov89wARbeOSqr+J2IHukrgOt6tJ7jfCbmx6mm
S/9LJNyCQ81GoGAaMq2HvFnyOatAH7K0pIi9swehZ8XyorBQc7CeziO6NVgxsNAz
ieFKCXJYGdS32z6QAg7Et/pIzKU2xNstciVLNa5AXYZ2/5Z5wOvsPsahRCaSm+w9
bomPBfbyiFGp3dtPe8OBDGORdFjfqIHEwfkgTw3i+QImiGs8R3Ke/qZw4ojFC2iI
vgQBFgoAZgUCVmtCE18UgAAuAChpc3N1ZXItZnByQG5vdGF0aW9ucy5vcGVu
cGdwLmZpZnRoaG9yc2VtYW4ubmV0MzNBQ0VENEVFOTEzNEVFQkRFNkE4NTA2MTcx
MkJDNDYxQUY3NzhFNAAKCRAXErxGGvd45CUpAPwNDCXop+tmAs1zatvZDU9unmrE
7s9UEsiv+dhjvjZmwgD/WBOn4QBjSjp+lsChmRszLD/0UKS8QL/cC3L7lj+eWQU=
=xLr5
-END PGP SIGNATURE-


___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: Error message "gpg: Can't check signature: Broken public key"

[Brad Rogers]

On Fri, 11 Dec 2015 21:35:56 +
MFPA <2014-667rhzu3dc-lists-gro...@riseup.net> wrote:

Hello MFPA,

>1.4.x should verify the signature from my RSA subkey but report "Can't
>check signature: unknown pubkey algorithm" for the signature from my
>EDDSA subkey.

Unfortunately, GPGME and Claws Mail (probably) interfere with the error
reporting.  No matter.

-- 
 Regards  _
 / )   "The blindingly obvious is
/ _)radnever immediately apparent"
Loaded like a freight train flyin' like an aeroplane
Nightrain - Guns 'N' Roses


pgp2ObXJklwD2.pgp
Description: OpenPGP digital signature
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: GPA - import keys more easily?..

[Dark Penguin]

(or not even seeing it, because I think it would normally close
immediately after the program has finished running).


Oh, okay, I misunderstood your request. I thought you wanted to invoke
GPA from the command line, since you called it a command line option.

But I suppose you want a file association so GPA is launched on an .asc
or .gpg file, and subsequently takes the most logical action for the
actual content of the file (show key info with an option to import for
keys, decrypt and verify for encrypted/signed data).


Yes; I can set up a file association myself, but when I open someone's 
.asc public key in GPA, I see a "File manager" window with an option to 
decrypt it, which doesn't make sense. I want either GPA to automatically 
understand that this is a public key (which is not hard at all, because 
there is the PGP header written in plaintext), or at least to be able to 
open keys with GPA with some option to tell it that this is a key, not 
an encrypted message, if it can not see that without my help - maybe 
with a commandline option. Or at the very least, they should just add an 
"Import key" option in that file manager for such cases - that would 
also be fine by me. I just want to be able to import a key I'm already 
looking at without having to look for it again in the "Import key..." 
dialog.


There may be "workarounds" like installing some plugins for some mail 
clients, but I'm happy with GPA, and I want to use GPA, and installing a 
plugin (and probably switching to a compatible email client) and setting 
it up and getting used to it just to be able import keys a couple of 
seconds quicker does not really make sense.


PGP for Windows does that from time immemorial, naturally. I would 
expect at least this much from a frontend for encryption software for an 
operating system which, unlike Windows, is actually concerned about 
security, and I believe our new "converts" from Windows would expect it 
too, and I can't believe it's still not there by now. =/



--
darkpenguin

___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: Please consider joining Bountysource Salt to collect recurring donations

[Werner Koch]

On Fri, 11 Dec 2015 10:40, pe...@digitalbrains.com said:

> While I think it's a good idea to include an alias, I think you should
> do that consistently for all the menus, otherwise "Documentation" and
> "Related software" are going to end up even more hidden ;).

Frankly, I think we should change the style of the menu again because
we now have two identical entries in the sub-menu.


Shalom-Salam,

   Werner

-- 
Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.


___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: Please consider joining Bountysource Salt to collect recurring donations

[Andrey Utkin]

On 10.12.2015 18:49, Robert J. Hansen wrote:
> ... So, yeah.  I'm thinking this is not a credible source for
> fundraising.  Arduino and GNOME, projects with *far* greater visibility,
> get $0 a month from Bountysource.  I find it hard to believe we'd do
> much better.
> 
> I think this is something best avoided.
> 

The Salt project has released this spring or this autumn, I don't
remember for sure.
There's competing project Gratipay (former Gittip, rebranded recently),
and some more, so there's also a fragmentation.
Yes you are right that these platforms (and recurring donation to FOSS
projects in general) is far from being as popular as it should be. But
basically this is a network, and the value of network is bound to number
of members in it. If nobody is in, nobody considers joining worth. The
more time passes, the more projects and backers join and the more is
money flow.
I was surprised to become first backer of FFmpeg project, which was
already set up :)

Also I am not aware how much hassle is it for you to set up your
donation-collecting account on these networks, but I hope it's not that
painful.

Werner, Donate menu entry got better, but there's another issue - when
cursor pointer moves from menu header down to menu entries, menu
dropdown tends to disappear, it takes many attempts to catch it :)

Thanks for all the comments.



signature.asc
Description: OpenPGP digital signature
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users