Re: [Sks-devel] New Debian Binary Replacement
On May 18, 2012, at 6:03 PM, Kristian Fiskerstrand wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On 2012-05-19 00:02, Jeffrey Johnson wrote: >> >> On May 18, 2012, at 5:58 PM, Kristian Fiskerstrand wrote: > >> >> Does she have a fingerprint registered in SKS key servers? >> > > In fact, she does have her own OpenPGP key :) > Then ask her for a clear delegated authority to inherit your birth right that noone will ever contest. Serously: I can do FL/OSS comedy standup on one leg with my eyes closed after 3 martinis: is there really a need to supply policy where de facto common sense might be saner? 73 de Jeff ___ Sks-devel mailing list Sks-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/sks-devel
Re: [Sks-devel] New Debian Binary Replacement
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 2012-05-19 00:02, Jeffrey Johnson wrote: > > On May 18, 2012, at 5:58 PM, Kristian Fiskerstrand wrote: > > Does she have a fingerprint registered in SKS key servers? > In fact, she does have her own OpenPGP key :) - -- - 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/ iQIcBAEBCAAGBQJPtsdLAAoJEBbgz41rC5UId3oP/1e9cYmdIrDjdPCBcWefuXT5 GBENnEFqwOcOzp/za7UTwL7ayuQsW/AnG+9zN+3pBmNdAmuyy9EjmHmTuJMPoQuS UkTLkcgotR8dRCpq8S6trM8hWwjVJILgLGgytCSWvcIptf3+4+e/qqT/tYwmuC1m MQHFVl6qLyLDMfDIDASEWe81Uzis3UpBaV7w+TeYdsGnPUL9FTczqZzJnALQUcTd N8scQEgyHGLpnylDFfIKKKwSbDIiM+6bzJSblqL0XROLoj51gtWgKBwsoRTfDroZ 6enrpShc/nt8yKq+p6rvRaBXxtr/UovM220jnlaxIZNw/RpOvBcDu+u/qdmNDvDF o4/tbYTgpOmXSgCcGCHQC6iYsGb7R4xQ11rnT3qTLF53iSPWNM5dM1AooQEN7OtS p5lVgtaL/+VY/S1LoEVsvlfl5YnkIPyiG1Yr4To1CnmVR+xZisjTa02/ERO++LKd r6+//oNeIEXDDrzOx1PpuOvtrn2g/50l21OumavK+QYG6E+jOMyKvFtMU0NnA30n qepn64wuy86FHxlUue8afDyV7rC4pYwE095V3cDbdCEhs5HGhGMqLmmET4e/rGzD E7iK5UZJQH/6Dh4LHeQHKyHtxNIAs5GLHuIj5e+xz95rxStqX2d2h6G/u9+tU41g 9jLwpeMUydCRNflia0KT =d2+r -END PGP SIGNATURE- ___ Sks-devel mailing list Sks-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/sks-devel
Re: [Sks-devel] New Debian Binary Replacement
On 05/18/2012 02:52 PM, Jeffrey Johnson wrote: > > And wouldn't patience to see whether there actually > is a SKS fork, with a need to specify forked version pool acceptance > criteria, perhaps with administrative delegation to inter-continental > and inter-national naming authorities, registered/distributed through DNS, > with creepy-toe certificate compliance, and more … wouldn't > a bit of patience be more prudent than this continued stoopid thread? I'm not sure what DNS has to do with this. But unless this fork is (assuming it comes to pass) going to establish its own keyserver pool separate from the current SKS, it is obviously going to have to work with existing servers. It seems to me self-evident that whether a new pool were created or not (and nothing I've seen suggests that it would be) that it would be best for all concerned if keyservers are compatible with each other. That said, your point about expecting people who are already pissed to comply with directives about the form a fork should take seems apropos. A false claim to authority can only make matters worse. -- David Benfell dbenf...@gmail.com ___ Sks-devel mailing list Sks-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/sks-devel
Re: [Sks-devel] New Debian Binary Replacement
On May 18, 2012, at 5:58 PM, Kristian Fiskerstrand wrote: > > If not, I take the liberty to exclude any keyserver being > non-compliant from the pool. > Yo mamma gave you that right and privilege when you were born ;-) Does she have a fingerprint registered in SKS key servers? 73 de Jeff ___ Sks-devel mailing list Sks-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/sks-devel
Re: [Sks-devel] New Debian Binary Replacement
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 2012-05-18 23:52, Jeffrey Johnson wrote: > > On May 18, 2012, at 4:43 PM, Kristian Fiskerstrand wrote: > >> >> I have started pondering on policy regarding a possible fork and >> its criteria for inclusion in the main pool of >> sks-keyservers.net >> > > Do these questions need explicit answers? > > Even if an answer for how to handle version forks were specified, > is there any reason to believe that anyone on a "fork" is going to > comply with the specification? If not, I take the liberty to exclude any keyserver being non-compliant from the pool. - -- - 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/ iQIcBAEBCAAGBQJPtsYQAAoJEBbgz41rC5UIClsP/jkqv3+/bUiSkijrk90/RWMF YuX2q2ShES7J1WTX10Akcy/Ahb31Hfqbqw1AXdqiDe7AOwSReEWpNFKYEgxh4fg7 JFl5XGjU/H+HwNWd8vX2syqnWsQ/oU+ak6A63Gu77S8Rbc5wREXVzzvje5QCCgRG b3aPue6Oyz7UUhEOTlTjpjATKCdwJ/1abDoSGYWA7J6SMBfsq/o0KFHuFhOf5ywT NaPL/C3laVW66j6RFxm67f6Hwmh71eywClfRrimgG0XjN6Dsm3zoJPUjVfUNpm53 pmjLzuELOtqydPnsp3NATFvlk/oZavs1BnyRsJkDGrWf9Al1MZIumcadHymToWFj KsLKBb7hQTpZxbhS5zJVgRtkbbxatSezRrp6QdAeiy2zqOWncd79YZayc4OsRILx 7oasL0eVe9T799ZCNdzoOSnEKlYEAgSomSwD9hbG2auQuO32T+GuvsnKw2xYD/jb m1qq9q5d96d/occxAztwQUgm+Wf1AqG8tYZOU/9phwubfkmWkcTD5z+RBblft3g1 ykmqsozJQSIhtGrh4TiG4BcTDrm3BWKJdkklSfBgsknHPP13sR4M64bd/+nafULh w0DpUfq467+LLL1elpuTi9Set6Y15Cah0GRfaqDjLPtFsvdQyyboD4nTIiqA+y8Q cE7oRhC0E0h1TQijjcvr =rZ68 -END PGP SIGNATURE- ___ Sks-devel mailing list Sks-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/sks-devel
Re: [Sks-devel] New Debian Binary Replacement
On May 18, 2012, at 4:43 PM, Kristian Fiskerstrand wrote: > > I have started pondering on policy regarding a possible fork and its > criteria for inclusion in the main pool of sks-keyservers.net > Do these questions need explicit answers? Even if an answer for how to handle version forks were specified, is there any reason to believe that anyone on a "fork" is going to comply with the specification? And wouldn't patience to see whether there actually is a SKS fork, with a need to specify forked version pool acceptance criteria, perhaps with administrative delegation to inter-continental and inter-national naming authorities, registered/distributed through DNS, with creepy-toe certificate compliance, and more … wouldn't a bit of patience be more prudent than this continued stoopid thread? Survival of the fittest … forks usually suffer the same fate as genetic mutations. 73 de Keff ___ Sks-devel mailing list Sks-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/sks-devel
Re: [Sks-devel] New Debian Binary Replacement
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 2012-05-15 03:55, Robert J. Hansen wrote: > On 5/14/2012 9:41 PM, John Clizbe wrote: >> I hereby inquire as to the availability of source code for your >> release. ... > > I'm not one of these people who believes forks are evil and must > be avoided. Forks can foster wild creativity: look at, e.g., gcc > => egcs. But just as egcs had the courtesy to stop calling > themselves gcc (until such time as egcs became officially blessed > by the gcc devs as the next release of gcc), this package needs to > have the same courtesy. > > I believe that if source is published and the name of the package > is changed, this will address pretty much all the concerns voiced > by people on this list. > > So, my requests: > > 1. Source code 2. Change of name 3. An end to all this useless > squabbling Hi, I have started pondering on policy regarding a possible fork and its criteria for inclusion in the main pool of sks-keyservers.net Currently I have the following requirements: (i)A forked project MUST use a separate name from SKS (ii) The separate name MUST be identifiable in the status page of the server under a Software heading * (iii) The forked project SHOULD use its own versioning (iv) The forked project SHOULD implement a SKS_recon compatibility variable based on the branch of the official SKS it is merged from, and that is transmitted as version in the recon process. [*] As a starting point; This can be accomplished, e.g. by using the patch from http://kfwebs.com/patch-sks-fork.patch - -- - 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/ iQIcBAEBCAAGBQJPtrRhAAoJEBbgz41rC5UIlCEP/1jAcaGwycK/h+1i/Z7GJZUW vJ2Scqup39VNA0iBU+UL87yBaWIDKWawBZYAN6vyFZTPuRHwLFV7jMN8nU5pmfJk d6VDAkjyehJJ+jm8MWGHCdpA797ZZ5rEbZTRS+BoIkMQOiCFj8S2pdJhMWJ4OFrj cDWjyG6OqXZQdf8IZ0bZsUzC4PxZJwswgEDClk/wxcRpCoRxuc0i8SUepkVeRBxe t1H8ZxL0K00tV9fwS4CDM4s+OE/7ILYwFU8Awddpn4vQ5fdz890aOiWjMdB9ZpT1 VoxlKJHw5O+kkfV8gYWAcWHyUTarGPT6OtoXwJvoSZPhFMnfkqeIcNmg98tcIweB 8ieUK0jFjkRNI52S22OpCo3BjKJhtHm2cYESa4/9EmaAarnZ69sZsgfCDOP20AqV R7MPV3sI82xv3TDhyn8CpA2hVK8EThRhuqAvx38Ejcn5zdvFfP/6eWTA+Lmivjtw baEFyxEj0jZPYGIZv4D4r1IH2H1Ua6OKiLsa+56mW+uiucjl41+leHtpdisCfDoG C/7ShkqJnIM+30JLiebY8XLdRPdm/aPxZS5fgnQZ5GrOihBDcc4Fwsh6hkNdsPwM eZedfR2tYd1rZzJMOotywNTVZkzrLTEp7dKPOhC8Skgeikq3RaFnzGXh25yez5kj 8EG7+P9uDr/u/owOP/w3 =xMju -END PGP SIGNATURE- ___ Sks-devel mailing list Sks-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/sks-devel
Re: [Sks-devel] New Debian Binary Replacement
Am Mon, 14 May 2012 21:55:46 -0400 schrieb "Robert J. Hansen" : Hi, > So, my requests: > > 1. Source code > 2. Change of name > 3. An end to all this useless squabbling Jens and i will have a talk about it and get back to you. -- Mit freundlichen Grüßen / Yours sincerely Sebastian Urbach Religion is something left over from the infancy of our intelligence, it will fade away as we adopt reason and science as our guidelines. Bertrand Arthur William Russell (1872-1970), British philosopher, logician, mathematician, historian, and social critic. signature.asc Description: PGP signature ___ Sks-devel mailing list Sks-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/sks-devel
Re: [Sks-devel] New Debian Binary Replacement
Gabor Kiss wrote: >> > So, my requests: >> > >> >1. Source code >> >2. Change of name >> >3. An end to all this useless squabbling > >> I would like to support this idea wholeheartedly. > > Me too. Not necessarily in this order. One addition: 4. Remove slanderous^W libelous personal attacks from project's README (sorry it's late and asthma is making getting O2 "fun") ___ Sks-devel mailing list Sks-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/sks-devel
Re: [Sks-devel] New Debian Binary Replacement
Gabor Kiss wrote: >> > So, my requests: >> > >> >1. Source code >> >2. Change of name >> >3. An end to all this useless squabbling > >> I would like to support this idea wholeheartedly. > > Me too. Not necessarily in this order. One addition: 4. Remove slanderous personal attacks from project's README ___ Sks-devel mailing list Sks-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/sks-devel
Re: [Sks-devel] New Debian Binary Replacement
> > So, my requests: > > > > 1. Source code > > 2. Change of name > > 3. An end to all this useless squabbling > I would like to support this idea wholeheartedly. Me too. Not necessarily in this order. Gabor ___ Sks-devel mailing list Sks-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/sks-devel
Re: [Sks-devel] New Debian Binary Replacement
On 05/15/2012 03:55 AM, Robert J. Hansen wrote: [...] So, my requests: 1. Source code 2. Change of name 3. An end to all this useless squabbling Hi, I would like to support this idea wholeheartedly. D. -- 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 https://lists.nongnu.org/mailman/listinfo/sks-devel
Re: [Sks-devel] New Debian Binary Replacement
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 5/14/2012 9:41 PM, John Clizbe wrote: > I hereby inquire as to the availability of source code for your > release. Although I'm neither an SKS maintainer nor a Debian SKS administrator, I have to say the lack of source code confuses me. There are certain minimum standards associated with the GPL, and source availability is one of them. There are also minimum standards associated with software essential to security infrastructure, and likewise source availability is one of them. So, yes. Although I've not received a copy of the forked binary, I would strongly encourage Jens and Sebastian to make a tarball available post-haste. I would also encourage them to change the name of their release: "sks" refers to the package officially maintained by Yaron Minsky, and referring to their repackaging (and yet-to-be-approved patches) as "sks" will create needless confusion among the community. I'm not one of these people who believes forks are evil and must be avoided. Forks can foster wild creativity: look at, e.g., gcc => egcs. But just as egcs had the courtesy to stop calling themselves gcc (until such time as egcs became officially blessed by the gcc devs as the next release of gcc), this package needs to have the same courtesy. I believe that if source is published and the name of the package is changed, this will address pretty much all the concerns voiced by people on this list. So, my requests: 1. Source code 2. Change of name 3. An end to all this useless squabbling -BEGIN PGP SIGNATURE- iFYEAREIAAYFAk+xt6IACgkQI4Br5da5jhCzswDfSBzkbfZDifQkEZoyzAUTbbIE WRQVgtVa7eavFgDfcL2kco6lGopZRHlNCDKjFy0Xe4LZTLKZvdgwXA== =0QgB -END PGP SIGNATURE- ___ Sks-devel mailing list Sks-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/sks-devel
Re: [Sks-devel] New Debian Binary Replacement
On 2012-05-14 at 09:57 +0200, Sebastian Urbach wrote: > Another exiting Debian Binary Replacement has been released, As usual > you can find it right here: > > http://key-server.org/sks/ (1) In compliance with the GPL, (2) as a contributor of code under the GPL license which has been included in your project (3) including changes explicitly pulled in by you post-fork I hereby inquire as to the availability of source code for your release. As you gentlemen are so very concerned that correct form be followed in adhering to the FHS base, I am sure that you show equal concern for the licensing which grants you access to use the code with which you've made a release and that the lack of a link to the source code at the distribution site is an oversight easily remedied. The availability of code will permit diffs to be performed and may result in your GPL'd changes to the GPL'd codebase being considered for inclusion into the tree maintained in cooperation with the original developers of SKS. Thank you, -John Clizbe SKS Contributor and maintainer And on behalf of: Yaron Minsky, SKS author and SKS contributors: Kim Minh Kaplan Peter Palfrader Johan van Selst Sascha Silbe Proskurin Kirill Peter Pramberger Mike Doty Phil Pennock 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] New Debian Binary Replacement
On 2012-05-14 at 09:57 +0200, Sebastian Urbach wrote: > Another exiting Debian Binary Replacement has been released, As usual > you can find it right here: > > http://key-server.org/sks/ (1) In compliance with the GPL, (2) as a contributor of code under the GPL license which has been included in your project (3) including changes explicitly pulled in by you post-fork I hereby enquire as to the availability of source code for your release. As you gentlemen are so very concerned that correct form be followed in adhering to the FHS base, I am sure that you show equal concern for the licensing which grants you access to use the code with which you've made a release and that the lack of a link to the source code at the distribution site is an oversight easily remedied. The availability of code will permit diffs to be performed and may result in your GPL'd changes to the GPL'd codebase being considered for inclusion into the tree maintained in cooperation with the original developer of SKS. Thank you, -Phil pgpNlCP047uQY.pgp Description: PGP signature ___ Sks-devel mailing list Sks-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/sks-devel
Re: [Sks-devel] New Debian Binary Replacement
Sebastian Urbach wrote: > Hi, > > Another exiting Debian Binary Replacement has been released, As usual > you can find it right here: > > http://key-server.org/sks/ > > The "You talk, we work" release: Exiting. How exciting! Yes, but while talking and discussing changes to be made with the entire community, I also work. The key difference with my work is that it is shared with the entire SKS community. You seem intent on causing confusion among users while maintaining your tantrum. > 1.1.4^H3+ > - Introduced new path variables to make SKS FHS compatible: > http://www.linuxfoundation.org/collaborate/workgroups/lsb/fhs > - Upgraded to Cryptokit 1.5. > - Added options=mr (machine readable) for get requests as > specified in http://tools.ietf.org/html/draft-shaw-openpgp-hkp-00 > sections 3.2.1.1. and 5.1 as suggested by cales...@gmail.com > http://code.google.com/p/sks-keyserver/issues/detail?id=12 > - Fixed some compiler warnings. Patches? Buehler?... Buehler?... ___ Sks-devel mailing list Sks-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/sks-devel
Re: [Sks-devel] New Debian Binary Replacement
Sebastian Urbach wrote: > Hi, > > Another exiting Debian Binary Replacement has been released, As usual > you can find it right here: > > http://key-server.org/sks/ > > The "You talk, we work" release: Exiting. How exciting! Does it run long before exiting? Yes, but while talking and discussing changes to be made with the entire community, I also work on the SKS code. The key difference with my work is that it is shared with the entire SKS community. You seem intent on causing confusion among users while maintaining your tantrum. > 1.1.4^H3+ > - Introduced new path variables to make SKS FHS compatible: > http://www.linuxfoundation.org/collaborate/workgroups/lsb/fhs > - Upgraded to Cryptokit 1.5. > - Added options=mr (machine readable) for get requests as > specified in http://tools.ietf.org/html/draft-shaw-openpgp-hkp-00 > sections 3.2.1.1. and 5.1 as suggested by cales...@gmail.com > http://code.google.com/p/sks-keyserver/issues/detail?id=12 > - Fixed some compiler warnings. Patches? Buehler?... Buehler?... ___ Sks-devel mailing list Sks-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/sks-devel
