On 3/7/12 9:41 PM, John Clizbe wrote:
> This is due to two reasons:
Let's not forget:
3) This would introduce legal headaches. So long as SKS has no
crypto code, it doesn't need to conform to crypto export laws.
___
Gnupg-users mailing list
Gnupg-
Faramir wrote:
> El 06-03-2012 16:58, Peter Lebbing escribió:
> ...
>> The keyservers don't do any validation on revocation certificates;
>> anyone who feels like it can add /invalid/ revocation certificates
>> to your key to annoy you. But as soon as OpenPGP software imports
>> the key from the ke
Am Donnerstag, 8. März 2012, 00:39:11 schrieb Faramir:
> El 07-03-2012 18:24, MFPA escribió:
> ...
>
> >> Only your private key can generate the revocation certificate,
> >
> > Can't you add another key as a designated revoker, and then
> > generate the revocation certificate with that other priv
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
El 07-03-2012 18:24, MFPA escribió:
...
>> Only your private key can generate the revocation certificate,
>
>
> Can't you add another key as a designated revoker, and then
> generate the revocation certificate with that other private key?
You ar
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi
On Wednesday 7 March 2012 at 12:31:11 AM, in
, Faramir wrote:
> Only your private key can generate the revocation
> certificate,
Can't you add another key as a designated revoker, and then generate
the revocation certificate with that oth
On 03/07/2012 03:31 PM, Ingo Klöcker wrote:
> Hmm. I guess you are right. Just a minor remark: To my knowledge it is
> not possible to get the passphrase out of gpg-agent. The whole point of
> gpg-agent is that it encapsulates all operations involving the secret
> key and the passphrase in order
On Tuesday 06 March 2012, Daniel Kahn Gillmor wrote:
> On 03/05/2012 04:36 PM, Ingo Klöcker wrote:
> > 4. He has left his laptop unlocked and unattended for a very short
> > period of time and he is using gpg-agent with a cache-ttl > 0.
> >
> > I have verified that one can generate a revocation ce
On 03/07/2012 04:15 AM, kwadronaut wrote:
> I noticed that some tools (i.e. Enigmail) don't give you the option to
> specify a revocation reason. I haven't uploaded my revoked key as of yet,
> so how should I edit it to specify a reason?
If your frontend doesn't give you a feature you want, you
Dear all,
> because you've made that file executable.
> chmod u-x /home/alastair/.gnupg/gpg.conf
I assume this one here is the "best" solution (from [1]):
> mkdir "$HOME/.gnupg"
> chown -R "$USER" "$HOME/.gnupg"
> chmod -R -N "$HOME/.gnupg" 2> /dev/null; # for OS X ACLs
> chmod -R u+rwX,go= "$HO
On 07/03/12 14:56, Alastair Langwell wrote:
> gpg: WARNING: unsafe ownership on configuration file
> `/home/alastair/.gnupg/gpg.conf'
because you've made that file executable.
chmod u-x /home/alastair/.gnupg/gpg.conf
signature.asc
Description: OpenPGP digital signature
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I fixed the issue with a little help from one of the IT gurus at work.
I ran the following:
sudo chmod -R 700 ~/
sudo chown -R alastair:alastair ~/
This fixed the issue although now any command I run from gpg spits out
the following complaint before
Oh I understand - my apologies, I'll put everything up into the thread when I
get a chance.
Sent from my iPhone
On 7 Mar 2012, at 08:52, Werner Koch wrote:
> Hi,
>
> if you post an URL which is the actual body of your question, please
> also copy and paste the relevant parts from that web pag
On 07/03/12 09:19, Alastair Langwell wrote:
> Thanks to you and Robert for getting back to me. However this
> unfortunately didn't solve the problem. I ran:
>
> chown alastair:alastair ~/.gnupg/
>
> and
>
> chown alastair:alastair ~/.gnupg/*
>
> Then I tried root:alastair and alastair:root but
On Mon, 17 Oct 2011 20:11:29 +0200, Werner Koch wrote:
> of the whole system. We prepared a short paper; if you are interested
Some suggestions and questions, some are applicable to the paper while
others might be more suited for a FAQ section on the website:
* More pictures.
* You're suggesti
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
As per Werner's email below, please find the issue pasted out below:
Hi,
I'm using Seamonkey on Lubuntu 11.10.
Basically, any time I try to decrypt an email from Enigmail (Seamonkey
2.4.1/Enigmail 1.3.3/GnuPG 1.4.11) I get the following error:
Error
On 06/03/12 19:59, auto15963...@hushmail.com wrote:
>> 4. He has left his laptop unlocked and unattended for a very
> short period
>> of time and he is using gpg-agent with a cache-ttl > 0.
>
> I do in fact use gpg-agent and a cache >0, but this machine is not
> in a workplace or public location
On Mon, 05 Mar 2012 13:40:09 -0500, David Shaw wrote:
> You can examine the revocation certificate with:
>
> gpg --export (your key id) | gpg --list-packets
> The piece you are interested in will look like this. It's usually the
> second packet in an exported key:
>
> :signature packet: algo 1,
Hi,
if you post an URL which is the actual body of your question, please
also copy and paste the relevant parts from that web page. This is
important for some reasons:
1. Not everyone is online while reading mails. For example, I often go
over mails while traveling by train. Establishing an
Thanks to you and Robert for getting back to me. However this
unfortunately didn't solve the problem. I ran:
chown alastair:alastair ~/.gnupg/
and
chown alastair:alastair ~/.gnupg/*
Then I tried root:alastair and alastair:root but still no go.
Any other ideas? In the meantime, I'll try and cho
19 matches
Mail list logo
