On 2016-04-29 06:54, Paul R. Ramer wrote:
> Personally, I would rather not have to hit the "Page Down" button
> *every* time I wrote an email (provided I have full-size keyboard). If
> you are always varying from the defaults in a consistent way, then the
> defaults need to be different.
Are you sure that you are using gpg2? private-keys-v1.d only contains
private keys for gpg2. gpg1 stores them in ~/.gnupg/secring.gpg or
something like that. If enigmail uses gpg2 and you created your key with
gpg1, they will not see the same keys. '--version' is your friend.
IIRC, using the key
On 29.03.2016 05:53, Daniel Villarreal wrote:
>> Depending ... the gnupg 2.x executable is still called 'gpg'. I
>> guess it depends on if the distributor wants to keep easy backwards
>> compatibility. On archlinux,.. only one gnupg package ... The
>> executable is called gpg...Regards, Viktor
On 28.03.2016 19:16, Daniel Villarreal wrote:
> Should we not strive to use gnupg v2x ? I always try to use gpg2 on
> the command-line, whereas documentation seems to show gpg.
>
> example...
> Encrypting and decrypting documents
> https://gnupg.org/gph/en/manual.html#AEN111
Depending on the
On 22.03.2016 23:10, Dashamir Hoxha wrote:
> You got this wrong. It does not enforce 1 month expiry. Right after
> creating the key you can change its expiry to 10y, if you wish. But if
> you say nothing, after 1m you will have to renew it (if you still
> remember the passphrase). This is like a
Thanks, I found it myself but since the sender of a mail to the list
does not get a copy of it, I could not simply reply. If I use
'--list-options show-unusable-subkeys', I see the missing keys, they are
simply expired. Sorry to disrupt.
Regards,
Viktor
signature.asc
Description: OpenPGP
Hi,
is there a possibility to list what each of the private keys in
~/.gnupg/private-keys-v1.d is? Some of them I recognize in the listing
of 'gpg --with-keygrip -K', but there are six files in the folder while
only three keygrips are shown by the command (one of which is the master
key and not
On 21.03.2016 10:44, Paolo Bolzoni wrote:
> Dear list,
>
> The subject pretty much says it all already, I am using GnuPG 2.1.11
> (with libgcrypt 1.6.5) and I was wondering if I should always add
> myself as recipient when encrypting a file, of course, in addition of
> the real recipient.
>
> Is
On 21.03.2016 18:38, Peter Lebbing wrote:
> $ gpg2 -Ar de500b3e -e file.txt
>
> is nicer than:
>
> $ gpg2 -o file.txt.gpg -r de500b3e -e file.txt
Actually, it seems that if you omit -o, gpg2 will do exactly this.
Regards,
Viktor
signature.asc
Description: OpenPGP digital signature
On 2016-03-18 13:18, Peter Lebbing wrote:
> Can someone point me in the direction of the solution to this
> counterintuitive probability theory result? Any of a common name for the
> property, a mathematical explanation or an intuitive explanation are
> much appreciated!
Any match of a pattern
On 08.03.2016 16:33, Daniel Kahn Gillmor wrote:
> Sorry, but no. The keyservers are globally-synced and append-only. you
> will not be able to remove stuff once it's posted there.
I always wondered what would happen if someone uploaded something to the
keyservers where he has no permission to
On 05.03.2016 19:33, Josef Carnap wrote:
> It looks as if the files simply were copied to folder_2. But when I try
> to open the *.docx files with Libre Office for example I can see that
> doesn't work.
> So I guess the very problem ist the missing file extension *gpg for the
> files in folder_2.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 2015-12-27 07:11, Rob Landau wrote:
> Good day, I have just received my first Linux system (Ubuntu
> 14.04) It has Seahorse installed, but I don't see any GnuPG
> application. How can I determine if there is a GnuPG installed,
> and if so
On 16.08.2015 16:26, Stefan Claas wrote:
if i understand you correctly it would not help me if someone
would sign my key without my approval, so to speak.
Sure it helps. If Alice signs my key and Bob wants to send me something
and trusts Alice, he can derive some trust that my key is also
On 2015-07-30 16:39, MFPA wrote:
On Thursday 30 July 2015 at 1:43:35 PM, in
mid:55ba1bf7.4090...@enigmail.net, n...@enigmail.net wrote
BTW, as another example, several keys of
t...@gpgtools.org are faked (search for these keys and
the the interesting result).
Sorry, I don't see a result
On 31.07.2015 01:11, MFPA wrote:
Only if you download the key from the GPGTools website and find the
key-id first. (If the GPGTools team shows their key ID or Fingerprint
on their website, I failed to find it.)
On the front page they have 'to verify the signature, please download
and import our
On 2015-07-30 10:17, Ingo Klöcker wrote:
I'm sorry to tell you that you have fallen into the trap. There is only one
genuine pg...@ct.heise.de key the fingerprint of which is printed in each
issue of the c't magazine. The other one is a fake. And the fact that the
fake
key with the
On 2015-07-29 18:24, n...@enigmail.net wrote:
So, could somebody explain in a bit more detail how a PoW approach works?
As far as I understand it, for any key that you have - regardless
whether you have access to the mail address in the uid - you can add
some signature where anyone with the
On 04.07.2015 14:03, Juan Miguel Navarro Martínez wrote:
I could do it myself by importing the keys in GPG 2.1, then exporting
them.
Hi,
thanks for the quick reply, but I am using GPG 2.1.5 and 'gpg --import
sec.key' does not seem to work if there are already other subkeys of the
same key
OK, it seems that the actual problem was that --export-secret-subkeys
does not work if I leave the passphrase empty. Since my hard disks are
encrypted, I usually do not have passphrases for my secret keys and
since GnuPG 2.0 this created some problems. When I exported them with a
passphrase and
Hi,
there has already been a discussion on this two years ago, see
https://lists.gnupg.org/pipermail/gnupg-users/2013-September/047567.html
I have been following the intstructions on
https://wiki.debian.org/Subkeys for some time now, with my master key
only residing on my backup disk and several
21 matches
Mail list logo
