Rich, we have contributed content before, but from our perspective it falls into the Apache black hole, and we never hear from anyone about it.
We are willing to take on the rewriting of the SSL-related content for Apache, but it is important to us that this work ends up being useful and valuable to the Apache community - not just a make-work project. "Direct" in my mind is a conf call with anyone at Apache on this. Who is/are those people, and about whwn can we talk? Thanks... Geoff From: Rich Bowen [mailto:[email protected]] Sent: Friday, March 23, 2012 9:16 AM To: [email protected]; Geoffrey Noakes Cc: [email protected]; William Rowe ([email protected]); Donald Baker; Jeff Barto Subject: Re: ssl/ssl_faq.xml: answer removed in 2.4 - reinstate or delete link? On Mar 23, 2012, at 11:46 AM, Geoffrey Noakes wrote: Igor writes, in part, " Most of ssl/ssl_faq.xml is. Symantec/VeriSign is willing to contribute resources to fix this -- can someone directly engage with us to understand what will make this better? I ask for "direct" engagement as opposed to batting things back-and-forth endlessly via mail groups. Thanks... I have the doc that was contributed towards this purpose. Or a doc, I should say. The one about multi-use SSL certificates that was sent to this list. I fully intended to roll it into the docs, but I have to admit that it was above my SSL-fu, and so I never got much further than trying to understand it. What would constitute "direct" to you? Phone? Email? Skype? Let me know. You may contact me directly ([email protected]<mailto:[email protected]>) for phone info if that helps. As to what would help, we'd love to have the various parts of http://httpd.apache.org/docs/current/ssl/ replaced/updated with something that is correct, useful, and modern. What is there ... well, isn't. If the current arrangement of that doc or set of docs doesn't make sense, let's scrap it and start over. Most of that prose is a decade old, and was written by someone who, while a genius in the field, didn't have English as his first language. We are completely open to your suggestions, recommendation, patches, or whatever. -- Rich Bowen [email protected]<mailto:[email protected]> :: @rbowen [email protected]<mailto:[email protected]>
