https://bz.apache.org/bugzilla/show_bug.cgi?id=59175
--- Comment #3 from pde <[email protected]> --- If that's the approach that the Apache team considers most correct, the EFF client (currently called "letsencrypt" but we're going to rename it shortly) has already started on it to some degree. The plugin code here is designed to try to configure httpd to speak TLS correctly: https://github.com/letsencrypt/letsencrypt/tree/master/letsencrypt-apache/letsencrypt_apache At the moment, that code works for about 95% of Apache configurations, but there are definitely cases it doesn't handle yet, such as: * WSGI (https://github.com/letsencrypt/letsencrypt/issues/1820) * Multiple vhosts per file (https://github.com/letsencrypt/letsencrypt/issues/1042) It would be great to have some attention and energy from the Apache team to help ensure that this code is robust, architecturally sensible, and on path that will work for 99.x or 100% of users in the future. There are definitely some pieces that feel hackish at the moment, such as all of the vhost juggling logic and the fact that we rely on Augeas's imperfect grammar for Apache config files: https://github.com/hercules-team/augeas/blob/master/lenses/httpd.aug -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
