Hello,
is there any way to change the expiration date of mainkey AND ALL attached
subkeys by one action only (and not key-by-key)?
Source:
pub 4096R/ erzeugt: 2014-12-09 verfällt: 2015-10-04 Aufruf: C
Vertrauen: unbekannt Gültigkeit: unbekannt
sub 4096R/F0E664
The type of UID that proves problematic when you include the angle
brackets in your search is this:
$ gpg2 -k c...@example.org
pub 2048R/17C05EBD 2014-08-13 [expires: 2015-04-14]
uid [ unknown] c...@example.org
$ gpg2 -k ""
gpg: error reading key: No public key
It's about an UID without
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi
On Tuesday 7 April 2015 at 4:34:05 AM, in
, Ben McGinnes wrote:
> The function and operation you're after is reasonable,
> no arguments there, my question is whether this is
> something which is actually a fault with GPG or if it's
> your MUA.
On 7/04/2015 7:57 pm, Peter Lebbing wrote:
> The type of UID that proves problematic when you include the angle
> brackets in your search is this:
>
> $ gpg2 -k c...@example.org
> pub 2048R/17C05EBD 2014-08-13 [expires: 2015-04-14]
> uid [ unknown] c...@example.org
>
> $ gpg2 -k ""
> gpg:
On 7/04/2015 10:39 pm, MFPA wrote:
>
> We are talking at cross-purposes.
>
> When I look at that UID:-
>
> Ben McGinnes
>
> I see angle brackets around the email address, in the usual way.
>
> I was talking about what happens when the angle brackets are not
> there.
>
> If I generate a
Hello Daniel,
> Do you want to require multiple people to come together to use that
> secret key? or do you want them each to have the ability to use the key
> independently from each other?
The objective is require multiple people to use that secret key. Yes
> The answer about what to do would
On Tue 2015-04-07 08:39:57 -0400, MFPA wrote:
> I was talking about what happens when the angle brackets are not
> there.
>
> If I generate a key with the UID of:-
>
>Test20150407 u...@example.com
>
> and try to encrypt an email to u...@example.com it fails.
The above is neither an RFC 5322 ad
On 07/04/15 14:56, Ben McGinnes wrote:
> Let me see if I've got this right ... the issue is one which can
> only occur when the key owner has deliberately overridden the
> defaults by using the "allow-freeform-uid" option
GnuPG implements the OpenPGP standard. What hoops the users need to jump
thr
On Tue 2015-04-07 09:14:09 -0400, Alfredo Palhares wrote:
> [dkg wrote:]
>> Do you want to require multiple people to come together to use that
>> secret key? or do you want them each to have the ability to use the key
>> independently from each other?
>
> The objective is require multiple people
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi
On Tuesday 7 April 2015 at 2:14:55 PM, in
, Daniel Kahn Gillmor
wrote:
> On Tue 2015-04-07 08:39:57 -0400, MFPA wrote:
>> I was talking about what happens when the angle brackets are not
>> there.
>> If I generate a key with the UID of:-
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi
On Tuesday 7 April 2015 at 2:14:09 PM, in
, Alfredo Palhares wrote:
> I am open to any suggestions.
Maybe somebody more knowledgeable than me can comment on whether
"Shamir's Secret Sharing Scheme" [0] might be something relevant to
mention
Hello,
FYI: I managed to solve my issue by using pure opensc-pkcs11. OpenPGP cards
seem to be supported by opensc. At least, I managed to sign an SSH public
key of a server with the key on the card.
Best regards,
Bolesław Tokarski
___
Gnupg-users mailin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi
On Tuesday 7 April 2015 at 1:56:01 PM, in
, Ben McGinnes wrote:
> Let me see if I've got this right ... the issue is one
> which can only occur when the key owner has
> deliberately overridden the defaults by using the
> "allow-freeform-uid"
On 8/04/2015 12:41 am, MFPA wrote:
>
>> allowing them to drop the standard format of "name
>> " and then they're shocked that doing so might
>> produce unintended consequences?
>
> Don't know about "shocked", but unintended consequences for a
> non-standard UID scheme was indeed the issue.
>
> T
On 8/04/2015 12:04 am, MFPA wrote:
> On Tuesday 7 April 2015 at 2:14:55 PM, in
> , Daniel Kahn Gillmor
> wrote:
>
>> We know how to structure a proper name-addr and an addr-spec, and
>> it's not difficult. If you want an e-mail address to be
>> recognizable to automated tools, you should structur
Alfredo,
I don't have any personal experience with splitting the key. What we do at my
employer is split the secret key passphrase. Yes, this is a manual process but
very secure. For highly important keys we assign six trusted individuals, three
have defined one half of the passphrase and three
On Tue, 7 Apr 2015 11:27, gnupgpac...@on.yourweb.de said:
> is there any way to change the expiration date of mainkey AND ALL attached
> subkeys by one action only (and not key-by-key)?
No. Please file a feature requests at bugs.gnupg.org. if you think this
is important.
Shalom-Salam,
Wer
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The Debian project solves this by having the secret key shared using
(https://en.wikipedia.org/wiki/Shamir%27s_Secret_Sharing).
https://ftp-master.debian.org/keys.html
On Tue, Apr 7, 2015 at 1:29 PM, Bob (Robert) Cavanaugh
wrote:
> Alfredo,
>
Hello,
I have been looking around a bit, but couldn't find the answer. I
would like to do the following with GPG if possible, thanks in
advance:
Assume we would like to hold a small election where no one should be
able to know which political party anyone have voted for.
User A, user B, and user
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi
On Tuesday 7 April 2015 at 7:15:13 PM, in
,
jan.svens...@hush.com wrote:
> Hello,
> I have been looking around a bit, but couldn't find the
> answer. I would like to do the following with GPG if
> possible, thanks in advance:
> Assume we wou
20 matches
Mail list logo
