Re: [Sks-devel] Bitbucket?
-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. And a slew of > catch up once I got home. > > Haven't had a lot of time to look at it. There is a nice > centrality to Google, but I'm really tired of Google's SSL cert of > the week when I push. > > How difficult will it be to migrate existing repos: trunk, me, > Kristian, etc? The Fork mechanism on bitbucket is rather good. Just create your own new fork (press the fork button), check it out and do a hg pull ../old-repo , I've already done so at [0] and created a pull request back into main trunk[1]. [0] https://bitbucket.org/kristianf/sks-keyserver [1] https://bitbucket.org/yminsky/sks-keyserver/pull-request/1/cache-control-and-updated-documentation - -- - Kristian Fiskerstrand http://www.sumptuouscapital.com Twitter: @krifisk - Corruptissima re publica plurimæ leges The greater the degeneration of the republic, the more of its laws - This email was digitally signed using the OpenPGP standard. If you want to read more about this The book: Sending Emails - The Safe Way: An introduction to OpenPGP security is now available in both Amazon Kindle and Paperback format at http://www.amazon.com/dp/B006RSG1S4/ - Public PGP key 0xE3EDFAE3 at http://www.sumptuouscapital.com/pgp/ -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBCAAGBQJPxyI9AAoJEBbgz41rC5UIJPEP/3JGgNciKzsoC+r/wYhqnVji dexie+EG3i1C9DdHZoG0+4mmMKvLPkDiUlAEKUe4WllIf6bzc5Btt4ePfWMecJ2K aDWqwjw6il6/zPWbdSls3vAXWO/IjWyLAP3kOcez07+eFRZanAQgxlWh6xq9CmJA GnFT1nx+WQ7SFZXVqMF/B2R9dj3qWbHgrV8dEUDrDvmMTiBlBz+N1ZhdeoNrkdUp vrxk7b+2qUpaf3dyMb5NX1H48v8lXhXitgL2PLw19BSY5vNMgClHl3jIoqbmrRCI xhhv4ik27sqyTwM8mrJu2h89fEU48+XYpW0U0nOVSfGsoWRIc/r4uCHbZ1wWoS7C DQGGaDGMNeDQ/ay9uZ6XWC0fr9nkCkZZyLP/Xi5ahJa7GhCtpAbJ+YroVNRY0vS3 sYxtUZ9nGWXtAbbxiYf/A/cz7PCIt93+8dKZWsiP24eruYSmoB/3blKB1D+P1NyG wssNh2OV/0j0Ju1QTbC/aBUJIwfZgQ4bvfadiun+6TxFOBFwkdrsQ1L48m5GTxjQ f1/yR7x3sodkhUBW/JiHmWEFsVjwtbWfWSDW3pgIIruz/0w3Ks5MQO4Jnn9wMQZE NJuStgXjomIDHNKtwzxW3RLKJ47LkADfgrmAs/y/rWltLLtfZay6YCuAtL4fD26j 2GD5YPWKi5sG2Imep8sq =Yedd -END PGP SIGNATURE- ___ Sks-devel mailing list Sks-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/sks-devel
Re: [Sks-devel] 0xd5920e937cc1e39b shows signatures with 0xca57ad7c continuing?
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 algorithm, so I'm not sure it would truly degrade performance. The only issue is, what do you do if the first time you learn of a key is from someone who deleted it? That said, I think there is a reasonable heuristic one could use here: don't add the key for awhile, seeing if you're going to encounter someone in the reconciliation who actually has the key. And if you don't, eventually learn it as an "unknown" key, and add it to your Ptree. That said, GC'ing the deletions is an issue, but it's just the keyid you need to keep, so it's not so bad. > The easiest solution would be to auto-expire keys after a fixed time > (a good strategy anyway from a security perspective). > > Best, >-Ari > > On May 30, 2012, at 7:55 PM, Yaron Minsky wrote: > > > Here's my quick sense of what the reasonable solutions are: > > > > - Add a key-deletion authority, as Gabor suggested. These deletion > > certificates would be gossiped around, and would lead to deletion of > keys. > >The deletion certificates would stick around for a long time, but > they'd > > be small, so the cost would be low. One coud have them auto-expire at > a > > specified time out, so that you eventually can GC them. > > - Have SKS have a local key-deletion file. Keys listed in the key > > deletion file would be excluded from the local set, but would probably > be > > kept in the Ptree, so that they don't show up as a difference when > > reconciling. People can work together to distribute key-deletion files > > from a trusted source, but it's at the discretion of the manager of any > > individual key server. > > > > The second one seems more likely to work as a social matter, since > building > > an agreed, trusted authority is tricky. > > > > (To say the obvious, I don't have the time to work on implementing either > > approach. But I'm happy to have others do so. Something like this was > > part of my original plans for SKS, but it never got done.) > > > > y > > > > On Sun, May 27, 2012 at 6:15 AM, Robert J. Hansen >wrote: > > > >> On 5/27/12 5:50 AM, Giovanni Mascellani wrote: > >>> I'm just a newbie here, but actually I'd like to see the same concept > >>> applied in a more general way: I think there is much garbage in the > >>> keyservers, even behind the PGP robo-signer. > >> > >> The problem here is this violates one of the principle design features > >> of the keyserver network: > >> > >> "We never, never, never lose certificates." > >> > >> It is preferable for a keyserver to outright go down than it is for even > >> one certificate to be lost. If a certificate is lost then a malicious > >> actor could re-upload another key with the same short ID (a very easy > >> thing to do), and that could facilitate all different kinds of attacks > >> on people who don't properly validity-check certificates before using > them. > >> > >> If the keyserver goes down then everyone knows in short order there's a > >> problem. If a certificate is lost and silently replaced it might be a > >> long time before being discovered. (Discovery is more likely if the > >> keyserver is synchronizing with others, but there are a lot of > >> standalone servers.) > >> > >> Further, expired certificates are still useful. I have some emails more > >> than five years old that are still relevant and useful. If a > >> certificate gets removed just because it expires, how am I to check the > >> signature on those messages in order to ensure they haven't been > >> tampered with? If the expired certificate remains on the servers, > >> though, I can download it, validity-check it, and be confident in the > >> integrity of my message. > >> > >> The same logic applies to revoked certificates: they're still useful for > >> the same reasons. > >> > >> The keyservers never, never, never lose certificates. That's a design > >> goal and one that the SKS maintainers believe is a good one. I agree > >> with them, and want to see this design goal maintained in all future > >> development. > >> > >> That said, welcome to the community, and please understand that although > >> I think your idea is awful I'm honestly happy to see you here. :) The > >> mailing list is a place where ideas come into violent collision, but we > >> try to be reasonable human beings to each other. Welcome! > >> > >> ___ > >> Sks-devel mailing list > >> Sks-devel@nongnu.org > >> https://lists.nongnu.org/mailman/listinfo/sks-devel > >> > > ___ > > Sks-devel mailing list > > Sks-devel@nongnu.org > > https://lists.nongnu.org/mailman/listinfo/sks-devel > > --- > Ari Trachtenberg
Re: [Sks-devel] Bitbucket?
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, Long weekend at BF's place. And a slew of catch > up > once I got home. > > Haven't had a lot of time to look at it. There is a nice centrality to > Google, but I'm really tired of Google's SSL cert of the week when I push. > > How difficult will it be to migrate existing repos: trunk, me, Kristian, > etc? > > That's my only question. Other than that, for now I'm site-agnostic. > I think it's quite easy. I migrated my trunk, and it was very straightforward. I just got a pull request from Kristian, which I put some comments on before including, which was also pretty easy. > - -John > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.12-git-509fe4ce-2012-01-31 (Windows XP) > Comment: When cryptography is outlawed, bayl bhgynjf jvyy unir cevinpl! > Comment: Be part of the £€€7 ECHELON -- Use Strong Encryption. > Comment: It's YOUR right - for the time being. > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ > > iQEcBAEBAgAGBQJPxuCWAAoJECMTMVxDW9A0ax0H/0MR3ZrjTz5HlSe+p1t6lN8g > gDc72XlFqOxhFm3SHRIe9CJ42nUjJgu6G2VIpNEMOnm0B4MZIsfiaxKNqrbkzew+ > 5mVscZT19QKzGPjvWARkNVO3pC6240XAtl8DLHiHB0E3ykRJ2iuXyRVH/LVW1nR5 > gktmgxZCSKs9pjnVckI0w7uERShlsT/13FBaOhiSEO+Q6xm/T+ZlQ9ddIqTu5pAa > zXFj5aZ2v+cJzo1tcb/4dMNcOy0xQgPPvDeqIdiiOzPrK9YOw9g+BDoYsDbOFgcQ > YS46bWrt8vKHeBrtelfy+CRkObmJDAKChJPFk5AdYGJlA5rUkLXgs02E+6PyFO6I > XgQBEQgABgUCT8bglgAKCRDrXhnz1laYJQF/AP4k0cdd9NApsN+PLRfRV1VPUh0m > Dwh790wY2hX8cEpXBgD/UkpJ34u0sYkU3wFV6FpulYYLyYLcqQQ1GLYWBpyHY3M= > =mqnR > -END PGP SIGNATURE- > ___ Sks-devel mailing list Sks-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/sks-devel
Re: [Sks-devel] 0xd5920e937cc1e39b shows signatures with 0xca57ad7c continuing?
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 2. There is no #2. ___ Sks-devel mailing list Sks-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/sks-devel
Re: [Sks-devel] 0xd5920e937cc1e39b shows signatures with 0xca57ad7c continuing?
> > 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? A trusts B, the only trustworthy people in the city who is allowed to travel. B trusts C, who is honest but a bit naive. C trusts D, who is a secret agent. D signs fake keys owned by Big Brother. Big Brother signs a fake E' key then distributes it via the only key server A can reach. What can A do if he wants to send encrypted mail to the real E? Gabor ___ Sks-devel mailing list Sks-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/sks-devel
[Sks-devel] SKS segfaulting on Fedora 17
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.
I made a dump of the current KDB from keyservers.org and migrated it
over to isaiah, where it was placed in a subdirectory 'dump' off of my
sks dir (/var/sks).
Once there, from /var/sks I did an sks build run as follows:
sks build -n 10 -cache 100 /var/sks/dump/*.pgp
And bam, instant segfault. build.log is not useful:
2012-05-31 01:51:59 Opening log
2012-05-31 01:51:59 Opening KeyDB database
That's it. Running gdb on the sks binary reveals:
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Loading keys...done
Program received signal SIGSEGV, Segmentation fault.
SHA1_copy_and_swap (numwords=, dst=0x7f7feff0,
src=0x77cbe948) at sha1.c:38
38 d[0] = s[3];
(gdb) l
33unsigned char * s, * d;
34unsigned char a, b;
35for (s = src, d = dst; numwords > 0; s += 4, d += 4, numwords--) {
36 a = s[0];
37 b = s[1];
38 d[0] = s[3];
39 d[1] = s[2];
40 d[2] = b;
41 d[3] = a;
42}
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:
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Loading keys...done
Program received signal SIGSEGV, Segmentation fault.
0x00509713 in caml_darken ()
(gdb) l
1 /* interp - add information about dynamic loader to shared library
objects.
2 Copyright (C) 1996 Free Software Foundation, Inc.
3 This file is part of the GNU C Library.
4
5 The GNU C Library is free software; you can redistribute it and/or
6 modify it under the terms of the GNU Lesser General Public
7 License as published by the Free Software Foundation; either
8 version 2.1 of the License, or (at your option) any later version.
9
10 The GNU C Library is distributed in the hope that it will be useful,
... If any of the SKS maintainers want to take a look at this _in situ_,
I'd be happy to provide access to isaiah for debugging purposes.
___
Sks-devel mailing list
Sks-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/sks-devel
Re: [Sks-devel] 0xd5920e937cc1e39b shows signatures with 0xca57ad7c continuing?
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 Sks-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/sks-devel
Re: [Sks-devel] SKS segfaulting on Fedora 17
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 .pgp files first. The dump files are large (50,000), but the server is fairly beefy: 32Gb RAM and an i7. It shouldn't be hitting any hardware limitations: it's far more capable than the current keyservers.org is, and it handled this without a hiccup. I have no idea what the root cause of this segfault is, but it certainly seems interesting. ___ Sks-devel mailing list Sks-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/sks-devel
[Sks-devel] keyserver.gingerbear.net offlne
-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 functional. (ATM bridge wedged for a bit between 6:25 and 8:55) Until connectivity is restored the servers of keyserver.gingerbear.net will be unaccessible to the public, but will remain caught up with the SKS network through local peering with the servers of sks.keyservers.net. Bit of a PITA we worry about with every storm. Usually we just lose power until the UPS batteries are drained completely. - -John - -- John P. Clizbe Inet: John (a) Gingerbear DAWT net SKS/Enigmail/PGP-EKP or: John ( @ ) Enigmail DAWT net FSF Assoc #995 / FSFE Fellow #1797 hkp://keyserver.gingerbear.net or mailto:pgp-public-k...@gingerbear.net?subject=HELP Q:"Just how do the residents of Haiku, Hawai'i hold conversations?" A:"An odd melody / island voices on the winds / surplus of vowels" -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12-git-509fe4ce-2012-01-31 (Windows XP) Comment: When cryptography is outlawed, bayl bhgynjf jvyy unir cevinpl! Comment: Be part of the £7 ECHELON -- Use Strong Encryption. Comment: It's YOUR right - for the time being. Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJPx3i3AAoJECMTMVxDW9A0n5MH/A095uotVUm0V+rucoNZ0GKT ZmQWbIE84RGp+C4fPsk9p7MjdN/8iAygALM2SC76mJOFQHifcOT6c2CkXoiiAfDr 5a4TshoQh1GyTIUPb48KKKmCmf0hmGm2OtYxGoNe2LBrNIGDRkC2WJ5arYyPJ+Ac C/5DlQgbyyq7OX+B3c3oyTbALC+jObhhgLf3kQ4rrnAvbmoXUKVm9uzKk1JuL521 UuMdcBwjEOUAL2s5kJxmIGoktl0cMIU8bBEGSloZPmXas0A4YHV4Z9ZPEtYvU/pg 7lB5H+tJ413qaSYCh7oTXbAKck1LdKyX6MZvkuprPdCDWuWbhpIKXRPzYhEtcYaI XgQBEQgABgUCT8d4twAKCRDrXhnz1laYJUmnAP9NDTwDKSlc1ODwCD0430TnO5SH t5u+8e1B1Z+BrBLsYwD/Zjg6sFInuMGjkKzAKwZkduL1kX7kCj1n1r5dT0Hrzno= =/Vjd -END PGP SIGNATURE- ___ Sks-devel mailing list Sks-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/sks-devel
Re: [Sks-devel] keyserver.gingerbear.net offlne -- Resolved
-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 on any TV in the house. :-( > > sks-keyservers.net AT&T U-Verse link is still up and functional. (ATM bridge > wedged for a bit between 6:25 and 8:55) > > Until connectivity is restored the servers of keyserver.gingerbear.net will be > unaccessible to the public, but will remain caught up with the SKS network > through local peering with the servers of sks.keyservers.net. > > Bit of a PITA we worry about with every storm. Usually we just lose power > until the UPS batteries are drained completely. > > -John - -- John P. Clizbe Inet: John (a) Gingerbear DAWT net SKS/Enigmail/PGP-EKP or: John ( @ ) Enigmail DAWT net FSF Assoc #995 / FSFE Fellow #1797 hkp://keyserver.gingerbear.net or mailto:pgp-public-k...@gingerbear.net?subject=HELP Q:"Just how do the residents of Haiku, Hawai'i hold conversations?" A:"An odd melody / island voices on the winds / surplus of vowels" -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12-git-509fe4ce-2012-01-31 (Windows XP) Comment: When cryptography is outlawed, bayl bhgynjf jvyy unir cevinpl! Comment: Be part of the £7 ECHELON -- Use Strong Encryption. Comment: It's YOUR right - for the time being. Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJPx40kAAoJECMTMVxDW9A0r3oH/2gQI9JoOJ0yB+GZCS/Vb+Fj M5b7u/YohrGavcAsaece1jlcScxsLEkRu5OhwryYBkHXHHB7Ktu93Jfms/D+4o0O Pbv17RvDw/HYs0Dze0AofQucG2whVfUBnvLzk2/3dCkZPQZGL/BKwrbwnmNCU03g jfMFA54OYW+GME12/e7oWbTuDrtxzfeRCr017C2KRjD//Myll+iGvAOrzww5WwmN LMnTNsQB3njY82j1hlUrR/lYeE+Th7FdV0VPErBmIUV72sMSvl3WFcQePP4jkOoW hFswAxxvWZOZ43ibpBSaif4j+qQY+gGpHd1CD3vYfqtjX8UJNzXzGwhQzD2prW6I XgQBEQgABgUCT8eNJAAKCRDrXhnz1laYJX9XAP9s0El3IiQGMmsLz2dA19ThHW+i A3xUnAZhqKzbX8YV6wD+KgtvKCJfsjmaowslRptG3p3TV4YLxD8hB0BTLlEpaZk= =W3Er -END PGP SIGNATURE- ___ Sks-devel mailing list Sks-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/sks-devel
Re: [Sks-devel] Bitbucket?
-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 some English speaking countries? Sent from my VAX -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12-git-509fe4ce-2012-01-31 (Windows XP) Comment: When cryptography is outlawed, bayl bhgynjf jvyy unir cevinpl! Comment: Be part of the £7 ECHELON -- Use Strong Encryption. Comment: It's YOUR right - for the time being. Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJPx5UfAAoJECMTMVxDW9A0yjUH/i2jfd4P+bIfVSebGWUANR/H sxrhEkcXSlvrIJbqq2ASUL/RzdoLXje6L+VwUKPOBfIRFd1ZI4tDnGHg31ruRTmj y9WYBnJtTiLdgXmB1ElPWIAHDoiO/EM1RfgteO+CcLyQIVVUXXnb4MN89WCnjkcg VTzSbDunP1AM6i0Ln++3oeBH8RqgraY+gHgVRgf/tXz2xWmokFip/NQwk7OuYMka B2tb0rPhc2EOGy5VYXR3lGTiT57u6GV8juDxZKE9WEcy0lVa20VJh5Sy68fFzkmH avBKAmR60rwnJR6Hz+oW9pBp50QBDn1fqIDW6o7nfYANx0PIM7gopLRdqCB5s7SI XgQBEQgABgUCT8eVHwAKCRDrXhnz1laYJYdhAP4qRT8mznpt8ILMosVRK3Vw/hR/ gSK+llCXhgMDSM4Y8AD+M+/KxGMVuHYn7OdkJ7Q4t0kigitD4nqecx25YyRAzJ0= =9M2T -END PGP SIGNATURE- ___ Sks-devel mailing list Sks-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/sks-devel
Re: [Sks-devel] Bitbucket?
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 SKS is not a large distributed project: it's a fairly small one, is unlikely to grow into a huge one, and I'm not sure it's worth the additional complexity over other simpler RCSes. Feel free to emphatically disagree, of course. :) signature.asc Description: OpenPGP digital signature ___ Sks-devel mailing list Sks-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/sks-devel
Re: [Sks-devel] [patch] Clocks and VMs
-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 not immediately bad. > > Can someone who can reproduce the timing problems try this out please? > The Cygwin Ocaml compiler is acting up so I'm rebuilding from source. This has always been a VERY EASY problem to reproduce on Win32 on top of Cygwin. sks db runs fine, it's just recon that blows up. I'm looking forward to trying out this patch on Windows - -John - -- John P. Clizbe Inet: John (a) Gingerbear DAWT net SKS/Enigmail/PGP-EKP or: John ( @ ) Enigmail DAWT net FSF Assoc #995 / FSFE Fellow #1797 hkp://keyserver.gingerbear.net or mailto:pgp-public-k...@gingerbear.net?subject=HELP Q:"Just how do the residents of Haiku, Hawai'i hold conversations?" A:"An odd melody / island voices on the winds / surplus of vowels" -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12-git-509fe4ce-2012-01-31 (Windows XP) Comment: When cryptography is outlawed, bayl bhgynjf jvyy unir cevinpl! Comment: Be part of the £7 ECHELON -- Use Strong Encryption. Comment: It's YOUR right - for the time being. Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJPx6F4AAoJECMTMVxDW9A0iPEH/2bYhShvZt83i9Y2xrwjgezg TTFn8LEZSKsTq194k8pj7Dr8/cLDURfPuuEav+W7MmTAktNTL0JnsVmzFLs+yg1i tBWKvmMOFwG1Jgh6QTEas2JhynhTYVFVAF+iys98LbOewvnpazbHY7QFaHVHhWjJ eAn49w/eUW8cM0AdOfq5gqTsr25O7BpCepFWSOi+Zt2dD+PcIXIyOnjZXBkMr5tO mSGJ/eR/HwFD8DE/g1GfvwV1uMEM8qtlJ54F11qYpo8tujma6O2Wnh6u5jtPD5ML 5N8YP4NhFBRSB2xCD05zacquB/KxO70FoFdGu3syNJgj7lxOK62nWuTv//J7ccOI XgQBEQgABgUCT8eheAAKCRDrXhnz1laYJYRmAP9MyRQIdmugU1bvIEDA1nZkbbcq c73+MCYYlLFtL2pORQD/bdJkTumpRrxXJ5nBVbrWyx+LrnmpysBm5MhW/IwiMuE= =Ixd4 -END PGP SIGNATURE- ___ Sks-devel mailing list Sks-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/sks-devel
[Sks-devel] The Wiki has been moved to BitBucket
-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 (a) Gingerbear DAWT net SKS/Enigmail/PGP-EKP or: John ( @ ) Enigmail DAWT net FSF Assoc #995 / FSFE Fellow #1797 hkp://keyserver.gingerbear.net or mailto:pgp-public-k...@gingerbear.net?subject=HELP Q:"Just how do the residents of Haiku, Hawai'i hold conversations?" A:"An odd melody / island voices on the winds / surplus of vowels" -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12-git-509fe4ce-2012-01-31 (Windows XP) Comment: When cryptography is outlawed, bayl bhgynjf jvyy unir cevinpl! Comment: Be part of the £7 ECHELON -- Use Strong Encryption. Comment: It's YOUR right - for the time being. Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJPx7u2AAoJECMTMVxDW9A0lKYIAKxwGQWJLhgSLLbUajXtduB4 hnZrzJd76C6tFCwrsI8y6eVGkuaPvWjuQHAomIE5UkdRos814d7a7a3vjNcufwU6 Un5Cgp7MX8jyUGUZ5DPVjl2d03chLTrfr+fMJ3gje7gJvuAODyq3jpFfkpV5J90P PmZiT0Zz2/yvOUKIEgWmlFKAmGJmgQrFzALRgUR2XmXs1trdOOSizmhu9yoZrpC+ LkTjxdes+KI8hLTd9+kEBE9N79uXd9GKEuCuEIWE04LO9Gz1Eda39tP8QJM15yT/ nJ1oGGOcg8jSUt+T1FVN98/L/r4kKQsH4JFHA7odSka/CJQ+K7cBpyyKYV80rkCI XgQBEQgABgUCT8e7tgAKCRDrXhnz1laYJYUwAPoCrxb6Y3Cu7yK0l1LLdNmm9FW7 uqBr+2BMQ7tctNC5zgD/SsLoidtjADzq9hrUK5XjFDbpSB8mCzay2H1kRrc1ISQ= =cswK -END PGP SIGNATURE- ___ Sks-devel mailing list Sks-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/sks-devel
Re: [Sks-devel] Div.
-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/browse - -- - Kristian Fiskerstrand http://www.sumptuouscapital.com Twitter: @krifisk - Corruptissima re publica plurimæ leges The greater the degeneration of the republic, the more of its laws - This email was digitally signed using the OpenPGP standard. If you want to read more about this The book: Sending Emails - The Safe Way: An introduction to OpenPGP security is now available in both Amazon Kindle and Paperback format at http://www.amazon.com/dp/B006RSG1S4/ - Public PGP key 0xE3EDFAE3 at http://www.sumptuouscapital.com/pgp/ -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBCAAGBQJPx9hcAAoJEBbgz41rC5UI0EwQALdiMpwf5DZXeNPPWhFFXGij EJRxlYzWuTyxPewgR9fW3IedmqXSxFMquB+9S2Un3f6ycfhQElnO/Comk0XYs94i ucIJWDIMqypO5L78CJlwuw1tCMkf3CaJJOzTN3BFoAaEl9Q0LIHtAtDGIRaxbhl8 MbtKDzHRMcWlEoJ6UKrUo3L5T9XoQm4V5X/2o+x0kW8t76ALVEnvWCkpXy3Ofj9q yckD7VENsi+VcTMvyRxkEiTdVd1hHwW92r0MmVhRYbURnlSUdXWW1n/fnjtlW0In lVlh6BwlU09zY2PoGGzxeQ2T/Oru+ncX7YCVOBwUoN0beheG65D9Mi+kiwke5ytR 2+EL8LiE6Z1JyO7HppMKb+qJTqw489cUL0Uz0tSDs46Fipb1VwMBEF+av3R2bRPA /nmwjKrW/n6aF8mS6uHZC2qruJNCxBteNCLwPHnpxkkQ51vduYDkrNE3bJp3os1B cdT1Q618P6I+KvKgQeNTUK08+4dgbJaK1y0h2HeyEH2kAPCeYj/38cZaiofaXzll Ux2W4TBaKP7YpsYh9MMPMhLydB/pLE6TJmf7w5Nb8Y7yvHq8ctIc2s4rocnTt93K 61O2d70taTeWjLu80X9wJp2xLWvo9prb+ZtSKIEVN84W5rgu4z3gxYp6Py0PRUG3 /hXCnVguhTp47ptoMshE =aQZD -END PGP SIGNATURE- ___ Sks-devel mailing list Sks-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/sks-devel
Re: [Sks-devel] [patch] Clocks and VMs
-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 a peer >> with this code applied. So it's not immediately bad. > >> Can someone who can reproduce the timing problems try this out >> please? > > The Cygwin Ocaml compiler is acting up so I'm rebuilding from > source. This has always been a VERY EASY problem to reproduce on > Win32 on top of Cygwin. sks db runs fine, it's just recon that > blows up. > I'll hold off on experimenting with the clocksource in a VM then until you can test it on Cygwin. - -- - Kristian Fiskerstrand http://www.sumptuouscapital.com Twitter: @krifisk - Corruptissima re publica plurimæ leges The greater the degeneration of the republic, the more of its laws - This email was digitally signed using the OpenPGP standard. If you want to read more about this The book: Sending Emails - The Safe Way: An introduction to OpenPGP security is now available in both Amazon Kindle and Paperback format at http://www.amazon.com/dp/B006RSG1S4/ - Public PGP key 0xE3EDFAE3 at http://www.sumptuouscapital.com/pgp/ -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBCAAGBQJPx9jTAAoJEBbgz41rC5UIWFIP/0laff/oIV5XgYRnIAqDfkkJ 6ijqadgXafZ3P3DUe9wTeMPaNq3Iq7BlHEiZ1wE+SvpYVScLMc5dy6OyngNg3VMI PHDl7ndi+WtheNZ0pD5Iunm7sSJQzpg1jCpxl1Ui3ZkpfGEV1C43XURdz+sbfjiu ST1VJ8Xz+3UfBPfdtb55mE8SK+qKV66TnrLsRuoM+d83GDzmTK6f3pNKV9sYkMGX avACadnBG7gF/5mJwtu7Ufw5A0dbyAzNVC3bEteIWsXB5xExuQOd5fcFui5TSU01 JjCBXh/F2wg96c6+beeC2Cgjfi9XqPTlc/oc3gxCWYXE29I9ks6u/6aukZR+RpnK 2fxjIT23q1rNyfwyeQ5WmnuFjdY0oJvppwmbabdHzKans6zp9X0RtJuf0cHhI2kn tDGeRjcQg1vEGrnyU2GRK29tWkXC+B1SyUC/3FVM/KV2r4YPc+hcpr8V/KmIQ7GY iZB6kWWF7Zn1LMayBCX5jARPn6SG2z6Fn3ewxUJHhuPT2H927jA8NMESlE53fCPd 44SEYiLYJMdnJNOeIpBeE8DvUotUfKpJDxfe4+QdjFE64WorSJOsByi0B1cFhAqV YE5fqX34AmiyPpjFJAsCspr7wdPTg7AkKAaP/2X9aFqi/k29paMwsHQcpj1TIKcW F2YsWvbgaJJio3HCclLe =hBm6 -END PGP SIGNATURE- ___ Sks-devel mailing list Sks-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/sks-devel
Re: [Sks-devel] keyserver.gingerbear.net offlne
-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 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. This is verifiable by > turning on any TV in the house. :-( > > sks-keyservers.net AT&T U-Verse link is still up and functional. (ATM bridge > wedged for a bit between 6:25 and 8:55) > > Until connectivity is restored the servers of keyserver.gingerbear.net will be > unaccessible to the public, but will remain caught up with the SKS network > through local peering with the servers of sks.keyservers.net. > > Bit of a PITA we worry about with every storm. Usually we just lose power > until the UPS batteries are drained completely. > - -- John P. Clizbe Inet: John (a) Gingerbear DAWT net SKS/Enigmail/PGP-EKP or: John ( @ ) Enigmail DAWT net FSF Assoc #995 / FSFE Fellow #1797 hkp://keyserver.gingerbear.net or mailto:pgp-public-k...@gingerbear.net?subject=HELP Q:"Just how do the residents of Haiku, Hawai'i hold conversations?" A:"An odd melody / island voices on the winds / surplus of vowels" -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12-git-509fe4ce-2012-01-31 (Windows XP) Comment: When cryptography is outlawed, bayl bhgynjf jvyy unir cevinpl! Comment: Be part of the £7 ECHELON -- Use Strong Encryption. Comment: It's YOUR right - for the time being. Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJPyGEaAAoJECMTMVxDW9A0hhsIANfG3TmwtQHCLwJtKXWWAQQw ERRjDCPtqVMn1Wz1k6y5a//0QthzW7IUUqjIKnH8DR+dxd8W5bdQ+MfIDW/ELml1 L32U9u1a4q/zvagj7ca2Sw4beADHMiU1m8Mqp02VvDk3BudLhd55Nf7dDzVeo8gb EynPNpqKMKXaSTPLAbjnPahngFQSVuVO/OYJ9Md4W8+SkcCQVv57TbZ5a7jezsqU L3mDJi4/Uvc2au6FscXlW29RBqihX9E74YXDzdvREnImblIRMNNsuPMZsA5GTGfr 5ZjcX35D8sYgpEMgdce3fTfQxZEeQBu+4arQCYj1VdgrFbk0rPZ+N7wWs822GPuI XgQBEQgABgUCT8hhGgAKCRDrXhnz1laYJfVyAP93tzLjuUhwlHtrNfHzmcboC9s+ iTrdroP+SxTQETilXgD/QYTET4tj6Ne+wWc3dleQITvhl82PUOL1ei2qs5UHyLo= =omnT -END PGP SIGNATURE- ___ Sks-devel mailing list Sks-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/sks-devel
