-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 2012-05-31 05:08, John Clizbe wrote:
> Yaron Minsky wrote:
>> John? Seems like you're the main person who I haven't heard a
>> response from. How do you feel about switching to bitbucket?
>
> Sorry for the late reply, Long weekend at BF's place
On Wed, May 30, 2012 at 9:22 PM, Ari Trachtenberg wrote:
> The problem with the second plan is that the potential number of
> differences
> between hosts could grow quite large, degrading performance.
>
The deleted keys would be considered as present from the point of view of
the reconciliation
On Wed, May 30, 2012 at 11:08 PM, John Clizbe wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1,SHA256
>
> Yaron Minsky wrote:
> > John? Seems like you're the main person who I haven't heard a response
> > from. How do you feel about switching to bitbucket?
> >
> Sorry for the late reply
On 05/31/2012 01:41 AM, Gabor Kiss wrote:
> You have trust a long and thin chain of signatures between you
> and your abroad comrade. What if a government agent edged in the chain?
1. Then you're goatscrewed, because you're trusting the wrong people,
and there is *no* technology that can help
> > You have trust a long and thin chain of signatures between you
> > and your abroad comrade. What if a government agent edged in the chain?
>
> 1. Then you're goatscrewed, because you're trusting the wrong people,
> and there is *no* technology that can help you
What if you have no choice
keyservers.org is a Fedora 15/x64 system running on hardware that's
coming to the end of its expected useful life. isaiah.keyservers.org is
a Fedora 17/x64 system running on much newer and beefier hardware. The
old system runs SKS 1.1.1; the new runs SKS 1.1.3. Both come from the
Fedora repos.
On 05/31/2012 09:30 AM, Kiss Gabor (Bitman) wrote:
> What if you have no choice?
Let me repeat: if you're trusting the wrong people then you're
goatscrewed and there is no technology that can help you.
There is no Option B.
___
Sks-devel mailing list
S
On 05/31/2012 09:33 AM, Robert J. Hansen wrote:
> Now for where things get wacky: running the exact same command, but with
> -n 20 instead of -n 10, causes a segfault in a different part of the code:
-n 5 crashes in yet a different place, although it manages to actually
get through a couple of the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1,SHA256
Having a night of heavy thunderstorms, it looks like the cable/HSI supplying
keyserver.gingerbear.net took a cable cut ~4:28 AM CDT. This is verifiable by
turning on any TV in the house. :-(
sks-keyservers.net AT&T U-Verse link is still up and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1,SHA256
Appears that all is back to normal... for now.
- -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. This is verifiable by
> turning
-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
On 5/31/12 11:58 AM, John Clizbe wrote:
> Other than the name being somewhat offensive in some English speaking
> countries?
I'm going to chime in here on the side of the "git isn't necessary" crowd.
Git is a fine RCS for large distributed projects. For the Linux kernel
it's almost ideal. But
-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'
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1,SHA256
https://bitbucket.org/jpclizbe/sks-keyserver/wiki/Home
Yaron, the link is already set to s/jpclizbe/yminsky/
Wiki syntax is a bit different. See http://wikicreole.org/wiki/Creole1.0
- -John
- --
John P. Clizbe Inet: John
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 2012-05-31 02:30, Yaron Minsky wrote:
> Thanks for creating a clearly separated fork. I look forward to
> seeing the source!
>
I believe this is available as a Google Code fork/clone at
http://code.google.com/r/libfree-gnuks-keyserver/source/br
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 2012-05-31 18:51, John Clizbe wrote:
> 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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1,SHA256
Looks as if last night's storms caused a later failure on the CPE that started
~22:24 CDT. Reboots and resets of the cable modem have done no good.
It's not completely dead, the VoIP phone line is working *WHOOPEE*
keyserver.gingerbear.net will
17 matches
Mail list logo
