On Tuesday 24 February 2015 01:36:25 Daniele Nicolodi wrote:
Hello Daniel,
thanks for your reply.
On 21/02/15 20:11, Daniel Kahn Gillmor wrote:
On Wed 2015-02-18 13:46:19 -0500, Daniele Nicolodi wrote:
I have a sufficient trust in the security of the server where the
automated process
On Tue, 24 Feb 2015 00:59, dani...@grinta.net said:
However, the ordering is not really enforced: this
Right. Options and commands are actuallay interchangeable but that is
an undocumented features. In fact the only difference between a command
and an option is that tehre may only be one
On 24/02/15 09:34, Werner Koch wrote:
No, we can't error out on an arg which looks like an option because that
may actually be a valid argument.
However, if running interactively and --batch is not specified, might it
be useful to print Warning: --export-options did not match any key
with the
On 24/02/15 09:34, Werner Koch wrote:
I find it surprising that unrecognized tokens are simply ignored.
Wouldn't it be preferable to error out, at least on unrecognized options?
GnuPG does not follow the common GNU model of interchangeable options
and args. It is modeled like a classic Unix
Hello,
I am trying to write a program that read GPG privates keys that have
been exported to a GPG smartcard using GPG. Those keys are encoded
unsing a S2K Specifier that is described in RFC 4880 as
experimental (Tag 101). GPG (using gpg --list-packets) describes this
as gnu-divert-to-card S2K,
i will try going back to the older version of libgpg-error
This is the order of the build I did; if there are versions of packages
that don't require pth.
Let me know and I will try to rebuild with different versions
1. Build and install pth 2.07
2. Build and install libgpg-error 1.18 (due to
On 24/02/15 17:52, Werner Koch wrote:
for everything else you need to look at the code (parse-packet.c)
RFC 4880 specifies that for a string-to-key usage octet of 255, the final two
bytes are a checksum, but it /is/ part of the encrypted data for v4 keys. I was
curious and also had a look at the
On Tue, 24 Feb 2015 15:55, leonard.dal...@taztag.com said:
I have tried to find a description of this S2K format, but I haven't
found one. Does anyone know where I can find a description of this
experimental S2K ?
doc/DETAILS shows this
* GNU extensions to the S2K algorithm
S2K mode 101
got a working gpg2! Thanks. Now to figure out automation. Will post a
separate thread regarding my
issues with removing passphrase,.
On Tue, Feb 24, 2015 at 11:23 AM, Errol Casey er...@askerrol.org wrote:
i will try going back to the older version of libgpg-error
This is the order of the
When I use gpg2 --edit-key emailaddress, and then use passwd to
change/remove
passphrase by entering a blank passphrase. I get hung in an input loop
lqk
x Please re-enter this passphrase x
x
Il 25/02/2015 00:01, Peter Lebbing ha scritto:
On 24/02/15 23:16, Daniel Kahn Gillmor wrote:
If you asked me to /destroy/ the key, I would look through my drawers for all
backups I have and do a shred on them, and think really hard where any
further
copies might have ended up.
Use a
Hi
Can someone tell the how to disable pinentry? I'd like to be able to run gpg
--edit-key, or to open a password encrypted file without a GUI. I was able to
do that in RHEL5, but so far, not in RHEL6 or CentOS 6.
I have gpg 2.0.14 on CentOS 6.6 and RHEL6U6.
I've tried to disable pinentry,
On 24/02/15 23:16, Daniel Kahn Gillmor wrote:
So why are you keeping it around?
I suppose it depends on your definition of destroying...
I think you'd be fine with setting an expiry date and --delete-secret-key-ing
the subkey when the time comes.
If you asked me to /destroy/ the key, I would
On Mon 2015-02-23 19:36:25 -0500, Daniele Nicolodi wrote:
On 21/02/15 20:11, Daniel Kahn Gillmor wrote:
Using a subkey is a reasonable approach, and rotating (and destroying)
the secret key of the rotated subkey is not a bad idea.
What do you exactly mean by destroying? Isn't setting a
14 matches
Mail list logo
