Just my idea. I tried to understand the dispatcher code and keyring.c
Werner was referring to, but I would not know how to implement it.
Save each chunk as a seperate relational tuple?
By the way: Because of database design, even SQLite would probably be
faster for reading, but not for writing. Bu
Hi there,
LANG=C is always ANSII. For UTF-8 use en_EN.UTF-8.
Regards.
2011/1/17 Werner Koch :
> On Sun, 16 Jan 2011 20:45, bo.bergl...@gmail.com said:
>
>> I set the environment variable to "C" and then ran gpg2 -h. Example of
>> output:
>
> Use
>
> set LC_MESSAGES=C
>
>> Characters used for th
Hello everyone,
there is a bug where kwatchgnupg adds gpg2-Options to gpg.conf,
whether it is a gpg2 config file or not. gpg refuses to work with
these invalid options.
Perhaps some of the devs might want to take a look at it, as it is
very annoying.
https://bugs.kde.org/show_bug.cgi?id=226630
Hi,
try
$ gpg2 --no-default-keyring --keyring --list-keys
It doesn't give me the same output, but this seems the most obviuous
command to me. I couldn't find the exact output either. I was missing
fingerprints, but --with-fingerprint didn't help.
Hope this helps,
Ben
2010/6/8 Joke de Buhr :
>
Hello every one!
I'm new to this list, but this seems a very interesting topic to me.
2010/6/4 Micah Anderson :
>
> 0 1 * * * /usr/bin/gpg --refresh-keys > /dev/null 2>&1
Thanks for this wounderful idea. I update my keys every now and then,
but it usually comes down to events like key signing par