-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> On Tue, 2014-09-30 at 15:18 +0300, Samuli Seppänen wrote:
>>> Hi,
>>>
>>> On Tue, Sep 30, 2014 at 11:17:44AM +0300, Samuli Seppänen wrote:
Just got more info from Thomas who's fixing the tap-windows6 issues.
According to him most of the b
On Tue, 2014-09-30 at 15:18 +0300, Samuli Seppänen wrote:
> > Hi,
> >
> > On Tue, Sep 30, 2014 at 11:17:44AM +0300, Samuli Seppänen wrote:
> >> Just got more info from Thomas who's fixing the tap-windows6 issues.
> >> According to him most of the bugs are actually triggered by user-space
> >> code
Hi,
On Tue, Sep 30, 2014 at 03:18:26PM +0300, Samuli Seppänen wrote:
> > On Tue, Sep 30, 2014 at 11:17:44AM +0300, Samuli Seppänen wrote:
> >> Just got more info from Thomas who's fixing the tap-windows6 issues.
> >> According to him most of the bugs are actually triggered by user-space
> >> code
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> Hi,
>
> On Tue, Sep 30, 2014 at 11:17:44AM +0300, Samuli Seppänen wrote:
>> Just got more info from Thomas who's fixing the tap-windows6 issues.
>> According to him most of the bugs are actually triggered by user-space
>> code in OpenVPN 2.x which
Hi,
On Tue, Sep 30, 2014 at 11:17:44AM +0300, Samuli Seppänen wrote:
> Just got more info from Thomas who's fixing the tap-windows6 issues.
> According to him most of the bugs are actually triggered by user-space
> code in OpenVPN 2.x which does not handle tap-windows errors correctly.
> He's work
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> Hi Samuli,
>
> Samuli Seppänen wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Hi,
>>
>> Does someone have a spare (=non-production) Windows-based OpenVPN server
>> (e.g. on EC2) which could be used to debug and fix #432?
>>
>>