Re: [Sks-devel] pool.sks-keyservers.net down?
It appears to depend on the ISP at this point. For me, Qwest is working, AT&T and MCI are not. -Joe On Thursday, August 13, 2009, at 11:33AM, "Sebastian Wiesinger" wrote: >* Christoph Anton Mitterer [2009-08-13 19:42]: >> On Thu, 2009-08-13 at 10:39 +0200, Sebastian Wiesinger wrote: >> > I entered pool.sks-keyservers.net as keyserver address in GnuPG but it >> > doesn't return any A/ records at the moment. >> For me it works ;) > >Yeah, works again for me too. But it didn't work when I sent my first >mail. I also tried it at the authoritative servers for the zone to be sure. > >Regards, > >Sebastian > >-- >New GPG Key: 0x93A0B9CE (F4F6 B1A3 866B 26E9 450A 9D82 58A2 D94A 93A0 B9CE) >Old GPG Key-ID: 0x76B79F20 (0x1B6034F476B79F20) >'Are you Death?' ... IT'S THE SCYTHE, ISN'T IT? PEOPLE ALWAYS NOTICE THE >SCYTHE. >-- Terry Pratchett, The Fifth Elephant > >___ >Sks-devel mailing list >Sks-devel@nongnu.org >http://lists.nongnu.org/mailman/listinfo/sks-devel > > ___ Sks-devel mailing list Sks-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/sks-devel
Re: [Sks-devel] pool.sks-keyservers.net down?
* Christoph Anton Mitterer [2009-08-13 19:42]: > On Thu, 2009-08-13 at 10:39 +0200, Sebastian Wiesinger wrote: > > I entered pool.sks-keyservers.net as keyserver address in GnuPG but it > > doesn't return any A/ records at the moment. > For me it works ;) Yeah, works again for me too. But it didn't work when I sent my first mail. I also tried it at the authoritative servers for the zone to be sure. Regards, Sebastian -- New GPG Key: 0x93A0B9CE (F4F6 B1A3 866B 26E9 450A 9D82 58A2 D94A 93A0 B9CE) Old GPG Key-ID: 0x76B79F20 (0x1B6034F476B79F20) 'Are you Death?' ... IT'S THE SCYTHE, ISN'T IT? PEOPLE ALWAYS NOTICE THE SCYTHE. -- Terry Pratchett, The Fifth Elephant signature.asc Description: Digital signature ___ Sks-devel mailing list Sks-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/sks-devel
Re: [Sks-devel] Improving the SKS development model
On Thu, Aug 13, 2009 at 05:40:04PM +, Kim Minh Kaplan wrote: > as raw PGP files with modifications in the Berkeley DB. Is there any > particular reason you chose not to dump all the keys in Berkeley DB and > then do without the dump directory? I reckon this is because of initial import duration (build vs pbuild) only. Personally, I am against using pbuild exactly for reasons you said. -- NAME:Dinko.kreator.Korunic DISCLAIMER:Standard.disclaimer.applies ICQ:16965294JAB:kreator...@jabber.orgPGP:0xEA160D0B HOME:http://dkorunic.netQUOTE:Eat.right.stay.fit.and.die.anyway ___ Sks-devel mailing list Sks-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/sks-devel
Re: [Sks-devel] pool.sks-keyservers.net down?
On Thu, 2009-08-13 at 10:39 +0200, Sebastian Wiesinger wrote: > I entered pool.sks-keyservers.net as keyserver address in GnuPG but it > doesn't return any A/ records at the moment. For me it works ;) # dig pool.sks-keyservers.net any ; <<>> DiG 9.6.1-P1 <<>> pool.sks-keyservers.net any ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 43102 ;; flags: qr rd ra; QUERY: 1, ANSWER: 19, AUTHORITY: 2, ADDITIONAL: 0 ;; QUESTION SECTION: ;pool.sks-keyservers.net. IN ANY ;; ANSWER SECTION: pool.sks-keyservers.net. 21600 IN 2001:41d0:1:e812:1c:c0ff:fe65:2cd4 pool.sks-keyservers.net. 21600 IN 2a01:198:328:488::189 pool.sks-keyservers.net. 21600 IN 2a02:898:31:0:48:4558:73:6b73 pool.sks-keyservers.net. 21600 IN 2001:470:1f0a:d4::2 pool.sks-keyservers.net. 21600 IN 2001:610:1108:5011:230:48ff:fe12:2794 pool.sks-keyservers.net. 21600 IN 2001:638:204:10::2:1 pool.sks-keyservers.net. 21600 IN 2001:738:0:1:209:6bff:fe8c:845a pool.sks-keyservers.net. 21600 IN 2001:1418:1d7:1::1 pool.sks-keyservers.net. 21600 IN 2001:16d8:ee30::4 pool.sks-keyservers.net. 21600 IN A 79.47.84.242 pool.sks-keyservers.net. 21600 IN A 84.16.235.61 pool.sks-keyservers.net. 21600 IN A 84.253.50.136 pool.sks-keyservers.net. 21600 IN A 87.98.166.252 pool.sks-keyservers.net. 21600 IN A 98.218.83.144 pool.sks-keyservers.net. 21600 IN A 161.53.2.216 pool.sks-keyservers.net. 21600 IN A 194.171.167.98 pool.sks-keyservers.net. 21600 IN A 195.22.207.161 pool.sks-keyservers.net. 21600 IN A 195.111.98.30 pool.sks-keyservers.net. 21600 IN A 202.191.99.51 ;; AUTHORITY SECTION: sks-keyservers.net. 21600 IN NS ns1.kfwebs.net. sks-keyservers.net. 21600 IN NS ns2.kfwebs.net. ;; Query time: 90 msec ;; SERVER: 84.16.235.61#53(84.16.235.61) ;; WHEN: Thu Aug 13 19:41:04 2009 ;; MSG SIZE rcvd: 496 Regards, Chris. smime.p7s Description: S/MIME cryptographic signature ___ Sks-devel mailing list Sks-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/sks-devel
Re: [Sks-devel] Improving the SKS development model
Yaron Minsky writes: > Wow! You've been working hard. Your repo contains 30-some patches consisting > of 3k lines of diffs! Are you proposing pushing all of that to the mainline > tree? No most of them are old commits in other branches that I did while finding my way around mercurial and preparing the other patches that you already included some months ago. But I don't know enough about Mercurial to hide them. The only interesting patches are word index patch (977e38781686) as well as a tail recursion fix (c67b2f226c24), the two last commits. I still have some other commits in a private repository but I do not thing they should be published (except may be a reverse signature index but I have to investigate more first). On an other topic, I see that the preferred storage mecanism for keys is as raw PGP files with modifications in the Berkeley DB. Is there any particular reason you chose not to dump all the keys in Berkeley DB and then do without the dump directory? I ask the question because it feels like over time the keys in the dump directory will consist of many unused keys as they have been updated and now leave in the Berkeley DB. Kim Minh. ___ Sks-devel mailing list Sks-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/sks-devel
Re: [Sks-devel] Re: Improving the SKS development model
I did not update the CHANGELOG properly. I'll do that for the 1.1.2 release. y On Thu, Aug 13, 2009 at 3:52 AM, John Clizbe wrote: > Yaron Minsky wrote: > > One other note: I finally cut a 1.1.1 release. It is on the google code > > site. > > What patches are included? > > I didn't see any entries for 1.1.1 in the CHANGELOG > > -- > John P. Clizbe Inet:John (a) Mozilla-Enigmail.org > You can't spell fiasco without SCO. 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" > > > ___ > Sks-devel mailing list > Sks-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/sks-devel > ___ Sks-devel mailing list Sks-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/sks-devel
Re: [Sks-devel] Improving the SKS development model
Wow! You've been working hard. Your repo contains 30-some patches consisting of 3k lines of diffs! Are you proposing pushing all of that to the mainline tree? y On Thu, Aug 13, 2009 at 1:06 AM, Kim Minh Kaplan > wrote: > Yaron Minsky writes: > > If people would put up public hg repos containing their patches and >> emailed me when they thought they were ready for inclusion in the mainline, >> I would be happy to manage the process of pulling that in and of cutting >> releases. >> > > My repository (http://www.kim-minh.com/hg/sks/) now includes the recent > index patch (977e38781686) as well as a tail recursion fix (c67b2f226c24). > > Kim Minh. > ___ Sks-devel mailing list Sks-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/sks-devel
[Sks-devel] pool.sks-keyservers.net down?
Hi, I entered pool.sks-keyservers.net as keyserver address in GnuPG but it doesn't return any A/ records at the moment. Reading the list archive this isn't the first time. I'm now using my own SKS server but shouldn't the pool address be made more reliable? $ dig pool.sks-keyservers.net A +short $ Regards, Sebastian -- New GPG Key: 0x93A0B9CE (F4F6 B1A3 866B 26E9 450A 9D82 58A2 D94A 93A0 B9CE) Old GPG Key-ID: 0x76B79F20 (0x1B6034F476B79F20) 'Are you Death?' ... IT'S THE SCYTHE, ISN'T IT? PEOPLE ALWAYS NOTICE THE SCYTHE. -- Terry Pratchett, The Fifth Elephant signature.asc Description: Digital signature ___ Sks-devel mailing list Sks-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/sks-devel
Re: [Sks-devel] Re: Improving the SKS development model
Yaron Minsky wrote: > One other note: I finally cut a 1.1.1 release. It is on the google code > site. What patches are included? I didn't see any entries for 1.1.1 in the CHANGELOG -- John P. Clizbe Inet:John (a) Mozilla-Enigmail.org You can't spell fiasco without SCO. 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" ___ Sks-devel mailing list Sks-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/sks-devel
