I’ve deployed three new Hockeypuck clusters, each in different datacenters, two
publicly facing and the 3rd is an internal hot spare that’s mostly mostly going
to do scheduled key dumps but will be capable of replacing either of the other
two clusters for maintenance/outages.. I intend to get th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hello!
I am looking for peers for a new SKS installation.
I am running SKS version 1.1.6 on pgp.pm.
The server is physically located in Chicago, Illinois, USA.
I see 5423749 keys loaded.
If you agree to peer with me, please respond to me direct
Who are the intended targets of this service?
Non-PGP users.
You can't control the senders environment, maybe an old windows box
with keystroke logging, backdoors, etc. It's not my intention to be
the MITM. Yes it's a matter of trust.
Best
Jan
Gabor Kiss :
> Simple, we're using client
Simple, we're using client side encryption, you can review the
javascript code in your browser. The server/service receives encrypted
messages and send it to the receiver. The server/service can't decrypt
your message, it's PGP.
Best
Jan
"Kiss Gabor (Bitman)" :
Hello Kiss,
"Gabor" pl
Hello Kiss,
Take a look into the source code :-)
https://github.com/encrypt-to/encrypt.to
Best
Jan
"Kiss Gabor (Bitman)" :
What a great idea of NSA...
:-)
___
Sks-devel mailing list
Sks-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/
Lukas, you got an error message? What does dislike mean?
Thanks
Jan
Lukas Martini :
Hej,
ignoring the complete discussion on PGP encryption in browsers etc., one
quick thing: Your site dislikes my email address (lut...@ohai.su),
presumably due to the unusual TLD (.su is the old ccTLD of th
Thanks Lukas,
Oh yes we need to improve.
Lukas Martini :
Hej,
On 12/10/2013 03:19 AM, John Clizbe wrote:
How does the code handle keys with multiple email addresses? Does
it mail-bomb
them all?
I just tried and got mails to all my UIDs, so yes.
http://i.imgur.com/b1INK0w.png
Best,
Luk
Thanks John,
John Clizbe :
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 do
Thanks for your feedback.
Kristian Fiskerstrand :
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
an
>
> Frank
>
>
> --
> frank.villaro-dixon.eu - PGP: 6F36914A
> Envie d'électricité 100% verte ? Enercoop.fr
> What is a Velomobile ? www.sans-essence.eu
> ___
> Sks-devel mailing list
> Sks-devel@nongnu.org
20 PM, Frank Villaro-Dixon wrote:
On 13-12-09 12:56:09, Stephan Seitz, wrote 2.6K characters saying:
Hi there,
Hi,
Am Samstag, den 07.12.2013, 13:27 +0100 schrieb PGP Key Admin:
We love PGP! :-)
so I do. But, why are you going to use it in such a ummm grotesque
flavour?
If one's using that se
ards
Jan
Stephan Seitz :
Hi there,
Am Samstag, den 07.12.2013, 13:27 +0100 schrieb PGP Key Admin:
We love PGP! :-)
so I do. But, why are you going to use it in such a ummm grotesque
flavour?
If one's using that service he/she has to trust your service and
toolchain. It's complete
Hello Filip,
Now back again :-)
Thanks
Jan
Filip Stefaniak :
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
PGP Key Admin napisal(a):
We love PGP! :-)
We would like to make PGP as usable as possible for everyone. With
https://encrypt.to <https://encrypt.to/> you can send enc
Hello Dmitry,
The JS lib is open source: http://openpgpjs.org
Regards
Jan
"Dmitry Yu Okunev (pks.mephi.ru)" :
Hello.
On 12/07/2013 04:27 PM, PGP Key Admin wrote:
We love PGP! :-)
We would like to make PGP as usable as possible for everyone.
With https://encrypt.to <https
We love PGP! :-)
We would like to make PGP as usable as possible for everyone. With
https://encrypt.to you can send encrypted messages to PGP users and you can
receive encrypted messages from non-PGP users. We are using client side
encryption and we can't decrypt the message.
How does it work?
Hello Friends,
My new SKS keyserver running version 1.1.14 on pgpkey.org. Please add my new
keyserver to your list of gossip peers.
pgpkey.org 11370 # PGP Key Admin 0xB41D959A
The server is physically located in Germany (EU). The machine has IPv6
connectivity.
Status: http://sks
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
A big thank you for everyone who replied.
My server is fully up and running and I even got included in the pool,
which is pretty neat.
Thanks
On 8/21/2013 11:11 PM, ad...@gpg.im wrote:
> Hi All,
>
> I have a new keyserver running and would like to
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:
sks.gpg.im 11370 # 0x61845FFF
Thank you.
___
Hi all,
I have a couple of quick noobish questions...
I noticed this tweet:
https://twitter.com/abditum/status/352271467196588035
It refers to a key retrieved from pgp.mit.edu that the keyserver is
not allowing removal of. I noticed it was also available from
sks.pkqs.net, but didn't check any
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
LOL, the funny thing is that I have SEEN spoofed emails, containing the
necessary BEGIN PGP lines
as well, being read on non-pgp-enabled clients... and the reader would trust it.
On 03/04/2013 08:44 AM, Giovanni Mascellani wrote:
> Il 04/03/2013 1
Hi Folkert,
On 24/01/2013 12:40, folkert wrote:
> I feel kind of stupid now.
I always enjoy feeling stupid, because it means I'm learning :)
Cheers,
James
___
Sks-devel mailing list
Sks-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/sk
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
On 15/01/2013 16:09, DGRphone SKS Admin wrote:
> The line for the membership file should now read:
>
> sks.nimblesec.com 11370 # James Thomas 0xE600C820
>
> I'm BCC'ing all my peers along with this message, an
11370 # James Thomas 0xE600C820
I've changed the hostname, from_addr, and sendmail_cmd lines in my
sksconf file to reflect this. Previous DNS entries will remain valid,
and no IP addresses will be changing.
I'm BCC'ing all my peers along with this message, and the new a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Kristian,
On 26/11/2012 14:51, Kristian Fiskerstrand wrote:
>
> Try a "make cleanall"
>
This solved it!
Thank you very much.
- --
James Thomas
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with undefined -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
I'm attempting to install sks 1.1.4 on my new keyserver, which is
currently running Linux Mint 13 and using the 1.1.1 ubuntu packages.
I'm running into an issue when compiling. Here's a paste of what
happens when I try.
http://pastebin.com/y
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
I've set up a new keyserver and am interested in peering with some of
you fine folk. Please add me to your 'membership' file with the
following, and provide your details in exchange:
sks.dgrphone.net 11370 # James Thomas 0x5E523E17
Thank
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 03/13/2012 06:08 PM, Daniel Kahn Gillmor wrote:
> 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.
Sounds just like the kind of vu
If you need dns servers, I'd be happy to add your zones to mine. They're 3, on different geographic
zones.
On 07/08/2011 09:24 AM, Edson Brandi wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I'm having hardware issues with DNS server responsible for name
resolution of keyserver.fug.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 08/19/2010 07:17 PM, Jonathan Wiltshire wrote:
> This is a private machine in London, but it's publicly accessible. It will
> have IPv6 too in the future.
As soon as it becomes IPv6 let me know, I have an IPv6 server (can someone test
sks ipv6 p
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 07/14/2010 06:25 PM, Paul Collins wrote:
> barbadine.canonical.com 11370 # Canonical Sysadmins
What keyid for r...@admin.canonical.com ?
Cheers,
Buanzo
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Phil Pennock wrote:
> On 2010-01-07 at 14:54 -, crich...@fishysnax.com wrote:
>> I am looking for peers for a new SKS keyserver installation at
>> keyserver.fishysnax.com.
>
> Any idea why your PGP signature might have been marked BAD when my
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Daniel Kahn Gillmor wrote:
> PS i'm very interested in what you're working on, as i suspect i've been
> thinking over similar things. If you want to chat off-list about your
> project (or direct me to somewhere i can discuss it with you), let me kno
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Daniel Kahn Gillmor wrote:
> The output should already be machine-parseable (though it's not XML).
OK, so, I want this:
http://sks.buanzo.org:11371/pks/lookup?op=vindex&search=0x025A4EB06857704D
into mr.
But if I add &options=mr, then I get less
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Daniel Kahn Gillmor wrote:
> The output should already be machine-parseable (though it's not XML).
> Have you read David Shaw's I-D which documents the interface?
Lol, I was JUST starting to read it :)
Thank you Daniel.
-BEGIN PGP SIGNATURE---
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
MailFighter.net Admin wrote:
> I'll start testing it right away. Thanks everybody.
OK. The logs show that keys are being received, and all 4 membership entries
appear to be functional.
What I still need is to configure my mailsync file,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi everybody!
I've compiled by hand (I had to tweak /usr/include/bits/string3.h in Ubuntu
9.10 for it to compile,
just change line 96 from __extern_always_inline to __extern_inline, ugly, but
works, remember to
change it back).
I've setup my memb
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Daniel Kahn Gillmor wrote:
> Are you filing bugs about this with ubuntu? it would be really good for
> them to know that their packages are busted (with as much detail as
> possible).
It's this Debian bug: http://bugs.debian.org/cgi-bin/bugreport.c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
John Clizbe wrote:
> I ran
> sks build -n 13 -cache 100 /var/sks/dump/*.pgp
r...@mx4:/var/lib/sks# sks build -n 13 -cache 100 /var/sks/dump/*.pgp
unknown timeout type argument to DB_ENV->rep_get_timeout
Segmentation fault
It SIGSEGV's immediate
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Jens Leinenbach wrote:
> Where/when exactly do you get the segfault? After starting sks_build.sh?
> Does your system run out of memory?
See below for a trace.
> E.g. if you don't have much RAM:
r...@mx4:/var/lib/sks# free -m
total
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
First of all,
Thanks to everyone that emailed me off-list offering to peer up. :)
Now, I finished downloading the dump, but I'musing Ubuntu, and it fails with a
segfault. I know it's
got to do with different versions of libdb (compiled vs runtime)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hello! I'm in the process of becoming part of the sks pool. I'm currently
downloading the dump (will
be over in 30 more minutes), then I'll build the database, and after all that,
I'll ask for some
peers to gossip with.
My server (sks.buanzo.org b
41 matches
Mail list logo