Doug Barton:
> On 11/25/2016 02:28 AM, Stephan Beck wrote:
>> Hi David,
>>
>> I kindly invite you to post your PM on-list. It might be of interest for
>> other people as well.
>
> Why send this to the list, rather than to him privately?
Why not? I supposed that he was reading the list.
Cheers
On Fri, 16 Dec 2016 15:12:46 +0900
NIIBE Yutaka wrote:
> [...]
> I'm afraid you are using libgcrypt 1.7.4. In version 1.7.4, there was
> a bug in configure script, which might cause such a trouble.
Indeed. Looks like I mixed up those versions; it was the 1.7.3 -> 1.7.4
upgrade which caused the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Saturday 17 December 2016 at 1:16:13 AM, in
, Robert J.
Hansen wrote:-
>> I'd like to know if setting both versions to point
>> at the same
>> directory to obtain the pubring.gpg, secring.gpg
>> and trustdb.gpg
>> files can cause critical issu
Hello list,
I just want to tell as it is now: It seems to happen something
strange with network access within this PC. If it happens again, the
mail client Pegasus cannot connect at all to localhost (neither to
127.0.0.1) where GPGRelay (the GnuPG "Proxy") would listen - If
GPGRelay just would
>
> You can use different configuration files. A couple of years ago, dkg
> shared [0]:-
>
>> gpg 2.1.0 will look for the following files in $GNUPGHOME and choose the
>> first one it finds:
>
>> gpg.conf-2.1.0
>> gpg.conf-2.1
>> gpg.conf-2
>> gpg.conf
>
>> gpg 1.4.18 will do the same sort o
On Friday, 16. Dec 2016, 19:02:37 -0800, Doug Barton wrote:
> On 11/25/2016 02:28 AM, Stephan Beck wrote:
> > Hi David,
> >
> > I kindly invite you to post your PM on-list. It might be of interest for
> > other people as well.
>
> Why send this to the list, rather than to him privately?
Because i
Felipe Vieira :
> right now I have a working workstream that gets paths from a text file and:
>
> tar -> compress -> encrypt -> split (over each line/entry)
>
> Probably there is a security issue here as some of the paths are dozens of
> gigabytes in size.
>
> I would like to swap the 'encrypt ->
Am 16.12.2016 um 13:36 schrieb Andrew Gallagher:
> On 16/12/16 02:30, sivmu wrote:
>> If the token does the encryption (and signing) operations,
>
> Smartcards perform signing and DEcryption (which in the case of RSA are
> mathematically identical).
>
>> it needs randomness.
>
> That's true of
> On 18 Dec 2016, at 00:17, sivmu wrote:
>
> ... that this means RSA encrzption is reproducable, meaning encrypted
> files of the same plaintext result in the same ciphertext, as this woul
> make the process reproduceable and any malfunction can be easily noticed.
No, because the plaintext is s
>> The smartcard itself only RSA-decrypts the session key (or hash),
>> and this doesn't require an RNG.
>
> ... that this means RSA encrzption is reproducable, meaning
> encrypted files of the same plaintext result in the same ciphertext,
> as this woul make the process reproduceable and any malf
On Sun, Dec 18, 2016 at 12:27 AM, Helmut Waitzmann wrote:
>
> As this problem is more one of split/dd/shell than of gpg, how
> about discussing this in the usenet group “comp.unix.shell” rather
> than in the “gnupg-users” mailinglist?
>
Actually there is reason to discuss it here because the orig
Am 18.12.2016 um 01:30 schrieb Andrew Gallagher:
>
>> On 18 Dec 2016, at 00:17, sivmu wrote:
>>
>> ... that this means RSA encrzption is reproducable, meaning encrypted
>> files of the same plaintext result in the same ciphertext, as this woul
>> make the process reproduceable and any malfuncti
12 matches
Mail list logo
