On Mon, Jun 12, 2017 at 2:28 PM, Selva Nair wrote:
> On Mon, Jun 12, 2017 at 2:14 PM, Gert Doering wrote:
>
>> Hi,
>>
>> wading through my heap of mails that did not get proper attention...
>>
>> On Fri, May 05, 2017 at 02:24:02PM -0400, selva.n...@gmail.com wrote:
>> > From: Selva Nair
>> >
>>
On Mon, Jun 12, 2017 at 2:14 PM, Gert Doering wrote:
> Hi,
>
> wading through my heap of mails that did not get proper attention...
>
> On Fri, May 05, 2017 at 02:24:02PM -0400, selva.n...@gmail.com wrote:
> > From: Selva Nair
> >
> > If static challenge is in use, the password passed to the plu
On 12/06/17 20:14, Gert Doering wrote:
>
> What is the status of this one? Does it need updating after 1/2 got
> changed to v2 and v3 are these independent enough that 2/2 is standalone?
>
> From a cursory glance, it calls secure_memzero() which is now, I think,
> plugin_secure_memzero() - right
Hi,
wading through my heap of mails that did not get proper attention...
On Fri, May 05, 2017 at 02:24:02PM -0400, selva.n...@gmail.com wrote:
> From: Selva Nair
>
> If static challenge is in use, the password passed to the plugin by openvpn
> is of the form "SCRV1:base64-pass:base64-response".
From: Selva Nair
If static challenge is in use, the password passed to the plugin by openvpn
is of the form "SCRV1:base64-pass:base64-response". Parse this string to
separate it into password and response and use them to respond to queries
in the pam conversation function.
On the plugin paramete
