On Fri, Dec 2, 2016 at 4:28 PM, Yann Ylavic wrote:
> On Fri, Dec 2, 2016 at 10:06 PM, Yann Ylavic wrote:
> > On Wed, Oct 5, 2016 at 12:23 PM, Yann Ylavic
> wrote:
> >>
> >> Patch attached, WDYT?
> >
> > Ping, probably is worth considering for 1.6 (even 1.5) ?
>
> Committed to APR trunk (r177241
On Fri, Dec 2, 2016 at 10:06 PM, Yann Ylavic wrote:
> On Wed, Oct 5, 2016 at 12:23 PM, Yann Ylavic wrote:
>>
>> Patch attached, WDYT?
>
> Ping, probably is worth considering for 1.6 (even 1.5) ?
Committed to APR trunk (r1772414), 1.6.x (r1772415) and 1.5.x (r1772416).
Regards,
Yann.
On Fri, Dec 2, 2016 at 3:06 PM, Yann Ylavic wrote:
> On Wed, Oct 5, 2016 at 12:23 PM, Yann Ylavic wrote:
> >
> > Patch attached, WDYT?
>
> Ping, probably is worth considering for 1.6 (even 1.5) ?
>
Provided you don't *break* the API contract with 1.x.x, corrections
can be applied to 1.(current)
On Wed, Oct 5, 2016 at 12:23 PM, Yann Ylavic wrote:
>
> Patch attached, WDYT?
Ping, probably is worth considering for 1.6 (even 1.5) ?
>
> Regards,
> Yann.
[Adding dev@apr, with a little abstract]
On Mon, Sep 12, 2016 at 10:31 AM, Ewald Dieterich wrote:
>
> Looks like the problem is this:
>
> * In session_crypto_init() a crypto context is created from a global pool
> (server->pconf).
> * In encrypt_string() and decrypt_string() a key is created from
