> Ah, you got me ;-) So you are a developer?
In my day job I'm a developer, among other things. However, due to my
taking research funding from the U.S. government in the past, I do not
contribute code to either GnuPG or Enigmail. I find other, non-code,
ways to help the GnuPG and Enigmail teams
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 07/18/17 08:36, Robert J. Hansen wrote:
>> ... shouldn't the focus of GnuPG be on security?
>
> This *is* a security issue.
Since you put it that way, I agree.
> Some ... GnuPG use a ... "random_seed"... must not be backed up or
> shared ...
We have a simple process that has worked for thousands of files over the
years:
1) Client ZIPs up a bunch of files
2) Client GPG/PGP encrypts that ZIP file
3) Client uploads that encrypted file to us
4) Our production server automatically decrypts the file
5) Our production server automatically unz
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Saturday 15 July 2017 at 3:54:07 PM, in
, Brad Rogers
wrote:-
> Card no. CVV & expiry date.
Sorry, tired when I wrote that. On the shopping website, the customer
keys in the long card number, the **expiry date** and the last three
digits from
Werner Koch schrieb am 16.07.2017 um 21:17:
> On Sun, 16 Jul 2017 09:30, d...@fifthhorseman.net said:
>
>> I don't think there's currently any plan to do anything like this, but
>
> Actually this is implemented since GnuPG 2.1.19 (Debian has 2.1.18,
> though) when used withwith a pinentry from Gi
Hello!
The GnuPG Project is pleased to announce the availability of Libgcrypt
version 1.8.0. This is a new stable version of Libgcrypt with full API
and ABI compatibility to the 1.7 series. Its main features are support
Blake-2, XTS mode, an improved RNG, and performance improvements for the
ARM
> Sorry if I'm asking dumb questions
Not a dumb question.
> what would be wrong with sync'ing the whole gnupg directory (or the
> whole user profile / home directory) with rsync/duplicity/whatever ?
There are a number of lockfiles, sockets, etc., that live in the
~/.gnupg directory which shouldn
Am 18.07.2017 um 15:36 schrieb Robert J. Hansen:
>
>> While it would be nice if it were easier to be able to back up easily
>> as you're suggesting, shouldn't the focus of GnuPG be on security?
> This *is* a security issue.
>
> Some versions of GnuPG use a file called "random_seed", for instance.
>
Il 18/07/2017 14:23, Daniel Villarreal ha scritto:
> Have you ever asked Werner about what he thinks about "ease" of
> backing up?"
Security = confidentiality + integrity + availability
If you're not considering availability, you only can have partial security.
BYtE,
Diego
> Have you ever asked Werner about what he thinks about "ease" of
> backing up?"
I have made these observations before, yes.
> While it would be nice if it were easier to be able to back up easily
> as you're suggesting, shouldn't the focus of GnuPG be on security?
This *is* a security issue.
S
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 07/17/17 08:54, Robert J. Hansen wrote:
>> I'm not sure if Rob's routine actually backs up local
>> signatures... I couldn't see anything explicit about it with a
>> quick glance at the code. That's fine if you don't use local
>> signatures at
11 matches
Mail list logo
