Subscribe: GnuPG | devel
Added By: Feedage Forager Feedage Grade A rated
Language: English
agent  argparse  build commandline  gpg  multiple tokens  patch  path gpg  path  removed  rfc patch  rfc  socket  unnecessary ambiguity 
Rate this Feed
Rate this feedRate this feedRate this feedRate this feedRate this feed
Rate this feed 1 starRate this feed 2 starRate this feed 3 starRate this feed 4 starRate this feed 5 star

Comments (0)

Feed Details and Statistics Feed Statistics
Preview: GnuPG | devel

GnuPG | devel

Mailing List Archive by Gossamer Threads

Last Build Date: 16 Jan 2017 11:18:46 -0800

Copyright: (c) Gossamer Threads Inc. All rights reserved.

[RFC PATCH 2/2] Cleanup now unused code.

16 Jan 2017 04:27:00 -0800

* src/agent.c (build_w32_commandline_copy): Removed. (build_w32_commandline): Removed. (spawn_process_detached): Removed. * src/get-path.c (get_gpg_ag

[RFC PATCH 1/2] Get GPG Agent's socket directly from the agent.

16 Jan 2017 04:26:59 -0800

* src/agent.c (agent_connect): Call gpg-connect-agent to get the socket for a running agent. * src/get-path.c (get_gpg_connect_agent_path): New functi

[RFC PATCH 0/2] Scute: Fix connection to a running agent.

16 Jan 2017 04:26:58 -0800

Hi, The following patch set implements a new way for Scute to find the socket of the GnuPG Agent. The current code still uses a logic that was adapt

NTBTLS: ignoring ALERT

16 Jan 2017 00:07:01 -0800

While testing NTBTLS with the keyserver, I encounter the issue of:

KSBA: Using names of OID from different sources

15 Jan 2017 11:23:10 -0800

Hi all, Is there a reason for dn.c:append_atv() being restricted to only use names for OIDs which are in rfc2253 ? eg. while openssl s_client conver

Question about key generation

14 Jan 2017 05:45:16 -0800

Hello, we're trying to generate a pair of Rsa keys (public/private), using the latest release of libgcrypt sources, we're using the following method:

scd: support multiple tokens simultaneously

12 Jan 2017 21:06:43 -0800

Hello, This is an interim report which explains multiple tokens now works for me for decryption and signing. The gpg-agent <-> scdaemon protocol is

[PATCH] Set 'mym4_revision' to 0 if not a git repo

11 Jan 2017 20:52:25 -0800

--- It is possible for the source to not be located in a git repository (e.g. source is from a tarball). In which case the git repository information

self-sigs with weaker hashes

10 Jan 2017 15:58:55 -0800

hey all-- please take a look at the behavior of gpg 2.1.17 with key DC418BB65BF51BA86B845A48308B0A7BD8DEC2EC This is a 3072-bit DSA key with two Use

[PATCH] common: Avoid unnecessary ambiguity in argparse.

10 Jan 2017 13:16:15 -0800

* common/argparse.c (find_long_option): Avoid unnecessary ambiguity. If two struct ARGPARSE_OPTS share a prefix in their long_opt name, but have the