David Shaw wrote:
On Jun 4, 2014, at 4:52 AM, kwadronaut kwadron...@puscii.nl wrote:
Hi,
I noticed that the search for keys in the web fronted is picky in its
input. Some that should work (in my opinion) don't. I double checked
with 'How to specify a uid' in gnupgs documentation [1]. Is
Ronny Wagner wrote:
Dear Community,
i upgrade my two sks server from squeeze to wheezy with sks 1.1.4 (wheezy
backport).
After the update, I become following failed message:
Requesting 2 missing keys from ADDR_INET [80.101.216.220]:11371, starting
with 61AA86A0328D7DF39FC96E13B0A18B83
1
Ronny Wagner wrote:
Dear Community,
i upgrade my two sks server from squeeze to wheezy with sks 1.1.4 (wheezy
backport).
After the update, I become following failed message:
Requesting 2 missing keys from ADDR_INET [80.101.216.220]:11371, starting
with 61AA86A0328D7DF39FC96E13B0A18B83
1
d
Ronny Wagner wrote:
Hallo Tobias and John,
Server 01
I do a rebuild from a keydump, but its very slowly (/usr/sbin/sks build
/var/lib/sks/dump/*.pgp -n 2 -cache 100)
rebuilding kdb is not so great an idea as the problem was most likely in
PTree. running pbuild to build a new PTree is an
ad...@pgpkey.org wrote:
Thanks John,
You're welcome. Please don't CC me on replies to the list, one copy in one
inbox is sufficient.
NB: Those wishing to try the code and query their own keyserver need to be
running my latest trunk. The patch adding the header that OpenJS needs to be
able
Kristian Fiskerstrand wrote:
Granted this whole discussion probably belongs somewhere else, but
since we're first on the topic, let me chime in my two cents.
First of all, any encryption done in a browser will at least have to
be done in a browser extension that does not auto-update. One
Daniel Kahn Gillmor wrote:
On 11/27/2013 04:30 PM, Phil Pennock wrote:
On 2013-11-27 at 12:57 -0500, Daniel Kahn Gillmor wrote:
i'm running sks 1.1.4 on Debian GNU/Linux, wheezy, amd64 (x86_64)
platform.
I see the following situation in the logs of the recon process (this is
just an
Todd Lyons wrote:
Thomas, you are also running version 1.1.1 of the keyserver software.
You will find that some will refuse to peer with you unless you are
running at least 1.1.3.
Umm, what does peering have to do with the SKS version that one would refuse
to peer with a server running a
Daniel Kahn Gillmor wrote:
hi SKS folks--
I was just looking at the behavior of sks 1.1.4, and i noticed that it
seems to have /dev/random open for writing:
0 zimmermann:~# lsof /dev/random
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
sks 742 debian-sks3w CHR
John Clizbe wrote:
Daniel Kahn Gillmor wrote:
hi SKS folks--
I was just looking at the behavior of sks 1.1.4, and i noticed that it
seems to have /dev/random open for writing:
0 zimmermann:~# lsof /dev/random
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
sks 742
Daniel Kahn Gillmor wrote:
Hi John, all--
On 09/14/2013 09:46 PM, John Clizbe wrote:.
clearly i think that such data should neither propagate on the
keyservers nor be accepted or transmitted by the clients. Both sides of
the transaction should be actively filtering to minimize unwanted
Daniel Kahn Gillmor wrote:
On 09/14/2013 05:00 PM, Robert J. Hansen wrote:
[dkg wrote]:
I have told numerous people that the keyserver network will not
propagate local signatures.
This is true.
No, unfortunately, it is not true in any way for SKS 1.1.4 (and probably
earlier versions,
Phil Pennock wrote:
On 2013-09-12 at 19:40 -0400, Daniel Kahn Gillmor wrote:
While this seems like it is probably a fixable bug for someone who knows
their way around the codebase, I forsee problems with synchronizing the
pool, if some SKS keyservers start following the spec and others remain
Daniel Kahn Gillmor wrote:
Someone™ (0x75D292D353ADACCD) made a non-exportable certification on
your user ID John P. Clizbe jpcli...@keyservers.net
(2048R/0x2313315C435BD034). Someone else uploaded that key to a
keyserver (ok, i admit it was me :P). The keyserver network is
currently
Stefan Tomanek wrote:
Dies schrieb John Clizbe (jpcli...@gingerbear.net):
2012-10-27: Fixes for machine-readable indices.
Key expiration times are now read from self-signatures on the key's UIDs.
(KF)
In addition, instead of 8-digit key IDs, index entries now return the most
specific key
Stefan Tomanek wrote:
With this change, an additional line is appended to each search result when
using the machine readable output. This line is prefixed with fpr: and
contains the fingerprint of the key returned, making it possible to
distinguish
keys from each other before downloading
Christoph Anton Mitterer wrote:
Hi.
As mentioned previously I'm in the process of migrating/re-installing my
SKS instance at much better machine...
I run SKS 1.1.3 from Debian sid (which has BDB 5.1, IIRC).
Just for trying, I dumped the keydb from my old server, and made a full
build
Stefan Parviainen wrote:
On 06/29/2013 01:17 AM, Phil Pennock wrote:
If you're modifying code to add support for this, you should consider
just adding keyserver support, it's a very simple HTTP POST and there
are resilient pool addresses to help.
That would be the ideal, of course. However,
Frank de Bot wrote:
Hello,
Often my SKS servers stops working. In the log I see this last line:
Bdb.DBError(BDB2034 unable to allocate memory for mutex; resize mutex
region)
I run a FreeBSD 8.1 (x64) server with these versions:
SKS version 1.1.4
Compiled with Ocaml version 3.12.1 and
Rafael wrote:
We have here a local SKS only for local users, how can I backup and restore
all public keys from my server??
When I first read the subject I thought, Why, unless it's for local use only?
Backup -- sks dump
Restore/Creation -- sks build, followed by sks clean and sks pbuild.
David Benfell wrote:
Hi all,
Ick. This is proving more difficult than I expected.
Trying to dump the database on the old server yielded some kind of
database error, with the suggestion to run recovery. I couldn't find
how to do a recovery, so I just copied the latest dump from
Patrick R McDonald wrote:
All,
I would like to upgrade my sks on Debian Squeeze from 1.1.1 to 1.1.3
using Debian backports. Is there anything of which I need to be aware
when making this upgrade?
if your 1.1.3 is linked with the same version of Berkeley DB as your 1.1.1,
there should be
Phil Pennock wrote:
Folks,
We now have two separate issues affecting SKS (and GnuKS) keyservers
which have nginx or Apache in front of them, affecting interop
compatibility with various versions of GnuPG (and other clients) as
deployed.
Even as changed clients roll out, we can expect to
Phil Pennock wrote:
If someone has a current good example of Apache config for this, we
should add that too.
Using this on both servers, ports 80 11371
VirtualHost *:11371
ServerName keyserver.example.net
ServerAlias pool.sks-keyservers.net *.pool.sks-keyservers.net
Andy Ruddock wrote:
Kristian Fiskerstrand wrote:
On 02/19/2013 06:19 PM, Andy Ruddock wrote:
mid-December, so tried copying that but ran into out of space
for mutex errors each time I tried to start sks - even after
running sks cleandb.
sks cleandb doesn't address this, it only affects the
to extend my request for new peers.
You should already have gingerbear.net. You're welcome to add keyservers.net
keyserver.gingerbear.net 11370 # John Clizbe j...@gingerbear.net 0xD6569825
sks.keyservers.net 11370 # John Clizbe j...@gingerbear.net 0xD6569825
For mailsync, please add
pgp
Moritz Rudert (helios) wrote:
On 02/21/2012 06:02 PM, H.-Dirk Schmitt wrote:
Hello!
After upgrading from ubuntu/natty to ubuntu/oneiric sks stop working
with the error message
unable to allocate memory for mutex; resize mutex region in db.log.
If someone else runs in this problem below
Jakob Rößler wrote:
Hello list,
I just subscribed to this mailing list and wanted to say hello to you
guys.
Furthermore I want to request you to find somebody who agrees to
reconcile his sks database with mine.
Hello Jakob,
Welcome. There is an informal protocol we have for peering. The
folkert wrote:
Could you please post, HOW you're uploading? Say, what exactly are you
doing?
What I do is:
gpg --keyserver 172.29.0.11 --send-key C4739D2D
gpg --keyserver wwwkeys.pgp.net --send-key C4739D2D
gpg --keyserver subkeys.pgp.net --send-key C4739D2D
gpg --keyserver
Scott Grayban wrote:
The IPv4 for keyserver.borgnet.ushas changed. Everyone using my sks keyservers
peering needs to flush your dns cache so the new IP gets updated.
Kristian please flush your servers cache as well so that
http://sks-keyservers.net/status/info/keyserver.borgnet.us starts
Ronny Wagner wrote:
Hi All,
I have a new keyserver running and would like to peer with other
servers. Please add me to your 'membership' file with the following
entry and provide your details in return so I can do the same:
keys-01.licoho.de 11370
You already have one of my servers in
Phil Pennock wrote:
On 2012-11-06 at 18:18 +, Ronny Wagner wrote:
I have a new keyserver running and would like to peer with other
servers. Please add me to your 'membership' file with the following
entry and provide your details in return so I can do the same:
SKS does not efficiently
k clair wrote:
Hello,
I can't find anywhere that this is documented: Is there a way to
get the machine-readable output of a search to return the 16-digit
keyid rather than the 8-digit keyid?
The machine-readable index code is pretty simple and direct. There aren't
really any options other
Phil Pennock wrote:
On 2012-10-25 at 12:42 -0700, k clair wrote:
I can't find anywhere that this is documented: Is there a way to
get the machine-readable output of a search to return the 16-digit
keyid rather than the 8-digit keyid?
Not at present. It would require code changes, nothing
David Shaw wrote:
On Oct 25, 2012, at 4:50 PM, John Clizbe jpcli...@gingerbear.net wrote:
Kristian and I were discussing this exact item yesterday. From my reading
of [1], I think 16-digit key IDs should be returned in the mr index. I
/think/ Kristian may also be thinking that way.
Ideally
Daniel Kahn Gillmor wrote:
I think it's doable. Compare
http://keyserver.gingerbear.net/pks/lookup?search=0x83EB2E0Afingerprint=onop=index
and
http://keyserver.gingerbear.net/pks/lookup?search=0x83EB2E0Afingerprint=onop=vindex
Presently, options=mr returns the same for either op value, index
Stephan Beyer wrote:
Hi,
please touch your membership files to note SKS about changes;
sks.pkqs.net IP changed from 88.198.41.86 to 213.133.103.71.
The recon.log tells me that it is already syncing with some servers.
Is touching not required any longer in recent SKS versions?
Touching
Stephan Seitz wrote:
Hi,
it looks like you've got files with wrong permissions (i suspect wrong owner).
To generally avoid this, I'ld suggest to always work with the non-privileged
user.
Just a wild guess: You tried to start sks-recon and/or sks-db as root. Now
it's running with a
Andreas Thulin wrote:
My bad, I sent my e-mail to the wrong receiver...
Also, a correction: I'm running sks version 1.1.3.
Please see below.
/A
2012/9/9 Andreas Thulin andreas.thu...@gmail.com
mailto:andreas.thu...@gmail.com
Hi!
I'm running Ubuntu 12.04 (64 bit) on an
Andreas Thulin wrote:
All right,
those were really good tips - the build actually looks like it's working now
(since I get the expected output).
I've done this a few times :-)
Am I right when assuming that I need to run
# /usr/sbin/sks cleandb
and then
# /usr/sbin/sks pbuild
Rudert
Hello Moritz,
Your server was never removed from mine. In case you need my membership info
again:
keyserver.gingerbear.net 11370 # John Clizbe j...@gingerbear.net 0xD6569825
sks.keyservers.net 11370 # John Clizbe j...@gingerbear.net 0xD6569825
-John
PS: Anyone seeking additional peers
Andreas Thulin wrote:
Hi!
Thanks for good advice, I'll get back on getting a dump immediately. Trouble
is I tried and failed a couple of times with building the DB, and the sks
binary doesn't really give any useful feedback on what I'm doing wrong.
Would you say an e-mail to the sks
Jeffrey Johnson wrote:
On Aug 17, 2012, at 2:31 PM, Jason Harris jhar...@widomaker.com wrote:
Have any of the OCaml hackers ever thought about dumping keys in
keyid (v. SKS hash) order? That would make less deltas when using
rsync. Each keydump file would then have a set range of keys,
Stephan Seitz wrote:
Hi there,
running sks 1.1.3 i noticed reproducable db errors when trying to access
sks-db during sks dump.
It always results in:
Error handling request. Exception raised: Bdb.DBError(PANIC: fatal
region error detected; run recovery)
I didn't find much useful
Stephan Seitz wrote:
Hi there,
I'm going to create weekly or daily (currently undecided) dumps of the
sks-db.
There really is not enough churn to justify a daily dump
If I'ld offer that dumps for download, is there some best-practice how
the URL should look like and how to offer them?
Daniel Kahn Gillmor wrote:
hey folks--
it looks like the sks recon process on zimmermann.mayfirst.org
(a.k.a. keys.mayfirst.org) stopped about 10 days ago:
2012-07-16 05:28:34 Raising Sys.Break -- PTree may be corrupted:
Bdb.DBError(unable to allocate memory for mutex; resize mutex
Phil Pennock wrote:
On 2012-05-31 at 11:51 -0500, John Clizbe wrote:
I'm looking forward to trying out this patch on Windows
Were you able to do so? Did this make SKS tenable on Windows?
Stymied by a linking error. Working on some features Kristian and I have
discussed. I'll beat
Robert J. Hansen wrote:
Due to a catastrophic set of thunderstorms that have hammered public
utilities in the DC area, keyservers.org is experiencing prolonged
downtime. I don't expect it to be operational for the next couple of
days, and the downtime may extend more than a week. My
Brian D Heaton wrote:
Robert,
Depending on whether or not the cell sites have generators in addition
to their battery banks, that 4G service may get spotty soon. When we
went through the Snowpocalypse up here in the PAC-NW early this year
the cell sites started dieing in the rural areas as
Stephan Beyer wrote:
On 01.07.2012 04:29, Stephan Beyer wrote:
Interestingly, if I take a look into merge.log now, I can see:
2012-07-01 04:13:03 Fatal database error: Bdb.DBError(BDB2034 unable to
allocate memory for mutex; resize mutex region)
2012-07-01 04:13:03 closing database...
I
Kristian Fiskerstrand wrote:
On 2012-06-26 20:49, Kiss Gabor (Bitman) wrote:
Dear Johan,
Kristian Fiskerstrand wrote:
...
Just for curiosity I entered URL http://p80.pool.sks-keyservers.net:80
in my browser as written on page
http://sks-keyservers.net/overview-of-pools.php.
I get to page
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1,SHA256
Christoph Egger wrote:
Hi!
Daniel Kahn Gillmor d...@fifthhorseman.net writes:
On 06/25/2012 12:44 AM, Kristian Fiskerstrand wrote:
Please let me know if we should push the timeline some for the 1.1.2
minimum to get more time for
Daniel Kahn Gillmor wrote:
On 06/25/2012 02:16 AM, John Clizbe wrote:
After Christoph's last email re mutex_set_max I checked my own databases,
both
of which were set to 64K. PTree was almost equally split between in-use and
free. KDB was very close to running out with only about 3K left
David Benfell wrote:
Hi John,
On 06/24/12 23:54, John Clizbe wrote:
db_recover -h DB
It says:
atlanta# db4.6_recover -h DB
db4.6_recover: Unacceptable log file DB/log.002109: unsupported
log version 19
db4.6_recover: Invalid log file: log.002109: Invalid argument
David Benfell wrote:
Hi again,
On 06/25/12 00:08, John Clizbe wrote:
db_stat -h . -e|head
This is not looking good:
atlanta# pwd
/var/lib/sks
atlanta# cd DB
atlanta# db_stat -h . -e|head
db_stat: BDB1538 Program version 5.3 doesn't match environment version 4.6
db_stat: DB_ENV-open
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1,SHA256
Christoph Egger wrote:
Hi!
John Clizbe jpcli...@gingerbear.net writes:
David Benfell wrote:
On 06/25/12 01:15, John Clizbe wrote:
FWIW, I believe the current debian package for 1.1.3 is using 4.7
The 1.1.1 package in stable is at 4.7
Phil Benchoff wrote:
On Sun, Jun 24, 2012 at 09:20:07PM +0200, Kristian Fiskerstrand wrote:
As of *1. August 2012* I intend to change the minimum version for
qualification in the pool to 1.1.3.
Our keyserver runs on Centos 5.7. The distribution BDB is 4.3.29 and we
have ocaml 3.12.0. The
Jeffrey Johnson wrote:
On Jun 25, 2012, at 10:24 AM, Phil Benchoff wrote:
On Sun, Jun 24, 2012 at 09:20:07PM +0200, Kristian Fiskerstrand wrote:
As of *1. August 2012* I intend to change the minimum version for
qualification in the pool to 1.1.3.
Our keyserver runs on Centos 5.7. The
Christoph Egger wrote:
Hi!
Daniel Kahn Gillmor d...@fifthhorseman.net writes:
Backports of newer Berkeley DB work too, and likely
have some other usage cases than SKS because of bdb+sqlite3 API.
right, this is one other path i considered, but i don't really want to
have to maintain a bdb
/sks/sks_1.1.3-1.dsc
sks_1.1.3-1_amd64.deb
to main/s/sks/sks_1.1.3-1_amd64.deb
sks_1.1.3.orig.tar.gz
to main/s/sks/sks_1.1.3.orig.tar.gz
John Clizbe wrote:
I have exchanged some emails with the Debian SKS maintainer.
He is almost finished with the packaging and believes he can upload sks
Brian D Heaton wrote:
Howdy, I'm Brian and I'm trying to get a keyserver running on a
Rackspace hosted cloud server. Reading the archives about brokenness in
the Ubuntu packages, I've compiled both BDB and SKS from source.
Attempting the full-build, the system deadlocks after reading in the
will be offline until I can get to the local cable
office, swap out CPE, and get new cable modem installed and configured.
- -John
John Clizbe wrote:
Having a night of heavy thunderstorms, it looks like the cable/HSI supplying
keyserver.gingerbear.net took a cable cut ~4:28 AM CDT
to nothing
about SKS in general or about SKS in Debian with the exception of lame ass
excuses
of course.
Gold Medal : Christoph Martin / christoph.mar...@uni-mainz.de
Silver Medal : Fabio M. Di Nitto / fabbi...@fabbione.net
Bronce Medal : John Clizbe / jpcli...@gingerbear.net
Congratulations
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1,SHA256
C.J. Adams-Collier wrote:
No objection aside from never having heard of the bitbucket revision
control system. Any reason you're not considering something git-based?
Sent from my PDP-11
Other than the name being somewhat offensive in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1,SHA256
Phil Pennock wrote:
I do not run with SKS in a VM and have never experienced the clock
problem, so can't test if the attached patch resolves any problems. I
can confirm that I can receive a key from a peer with this code applied.
So it's
Jeffrey Johnson wrote:
Its the expired robo-signatures on existing pubkeys, not
the pubkeys, that need filtering. There is also a need to
delete pubkeys
Is there a solution that can filter out specific expired
signatures on pub keys that can be gossip'd efficiently?
AFAIK additional
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1,SHA256
Jeffrey Johnson wrote:
On May 30, 2012, at 10:58 PM, John Clizbe jpcli...@gingerbear.net wrote:
Jeffrey Johnson wrote:
Its the expired robo-signatures on existing pubkeys, not
the pubkeys, that need filtering. There is also a need
Gabor Kiss wrote:
So, my requests:
1. Source code
2. Change of name
3. An end to all this useless squabbling
I would like to support this idea wholeheartedly.
Me too. Not necessarily in this order.
One addition:
4. Remove slanderous personal attacks from project's
Gabor Kiss wrote:
So, my requests:
1. Source code
2. Change of name
3. An end to all this useless squabbling
I would like to support this idea wholeheartedly.
Me too. Not necessarily in this order.
One addition:
4. Remove slanderous^W libelous personal attacks from
solution breaking immediately if you use the command line option
to set the base directory of SKS somewhere else should be a Debian bug.
The patch was a whole lot of changes at once. as John Clizbe wrote -
all those changes were needed to fix only this one issue.
With the patch you can find
Jeffrey Johnson wrote:
On May 14, 2012, at 4:21 PM, John Clizbe wrote:
That would be Debian or Ubuntu, and any others based on that work. I
have not seen a FHS patch from the RPM based distributions.
Peter Pramberger's RPM packaging in Fedora has/had some tasteful FHS
patches if you want
Sebastian Urbach wrote:
Hi,
Another exiting Debian Binary Replacement has been released, As usual
you can find it right here:
http://key-server.org/sks/
The You talk, we work release:
Exiting. How exciting! Does it run long before exiting?
Yes, but while talking and discussing changes
Sebastian Urbach wrote:
Hi,
Another exiting Debian Binary Replacement has been released, As usual
you can find it right here:
http://key-server.org/sks/
The You talk, we work release:
Exiting. How exciting!
Yes, but while talking and discussing changes to be made with the entire
being considered for
inclusion into the tree maintained in cooperation with the original
developers of SKS.
Thank you,
-John Clizbe
SKS Contributor and maintainer
And on behalf of:
Yaron Minsky, SKS author
and SKS contributors:
Kim Minh Kaplan
Peter Palfrader
Johan van Selst
Sascha Silbe
John Clizbe wrote:
Jens told me about his success with cryptokit-1.5 a couple days after I pushed
my own work with 1.3. OCaml is frightening enough to the unitinitated. There
is no point adding another build complexity to SKS unless it is a) trivial, or
b) worth it. Read the Changlog
Jens Leinenbach wrote:
John Clizbe wrote:
Thank you for the medal. What sort of metal is bronce? Is it the result
of being exposed to too much lead as a child?
It's bronze. That's called typo. Or spanish. Not sure if lead exposure can
cause this.
There IS NO SKS VERSION 1.1.4! Yaron
to
nothing about SKS in general or about SKS in Debian with the exception of
lame ass excuses
of course.
Gold Medal : Christoph Martin / christoph.mar...@uni-mainz.de
Silver Medal : Fabio M. Di Nitto / fabbi...@fabbione.net
Bronce Medal : John Clizbe / jpcli...@gingerbear.net
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1,SHA256
Jens Leinenbach wrote:
Hi John,
I attached my changes as a patch. It should not break an existing SKS
installation and it should be easy to compile it for Debian with just a
few easy changes in settings.ml and adding the needed paths to
Jens Leinenbach wrote:
Hi John,
Hi Yaron,
I successfully compiled SKS with cryptokit v1.5 instead of the ancient
version 1.0:
http://forge.ocamlcore.org/frs/?group_id=133
If there's any interest, I can repack cryptokit v1.5 (some speedtest.ml
compile bug) and deliver a patch for SKS to
Jens Leinenbach wrote:
Hi,
I compiled SKS 1.1.3. for Debian, but I have a lot of trouble with
directories.
SKS seems to set all the files based on the directory configured in the
basedir variable.
And a basedir of . didn't work for me.
So I changed these variables in settings.ml:
let
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1,SHA256
Christoph Anton Mitterer wrote:
On Thu, 2012-04-26 at 12:01 +0200, Sebastian Urbach wrote:
I just want to offer tho host the debian sks packages anyplace,
anywhere, anytime so to say.
I guess one should really try to get updated packages
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1,SHA256
Daniel Kahn Gillmor wrote:
On 04/28/2012 09:26 AM, Jens Leinenbach wrote:
As already discussed on this list, there is this old SKS bug using POST
requests without sending the http version, so ngnix denies these POST
request.
And I didn't
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1,SHA256
Christoph Anton Mitterer wrote:
On Fri, 2012-04-20 at 19:44 -0500, John Clizbe wrote:
See my message from last night with the 11:38PM CDT timestamp.
Upgrading for DB is pretty painless.
Well if this is not possible, just add a NEWS entry
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1,SHA256
Johan van Selst wrote:
Daniel Kahn Gillmor wrote:
Fix?
I'm afraid i don't know ocaml at all, so i don't have a proposed fix.
It seems to be related to the event loop model on the sks db process,
though. Looking at it from a system
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1,SHA256
Daniel Kahn Gillmor wrote:
On 04/20/2012 08:44 PM, John Clizbe wrote:
I think we could host the .deb(s) on the Google Code download page
Would you need a .deb. for each Debian release?
If the packaging meets debian quality standards, i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1,SHA256
Christian Felsing wrote:
Hello,
key.ip6.li should now reachable again. There are issues:
EPEL package sks-1.1.3-0.2.20120124hg.el6.x86_64 contains version 1.1.2
# rpm -qa|grep sks
sks-1.1.3-0.2.20120124hg.el6.x86_64
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1,SHA256
John Clizbe wrote:
Robert J. Hansen wrote:
On 4/20/12 2:22 PM, Daniel Kahn Gillmor wrote:
I suspect the trickiest parts might be thinking about how to get a
smooth upgrade from 1.1.1 and possibly how to deal with a transition
to a newer
Kristian Fiskerstrand wrote:
On 19.04.2012 18:10, Kristian Fiskerstrand wrote:
Dear list,
...
Does anyone have any tips on how to resolve this?
I got around the error by downgrading ocaml to 3.10.2.
Trying to use 3.11.2 (earliest package found in gentoo portage) I
ended up with same
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1,SHA256
Kristian Fiskerstrand wrote:
On 19.04.2012 18:10, Kristian Fiskerstrand wrote:
Dear list,
Does anyone have any tips on how to resolve this?
I got around the error by downgrading ocaml to 3.10.2.
I'll save off my existing KBD and PTree
Phil Pennock wrote:
On 2012-04-12 at 18:02 -0500, John Clizbe wrote:
Presently, I have the search order as the list:
[ index.html; index.htm; index.shtml; index.xhtml;
index.xhtm; index.xml; ]
if none of these are found index.html will be returned so to have a
meaningful
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1,SHA256
Teun Nijssen wrote:
Hi John,
on 2012-04-11 05:00 John Clizbe wrote the following:
Hello,
We are pleased to announce the availability of a new SKS release:
Version 1.1.3.
nice; congratulations.
Thank you. There's still more to do
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1,SHA256
Phil Pennock wrote:
On 2012-04-11 at 01:40 -0500, John Clizbe wrote:
make dep
I just verified I was able to cause the same error by removing .depend.
It worked normally again after ' make dep'.
That worked, thank you.
I also forget
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1,SHA256
Sebastian Urbach wrote:
Hi,
If somebody needs a favicon.ico as well, here's mine. If you want to
have a other graphic and don't know hot wo do it, just mail me the
file :-)
The HTML part inside index.html is pretty direct. Did you use a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1,SHA256
Daniel Kahn Gillmor wrote:
The following patch probably also needs to be applied to the development
tree:
--- sks-1.1.2.orig/script.ml 2009-03-25 22:14:44.0 -0400
+++ sks-1.1.2/script.ml 2012-04-05 17:29:43.0
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1,SHA256
John Clizbe wrote:
I'm not sure if I have access to pull things from my repo into the main tree
or
if only Yaron can do it. I've done a fair amount since we cut 1.1.2.
I do not. I can pull my changes into a local copy of sks-keyserver
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1,SHA256
Anyone else seeing this?
- Original Message
Subject: Unauthorized server connections
Date: Thu, 05 Apr 2012 22:11:58 -0500
From: John Clizbe jpcli...@gingerbear.net
To: ab...@mozilla.com, webmas...@mozilla.com
There appears
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1,SHA256
Christoph Egger wrote:
Hi!
Recently I started to see failures in my recon.log:
2012-04-04 23:35:59 Error getting missing keys: Failure(!DOCTYPE HTML
PUBLIC \-//IETF//DTD HTML 2.0//EN\)
2012-04-05 00:57:10 Error getting missing keys:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1,SHA256
Peter Kornherr wrote:
Sorry, I forgot to mention the sks log entry for that request:
2012-03-20 23:19:18 Miscellaneous error: Failure(parse_post failed for lack
of a content-length header)
Is this a client problem or a matter of my
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1,SHA256
Daniel Kahn Gillmor wrote:
Hey SKS folks--
It appears that SKS 1.1.1's hkp interface is vulnerable to an ugly DoS
attack by a client holding open a network connection without completing
an HTTP request.
snip
---
I'd be very happy
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1,SHA256
Sebastian Urbach wrote:
Hi,
Do we have the owner of 75.9.55.99 here on this list ?
sks@booboo:~# host sks.keyservers.net
sks.keyservers.net has address 75.9.55.99
sks@booboo:~# grep sks.keyservers.net /var/sks/membership
sks.keyservers.net
1 - 100 of 179 matches
Mail list logo
