At the Circumvention Tech Festival there was an event called
speed-geeking, where the people responsible for a tool would speak for a
few minutes on something related to the tool and field a few minutes of
QA from the audience about the tool. I received a number of requests
afterwards to reprise
On Wed, 11 Mar 2015 15:12, br...@minton.name said:
git.gnupg.org) don't use that certificate. Have you considered a wildcard
certificate? I know this has been discussed before, e.g. at
Too expensive ;-). To stop all these complaints I will add a so called
real certificate but first I need
Peter,My understanding was that if you don't pass --symmetric, then a session
key is generated, with which the clear text is (symmetrically) encrypted and
then the session key is encrypted (asymmetrically) with the public key.
Conversely, if you do pass --symmetric, then there is no
Thanks Vedaal, yep that would be one mighty strong password!
From: ved...@nym.hush.com ved...@nym.hush.com
To: Maricel Gregoraschko maricelgregorasc...@yahoo.com;
gnupg-users@gnupg.org
Sent: Tuesday, March 10, 2015 4:42 PM
Subject: Re: AES-NI, symmetric key generation
On 3/10/2015
Thank you Pete for clearing things up. Makes a lot of sense to store
passphrase-to-key identification data, in addition to actual algorithm used, in
the output message rather than have the decryptor just assume things.
I figured out how to use --show-session-key: in my tests it doesn't show the
On 3/11/2015 6:55 PM, Maricel Gregoraschko wrote:
Thank you Pete for clearing things up. Makes a lot of sense to store
passphrase-to-key identification data, in addition to actual algorithm
used, in the output message rather than have the decryptor just assume
things.
Indeed. The folks who
On 11/03/15 18:55, Maricel Gregoraschko wrote:
One more question: Is there any standardization in output formats
between encryption programs and libraries, for example say you
encrypt with AES128 in CBC, with the same key (directly or via
passphrase), and since the output will have to have,
On 3/11/15 3:15 AM, Werner Koch wrote:
The standard ssh client on Windows seems to be Putty; you may use it
with the native GnuPG for Windows (i.e. Gpg4win) by using the option
--enable-putty-support instead of --enable-ssh-support.
PuTTY also has its own agent support, which works quite well.
Thanks Vedaal, yep that would be one mighty strong password!
It's also way overkill. :)
gpg --armor --gen-rand 1 16 will produce a (relatively) short
passphrase suitable for pretty much any imaginable usage. 128 shannons
of entropy's nothing to sneeze at.
Hi Robert,
Am 11.03.2015 um 18:10 schrieb Robert J. Hansen:
Things you're doing wrong with Enigmail is a short (500-word) essay on
four mistakes I repeatedly see Enigmail users making. However, it's not
limited to Enigmail: most of the content is broadly applicable to any
cryptosystem.
Hi all,
On my workstation, I have installed cygwin and GPG4win which is
bundled with a version of gpg-agent (cygwin comes whith oldies and
no gpg-agent AFAICS).
I enabled ssh support in the gpg-agent.conf file as usual and I
clearly see the socket files for both GNUpg and SSH.
When starting a
On Wed, 11 Mar 2015 07:18, xav...@maillard.im said:
I enabled ssh support in the gpg-agent.conf file as usual and I
clearly see the socket files for both GNUpg and SSH.
The Unix Domain Socket emulation used by Cygwin is different from the
emulation used by GnuPG on Windows. Recall that Cygwin
I would like to second the request for this feature.
On Wed, Mar 11, 2015, 6:23 AM Werner Koch w...@gnupg.org wrote:
On Wed, 11 Mar 2015 07:18, xav...@maillard.im said:
I enabled ssh support in the gpg-agent.conf file as usual and I
clearly see the socket files for both GNUpg and SSH.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I wanted to report a bug of gnupg, but my browser complained about the
certificate (self-signed, and for kerckhoffs.g10code.com) rather than
bugs.gnupg.org. I noticed that https://gnupg.org has a trusted certificate
from Gandi Standard SSL CA, but
Doug Barton dougb@dougbarton.email writes:
On 3/11/15 3:15 AM, Werner Koch wrote:
The standard ssh client on Windows seems to be Putty; you may use it
with the native GnuPG for Windows (i.e. Gpg4win) by using the option
--enable-putty-support instead of --enable-ssh-support.
PuTTY also has
15 matches
Mail list logo
