> Is there really a need to carry around every expired signature forever
> from a robo-signer?
> Should/could some of the expired signatures be actively filtered (and
> archived)
> instead of being carried in SKS key servers forever? Yes a policy change
> like this would be controversial and diff
When I was first implementing SKS retrieval, I verified about
4M recently updated keys,
While checking expired signature behavior, it was very easy
to spot 0xca57ad7c showing up repeatedly, often enough
to imprint the fingerprint sufficiently that I actually looked
(and decided to never again ver
Hi,
Sorry, the usual friday dump is a bit late today but it's available
right now:
http://key-server.org/dump/
ftp://key-server.org/dump/
As a few people may have noticed, there is a GnuKS listed in the
pool as server software. This is the fork of sks which we ar working
on right now. Source Cod
On 2012-05-25 at 10:53 -0400, Phil Pennock wrote:
> Attached patch for sksclient.ml lets it take multiple keys on argv and
> strips an optional 0x from the front of a keyid.
Attached patch is my diff from your hg tip. Fixes the bdb include,
changes sksclient to:
* use -stdin to read from stdin,
On 2012-05-25 at 13:14 +0200, Kristian Fiskerstrand wrote:
> Ok, I've pushed it to my repo for now, so it is available at [0].
>
> Note that if it is to be used for high-frequency jobs, another approach
> should probably be considered than opening and closing the DB each
> time. And not doing any
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 2012-05-25 13:56, Phil Pennock wrote:
> On 2012-05-19 at 19:47 -0500, John Clizbe wrote:
>> Thanks to work by Kristian Fiskerstrand, Phil Pennock, and myself
>> the following changes are now available on the SKS trunk:
>
> Fresh clone: --
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 2012-05-25 13:56, Phil Pennock wrote:
> On 2012-05-19 at 19:47 -0500, John Clizbe wrote:
>> Thanks to work by Kristian Fiskerstrand, Phil Pennock, and myself
>> the following changes are now available on the SKS trunk:
>
> Fresh clone: --
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
On 2012-05-19 at 19:47 -0500, John Clizbe wrote:
> Thanks to work by Kristian Fiskerstrand, Phil Pennock, and myself the
> following changes are now available on the SKS trunk:
Fresh clone:
- 8< cut here >8
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 2012-05-25 13:09, Phil Pennock wrote:
> On 2012-05-25 at 11:23 +0200, Kristian Fiskerstrand wrote:
>> Is this client something there is an interest in from others so
>> that we should include it directly?, wouldn't necessarily be
>> worse than t
On 2012-05-25 at 11:23 +0200, Kristian Fiskerstrand wrote:
> Is this client something there is an interest in from others so that
> we should include it directly?, wouldn't necessarily be worse than the
> spider..
I'm interested. I've glanced at the WoT stuff a couple of times and
pondered doing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 2012-05-25 09:27, Giovanni Mascellani wrote:
> Hi
...
>
> Thanks, I'll try it later. Since I do not know Ocaml, is it
> possible to make the program fail (exit with code != 0) when it
> finds no keys?
>
See updated patch vs latest trunk.
Also
Hi.
Il 25/05/2012 01:02, Kristian Fiskerstrand ha scritto:
> Hi Giovanni,
>
> You might want to try something like the attached patch
>
> needs "make sksclient", and use it like ./sksclient 6b0b9508
>
> (note, I've only added support for that key format)
Thanks, I'll try it later. Since I do n
12 matches
Mail list logo
