On 9/30/19 1:53 PM, Todd Fleisher wrote:
> Gabor,
> SKS on port 11371 will not have SSL, so the URL should be
> http://sks.e-utp.net:11371/pks/lookup?op=stats … https on port 443 for
> that URL does return data: https://sks.e-utp.net/pks/lookup?op=stats
>
>
>> On Sep 30, 2019, at 10:41 AM, Kiss
On 9/5/19 9:28 AM, Francisco Monserrat wrote:
> Hello ,
>
>
> It seems that all the peers my keyservers are currently down so both
> keyserver are outside the sks network, so please can anyone add the keyserver
> to their membership and tell me
>
My key server is currently down because of a
On Sun, Jun 16, 2019 at 11:04:16PM +0100, Andrew Gallagher wrote:
>
> > On 16 Jun 2019, at 22:32, Vincent Breitmoser wrote:
> >
> > Anyone got some good idea on how to continuously sync certificate updates
> > from
> > the SKS pool?
>
sks also has an option to send email (using the old
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I'm running it. The address is keyserver2.brian.minton.name:11371
(IPv6 only), if you want to try it out. I'm using the postgresql JSONB
backend, which seems to perform better than the MongoDB backend. The
DB usage is more or less steady, at
need some assistance from
Kristian. That being said, I think I am still experiencing the
problems others have been reporting on the list.
regards,
Brian Minton
-BEGIN PGP SIGNATURE-
iHUEARYIAB0WIQTu0BWAE9wubW4AHqQ3uVB6z/IBbgUCXCOCfwAKCRA3uVB6z/IB
bsgzAQD1WP6Vx9T+U1BJt/ZmFErJJ4zlquTUvKBHu
ewhere that is wrong.
In the mean time, my sks server is limping along, trying to load half its keys
from gossip...
--
Brian Minton
brian at minton dot name https://brian.minton.name
Live long, and prosper longer!
OpenPGP fingerprint = 8213 71DD 4665 CF4F AE20 2206 0424 DC19 B678 A1A9
signature.
,
Brian Minton
br...@minton.name
-BEGIN PGP SIGNATURE-
iHUEARYIAB0WIQTu0BWAE9wubW4AHqQ3uVB6z/IBbgUCXAcJKAAKCRA3uVB6z/IB
bpm8AQCNhFt26yqMEZU1SqPSW79f7oEChIapyeCu7qJTximxhwEA4WWSQjhqKXZ2
GKIaRKrisEXH5AgIwOAO38HTydT53AiIdQQBEQgAHRYhBPnEu3YOeD8N7BCmimuO
s6Blz7qpBQJcBwkoAAoJEGuOs6Blz7qp/CwA/29Jq
0x6FC10EAE0B5C3FC4
It's traditional to mention how many keys you have. Nevertheless, I'll peer
with you:
keyserver.brian.minton.name 11370 # Brian Minton
0x821371DD4665CF4FAE2022060424DC19B678A1A9
thanks,
--
Brian Minton
brian at minton dot name https://brian.minton.name
Live long, and prosper lon
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I've added you, please add me back.
keyserver.brian.minton.name 11370 # Brian Minton
0x821371DD4665CF4FAE2022060424DC19B678A1A9
-BEGIN PGP SIGNATURE-
iHUEARYIAB0WIQTu0BWAE9wubW4AHqQ3uVB6z/IBbgUCW2rl3QAKCRA3uVB6z/IB
bsGJAQCxCt+UetnhGE
I've been using them both for a while, and hockeypuck seems to stay synced.
It's not in the pool, but it seems to work to sync locally to my sks instance.
--
Brian Minton
brian at minton dot name https://brian.minton.name
Live long, and prosper longer!
OpenPGP fingerprint = 8213 71DD 4665 CF
On 12/08/2017 01:39 PM, Kristian Fiskerstrand wrote:
> On 12/08/2017 08:34 PM, Fabian A. Santiago wrote:
>> is there any reason to enable mailsync functionality? does anyone out there
>> still use it?
Last I checked, pgp-public-k...@the.earth.li is still accepting mailsync
emails.
Please don't send encrypted email to the list. Nobody will be able to read
it.
___
Sks-devel mailing list
Sks-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/sks-devel
t; intended primarily for personal use but anyone can use it.
You can peer with me:
keyserver.brian.minton.name 11370 # Brian Minton <br...@minton.name>
0x0424DC19B678A1A9
--
Brian Minton
brian at minton dot name http://brian.minton.name
Live long, and prosper longer!
OpenPGP fingerprint
On Fri, May 05, 2017 at 11:53:38AM -0400, Keith Erekson wrote:
>
> pgp.lehigh.edu 11370 # Keith Erekson <ke...@lehigh.edu> 0xC9A3C33D
You can peer with me. I'm also in Pennsylvania.
keyserver.brian.minton.name 11370 # Brian Minton <br...@minton.name>
0x0424DC19B678A1A9
--
You can peer with me:
keyserver.brian.minton.name 11370 # Brian Minton <br...@minton.name>
0x0424DC19B678A1A9
On 03/27/2017 02:54 AM, Franck Nijhof wrote:
> Dear reader,
>
> I am looking for peering partners for my new SKS keyserver;
> keyserver1.gnupg.pub.
>
>
I've added you. Please add me:
keyserver.brian.minton.name 11370 # Brian Minton <br...@minton.name>
0x0424DC19B678A1A9
signature.asc
Description: OpenPGP digital signature
___
Sks-devel mailing list
Sks-devel@nongnu.org
https://lists.nong
since hockeypuck.fidocon.de seems to have an ipv6
address, that's not a problem.
--
Brian Minton
brian at minton dot name http://brian.minton.name
Live long, and prosper longer!
OpenPGP fingerprint = 8213 71DD 4665 CF4F AE20 2206 0424 DC19 B678 A1A9
signature.asc
Description: PGP sig
ded. Please add me, with the following membership line:
keyserver.brian.minton.name 11370 # Brian Minton <br...@minton.name>
0x0424DC19B678A1A9
thanks,
--
Brian Minton
brian at minton dot name http://brian.minton.name
Live long, and prosper longer!
OpenPGP fingerprint = 8213 71DD 4665 CF4F AE20 2206 0
ending the HTTP 417 status upon receipt of Expect: 100-continue.
I've updated my config and I no longer get that error on POST. Kristian, if
you'd be so kind as to update the example lighttpd config, and add the
following line:
server.reject-expect-100-with-417 = "disable"
Thanks,
--
Br
On 10/06/2016 10:23 AM, Kristian Fiskerstrand wrote:
> Checked my notes, the 417 Expect test is related to clients publishing
> keys (--send-key) being rejected and not gossipping.
That makes sense. Clients submitting a key by POST could send that header.
signature.asc
Description: OpenPGP
On 10/06/2016 09:55 AM, Brian Minton wrote:
> I'm not sure about it. I generated a test key, and uploaded it to my
> server. Let's see if any peers get it:
> pub 2048R/1609776C 2016-10-06
> Hash=5B4454EAC3D51127B65622D49C76A7EA
> Fingerprint=603E 1A2F 7344
On 10/06/2016 09:24 AM, Kristian Fiskerstrand wrote:
> On 10/06/2016 03:21 PM, Brian Minton wrote:
>> So, there, I'm seeing the error. I'm guessing that the script Kristian is
>> using is sending the Expect: 100-continue header, while the actual sks client
>> is not. Otherw
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Oct 4, 2016 11:11 AM, "Danny Horne" wrote:
>
> I didn't, they were both bminton.is-a-geek.net
>
I only changed the hostname field in the sksconf file. Both names go to the
same address, but the keyserver name triggers
pool
status script is reporting a 417 error.
https://bitbucket.org/skskeyserver/sks-keyserver/wiki/Peering#%21lighttpd
thanks,
--
Brian Minton
brian at minton dot name http://brian.minton.name
Live long, and prosper longer!
OpenPGP fingerprint = 8213 71DD 4665 CF4F AE20 2206 0424 DC19 B678 A1A9
kup?op=stats and checking
if my server was listed.
--
Brian Minton
brian at minton dot name http://brian.minton.name
Live long, and prosper longer!
OpenPGP fingerprint = 8213 71DD 4665 CF4F AE20 2206 0424 DC19 B678 A1A9
signature.asc
Description: PGP signature
___
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
How often do the scripts re-scan a host?
-BEGIN PGP SIGNATURE-
iF4EARYIAAYFAlfzFykACgkQN7lQes/yAW5RagD/bKOs7soR7zuhJjghWMVLGMC7
F/0rReQ2WRcaVXbzCpEBANwwNLi2L+nAI3N0lIraBcnq7jWHD8nhL6eeWEYpJfcO
rvers currently not in the pool" section. I thought it would
automatically show up. Any thoughts?
thanks,
- --
Brian Minton
brian at minton dot name http://brian.minton.name
Live long, and prosper longer!
OpenPGP fingerprint = 8213 71DD 4665 CF4F AE20 2206 0424 DC19 B678 A1A9
-BEGIN PGP
z Wirth <m...@corenetworking.de>
0x44b1cafa8705700f
keyserver.vsund.de 11370 # Valentin Sundermann <m...@vsund.de>
0xA1AADE57842A21A3 - onename.com/vsund
keys2.kfwebs.net 11370 #0x0b7f8b60e3edfae3
thanks,
Brian Minton
--
Brian Minton
brian at minton dot name http://brian.minton.name
Live long,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I'm getting a lot of errors in my logs about filter mismatch. For
instance
INET [144.76.185.42]:51252>) rejected: filters do not match.\n\tlocal
filters: [ yminsky.dedup ]\n\tremote filters: [ yminsky.dedup
yminsky.merge ]")
Is that something I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
One possibility would be to have the keyserver sort by the time the key
was first seen. That way, there'd be a slightly lower chance of
getting an impostor's key. Going by the creation date is not very
useful, since impostors could create their
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I'm taking keyserver.brian.minton.name offline for a few days to
rebuild the db. I've been having db issues for a while, and I think a
complete wipe and reload of the db may help.
thanks,
Brian Minton
-BEGIN PGP SIGNATURE-
Version: GnuPG
a_verify=> Good
> gpg: secmem usage: 0/65536 bytes in 0 blocks
And here's the output of receiving:
> gpg2 -vvv --debug 4 --recv DD1A52F9DA8C9020
> gpg: reading options from '/home/bminton/.gnupg/gpg.conf-2'
> gpg: using character set 'utf-8'
> gpg: enabled debug flag
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I just have my sks server listening on 127.0.0.1 for port 11371
traffic. The relevant line in sksconf is
hkp_address: 127.0.0.1
It's behind a reverse proxy that listens on the public ipv4 and ipv6
addresses, for port 11371 as well as port 80.
sysadmin-keys-memb...@fedoraproject.org (Nick
> Bebout)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I've added you as a peer (sorry it took so long, I had some server
issues). Please also add me. My membership line is:
keyserver.brian.minton.name 11370 # Brian Minton <br...@minton.name>
0x0424
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I've updated the ip addresses of my keyserver. If you are peering with
me using sks, you should touch your membership file to force an IP
rescan. If you are using hockeypuck, I think unfortunately a restart
is required (CMars, if you are reading
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
You can peer with me. Here is my membership line:
keyserver.brian.minton.name 11370 # Brian Minton <br...@minton.name>
0x0424DC19B678A1A9
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
iF4EARYIAAYFAldPLpYACgkQ
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
I generally just ignore the Host: header on port 11371.
-BEGIN PGP SIGNATURE-
iIAEAREKACghHEJyaWFuIE1pbnRvbiA8YnJpYW5AbWludG9uLm5hbWU+BQJXIjV8
AAoJEGuOs6Blz7qpWXgA/R3Wj2x2aSkoAKdwz7cBXdy9NVU+9cjA2xE1jn/aDWJO
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
I've had an ipv6 only one for a long time, but it was hockeypuck and so not
eligible for pool membership anyway.
-BEGIN PGP SIGNATURE-
iIAEAREKACghHEJyaWFuIE1pbnRvbiA8YnJpYW5AbWludG9uLm5hbWU+BQJXIhgx
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
You can peer with me.
keyserver.brian.minton.name 11370 # Brian Minton <br...@minton.name>
0x0424DC19B678A1A9
-BEGIN PGP SIGNATURE-
iIAEAREKACghHEJyaWFuIE1pbnRvbiA8YnJpYW5AbWludG9uLm5hbWU+BQJWmZhH
AAoJEGuOs6Blz7
The dump files are OpenPGP format. You can just use gpg as the tool. For
instance:
gpg < /var/lib/sks/dump/sks-dump-0203.pgp
On Mon, Jan 4, 2016, 5:11 AM Kiss Gabor (Bitman)
wrote:
> Dear folks,
>
> First of all I wish all of you happy new year.
>
> "And now for something
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
bminton.is-a-geek.net:~$ ocaml -version
The OCaml toplevel, version 4.02.3
b-BEGIN PGP SIGNATURE-
Version: GnuPG v2
iF4EARYIAAYFAlZOQgIACgkQN7lQes/yAW404gD/eFMEn5SO7pErFPKhzkTK7Pf/
I can try to do that.
On Mon, Aug 3, 2015, 11:01 AM James Cloos cl...@jhcloos.com wrote:
Is anyone who runs hockeypuck with postgress willing to provide a
pg_dump of the hockeypuck db?
I'd like to see how resource-intensive it is, from the db perspective.
If so, please use the --create
You can peer with me. I'm running Hockeypuck and always looking for
peers. Especially ones that don't mind my server occasionally going
down, as it is experimental, like yours.
Here's my membership line:
keyserver2.brian.minton.name 11370 # Brian Minton br...@minton.name
0x0424DC19B678A1A9
I think spreading out the load seems reasonable. I don't know how the pool
maintenance scripts would handle one server suddenly having 40k more keys.
On Mon, Aug 3, 2015, 12:58 AM Daniel Roesler diaf...@gmail.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Howdy all,
I have been
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
If you're interested in peering with my hockeypuck setup, I'd love to peer
with you. The address is keyserver2.brian.minton.name port 11370 for recon
and port 11371 for hkp traffic. The only requirement is that my server is
ipv6 only, so you have to
You can peer with me. I'm running Hockeypuck and always looking for
peers. Especially ones that don't mind my server occasionally going down,
as it is experimental, like yours.
Here's my membership line:
keyserver2.brian.minton.name 11370 # Brian Minton br...@minton.name
0x0424DC19B678A1A9
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I've been seeing some gossip traffic from pgp.kama.gs. I don't mind
peering with them (in fact I've added them to my membership file), but
they don't seem to be synchronizing to the network.
thanks,
Brian Minton
-BEGIN PGP SIGNATURE
this is a feature. However, you can manually trigger a stats calculation
by sending SIGUSR2 to the sks process.
On Fri, Jul 31, 2015 at 12:45 PM, Pascal Levasseur
pascal.levass...@topette.eu wrote:
Hello,
It seems to me that the 'Hourly Histogram' displayed in the stats HTML
web page
to load sks-dump-0206.pgp and, as
it is my first SKS server, I do not know if the loading time is
following a linear curve or an exponential one !
Best regards.
Pascal Levasseur
Le 21/06/2015 23:01, Brian Minton a écrit :
I've added you to my membership file. Please add me
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Well, I've finally gotten my hockeypuck server,
keyserver2.brian.minton.name back online after a long outage. (side
note, systemd can be very frustrating). If any of you have been peering
with me, thanks! You should be able to recon with me.
If
Stephan, do you have any plans to resume updating your keyserver dumps? I
really liked having them available via rsync.
On Mon, Oct 6, 2014 at 2:46 PM, Pete Stephenson p...@heypete.com wrote:
On Mon, Oct 6, 2014 at 7:52 PM, Brian Minton br...@minton.name wrote:
[snip]
It's fixed now
I've added you to my membership file. Please add me:
keyserver.brian.minton.name 11370 # Brian Minton br...@minton.name
0x0424DC19B678A1A9
I noticed that I can't connect to you, but then I read your email that your
ETA was June 24th. That seems like a rather long amount of time to load a
key
MESSAGE-
Hash: SHA512
On 02/11/2015 04:54 PM, Brian Minton wrote:
On Wed, Feb 11, 2015 at 9:24 AM, Kristian Fiskerstrand
kristian.fiskerstr...@sumptuouscapital.com wrote:
1 GnuKS:0.9.2 5 SKS:1.1.1 1 SKS:1.1.2 15 SKS:1.1.3 16 SKS:1.1.4 2
SKS:1.1.4+ 89 SKS:1.1.5 6 SKS:1.1.5
I've added you. Here's my membership line:
keyserver2.brian.minton.name 11370 # Brian Minton br...@minton.name
0x0424DC19B678A1A9
On Wed, May 20, 2015 at 1:15 PM, Jayden Callahan ra...@rizon.net wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I am looking for peers for a new SKS
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Tue, May 19, 2015 at 4:23 PM, Daniel Kahn Gillmor
d...@fifthhorseman.net wrote:
Alternately, a solid answer to the following question would help us to
make these sorts of decisions in a more fine-grained way over time:
* how do we update the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
keyserver2.brian.minton.name is back up, and I am pleased to say,
Hockeypuck 2 is very nice. It is faster, and smaller, and seems to
work quite well. I did have some issues with it, related to
documentation, but that's to be expected with a beta,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I take it running a http proxy is not an option? Alternatively, download
the source on one machine and build it, then transfer the binaries to your
production server.
-BEGIN PGP SIGNATURE-
Version: OpenKeychain v3.1.2
it back in two or three days.
Thanks for peering!
regards,
Brian Minton
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iF4EAREIAAYFAlU/iRUACgkQa46zoGXPuqkXJQD/Rse+zmtLRt/0dHbsXyQHFyzo
AybWdYKY70EImh3fedgA/2/W5ZifLwY4kTrsfQC8Hqk5ra1ViHe0GOV88CjEuq/F
=uAzZ
-END PGP SIGNATURE
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Here's an example of using haproxy to proxy non-http traffic. The
example uses SMTP, but it should work with any TCP/IP traffic.
http://www.linickx.com/load-balance-anything-with-haproxy
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
AP9GHHnhbG1bw4WghDKf7HEQbDTq0ZoJJe9A8EQXo1lHNw==
=+Lzg
-END PGP SIGNATURE-
On Mon, Apr 20, 2015, 4:36 PM Patrick Kahr patr...@nerds.lu wrote:
On 20/04/15 22:09, Brian Minton wrote:
I was thinking about running sks on a Raspberry Pi. What kind of
device are you using?
Running
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I was thinking about running sks on a Raspberry Pi. What kind of
device are you using?
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
iF4EARYIAAYFAlU1XPIACgkQN7lQes/yAW4GWwEAYDRD/delIgKey+NWc1JdAY2N
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
First of all, Thanks for your contribution to Debian! :-)
You can peer with me. Just add the following to your membership file:
keyserver.brian.minton.name 11370 # Brian Minton br...@minton.name
0x0424DC19B678A1A9
-BEGIN PGP SIGNATURE
When I first started my keyserver, I imported the dump without the fast
option. However, when running, the server process still has all the
dump files open (as shown by lsof. Can I convert the server's db to not
read the dump files?
signature.asc
Description: OpenPGP digital signature
And, related question: Will sks be okay if the dump files are modified
by an external process? I have a cron job set up to fetch the latest
dump files via rsync.
On 02/16/15 10:30, Brian Minton wrote:
When I first started my keyserver, I imported the dump without the fast
option. However
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Wed, Feb 11, 2015 at 9:24 AM, Kristian Fiskerstrand
kristian.fiskerstr...@sumptuouscapital.com wrote:
1 GnuKS:0.9.2
5 SKS:1.1.1
1 SKS:1.1.2
15 SKS:1.1.3
16 SKS:1.1.4
2 SKS:1.1.4+
89 SKS:1.1.5
My keyserver (keyserver.brian.minton.name) is down again for a few
hours. I'm converting the filesystem to brtfs (for the snapshots and
online shrinking). I hope this will be the last interruption for a while.
signature.asc
Description: OpenPGP digital signature
It's back up and running.
On 02/10/15 10:55, Brian Minton wrote:
My keyserver (keyserver.brian.minton.name) is down again for a few
hours. I'm converting the filesystem to brtfs (for the snapshots and
online shrinking). I hope this will be the last interruption for a while
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I will peer with you. Please add the following line to your membership
file:
keyserver.brian.minton.name 11370 # Brian Minton br...@minton.name
0x0424DC19B678A1A9
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
-
On Mon, Feb 2, 2015 at 10:26 AM, Brian Minton br...@minton.name wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I will peer with you. Please add the following line to your membership
file:
keyserver.brian.minton.name 11370 # Brian Minton br...@minton.name
0x0424DC19B678A1A9
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello, Robert.
You can peer with me. Please add the following line to your membership
file:
keyserver.brian.minton.name 11370 # Brian Minton br...@minton.name
0x0424DC19B678A1A9
regards,
Brian Minton
-BEGIN PGP SIGNATURE-
Version: GnuPG
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
You can peer with me. My membership line is:
keyserver.brian.minton.name 11370 # Brian Minton br...@minton.name
0x0424DC19B678A1A9
I've added you to my membership file
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I will peer with you. Here is my membership line:
keyserver.brian.minton.name 11370 # Brian Minton br...@minton.name
0x0424DC19B678A1A9
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
iF4EARYIAAYFAlSAoskACgkQN7lQes/yAW4c+gEAwITUl15
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jens, you can peer with my hockeypuck server:
keyserver2.brian.minton.name:11370
It's ipv6 only but that should be no problem.
You may also peer with my SKS keyserver:
keyserver.brian.minton.name 11370 # Brian Minton br...@minton.name
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Tue, Nov 11, 2014 at 11:54 PM, Evert van Harten evhar...@snelmail.nl
wrote:
keysrv.technl.net 11370 # E. van Harten evhar...@snelmail.nl 0x9E27CC40
I've added you. Here is my server info:
keyserver.brian.minton.name 11370 # Brian Minton br
, please note my new line for your
membership file:
keyserver.brian.minton.name 11370 # Brian Minton br...@minton.name
0x0424DC19B678A1A9
Thanks,
Brian Minton
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
iF4EARYIAAYFAlRcxpsACgkQN7lQes/yAW4BUgEAadOsq7jGfQtjeHYgf0+zSPmx
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
The hockeypuck server will probably be going up and down a lot as I
work out the kinks. One of the biggest is that the Raspberry Pi only
has 512MB of RAM, and the hockeypuck server tends to use more than
that. Even so, I'm having fun trying to
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
You can peer with me
keyserver.brian.minton.name 11370 # Brian Minton br...@minton.name
0xDBF6A5BA777DF487
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iEYEAREDAAYFAlQ9UQ0ACgkQ2/alund99If2HwCgjAwsAEDtZS+Z3HkBdYzb+gMw
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
On Mon, Sep 29, 2014 at 12:02:14PM -0400, Brian Minton wrote:
I noticed that my key db was out of date, and I checked the logs and
they are full of messages like
2014-09-29 11:26:54 recon as client error in callback.: Unix error:
Invalid
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
You can peer with me. Just use the following line in your SKS
membership file:
keyserver.brian.minton.name 11370 # Brian Minton br...@minton.name
0xDBF6A5BA777DF487
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iEYEAREDAAYFAlQy2FgACgkQ2
events
2014-09-29 11:54:11 Recon partner: ADDR_INET [176.31.199.181]:11370
2014-09-29 11:54:11 recon as client error in callback.: Unix error:
Invalid argument - connect()
2014-09-29 11:54:13 Marshalling: LogQuery: (5000,1412004354.592334)
Am I doing something wrong? Is my sks misconfigured?
--
Brian
events
2014-09-29 11:54:11 Recon partner: ADDR_INET [176.31.199.181]:11370
2014-09-29 11:54:11 recon as client error in callback.: Unix error:
Invalid argument - connect()
2014-09-29 11:54:13 Marshalling: LogQuery: (5000,1412004354.592334)
Am I doing something wrong? Is my sks misconfigured?
--
Brian
IPv4 connectivity.
I have loaded a keydump dated 2014-09-10.
I see 3714964 keys loaded.
For operational issues, please contact me directly.
keyserver.brian.minton.name 11370 # Brian Minton br...@minton.name
0xDBF6A5BA777DF487
Thank you,
Brian Minton
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
IPv4 connectivity.
I have loaded a keydump dated 2014-09-10.
I see 3714964 keys loaded.
For operational issues, please contact me directly.
keyserver.brian.minton.name 11370 # Brian Minton br...@minton.name
0xDBF6A5BA777DF487
Thank you,
Brian Minton
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
IPv4 connectivity.
I have loaded a keydump dated 2014-09-10.
I see 3714964 keys loaded.
For operational issues, please contact me directly.
keyserver.brian.minton.name 11370 # Brian Minton br...@minton.name
0xDBF6A5BA777DF487
Thank you,
Brian Minton
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
/ZxmzPUCaAeacDxAUh1U+DLIVE
=+DRX
-END PGP SIGNATURE-
On Tue, Sep 16, 2014 at 10:07 AM, Brian Minton br...@minton.name wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Hi,
I am looking for peers for a new SKS keyserver installation.
I am running SKS version 1.1.5
85 matches
Mail list logo