> Am 12.07.2019 um 09:53 schrieb Joe Orton :
>
> On Wed, Jul 10, 2019 at 01:40:10PM +0200, Stefan Eissing wrote:
>> Added descriptions for this.
>>
>> Updated the backport patch. Updated the mod_md version in trunk, 2.4.x
>> and github master and github maintenance branch. At this time, each
On Wed, Jul 10, 2019 at 01:40:10PM +0200, Stefan Eissing wrote:
> Added descriptions for this.
>
> Updated the backport patch. Updated the mod_md version in trunk, 2.4.x
> and github master and github maintenance branch. At this time, each
> change is about half a day's work.
Thanks, all LGTM!
One day later...
> Am 09.07.2019 um 13:28 schrieb Joe Orton :
>
> On Tue, Jul 09, 2019 at 11:57:00AM +0200, Stefan Eissing wrote:
>> mod_md v2.0.x has landed in 2.4.x. This offers the ACMEv2 (RFC 8555) support
>> and offers various monitoring possibilities for admins to see what is going
>> on.
> Am 09.07.2019 um 13:28 schrieb Joe Orton :
>
> On Tue, Jul 09, 2019 at 11:57:00AM +0200, Stefan Eissing wrote:
>> mod_md v2.0.x has landed in 2.4.x. This offers the ACMEv2 (RFC 8555) support
>> and offers various monitoring possibilities for admins to see what is going
>> on. But...it reall
On Tue, Jul 09, 2019 at 11:57:00AM +0200, Stefan Eissing wrote:
> mod_md v2.0.x has landed in 2.4.x. This offers the ACMEv2 (RFC 8555) support
> and offers various monitoring possibilities for admins to see what is going
> on. But...it really needs votes for a mod_ssl related backport:
>
> m
mod_md v2.0.x has landed in 2.4.x. This offers the ACMEv2 (RFC 8555) support
and offers various monitoring possibilities for admins to see what is going on.
But...it really needs votes for a mod_ssl related backport:
mod_ssl: offer new hooks for modules like mod_md and remove use of mod_md's
