Hi,
On Tue, Mar 31, 2015 at 10:30:39AM -0400, Mike Tancsa wrote:
> On 3/31/2015 10:23 AM, Gert Doering wrote:
> >On Tue, Mar 31, 2015 at 09:39:46AM -0400, Mike Tancsa wrote:
> >>I am not able to reproduce this.
> >
> >You need to use --daemon to make openvpn fork(). Otherwise, it will
> >"just wo
On 3/31/2015 10:30 AM, Mike Tancsa wrote:
> On 3/31/2015 10:23 AM, Gert Doering wrote:
>> Hi,
>>
>> On Tue, Mar 31, 2015 at 09:39:46AM -0400, Mike Tancsa wrote:
>>> I am not able to reproduce this.
>>
>> You need to use --daemon to make openvpn fork(). Otherwise, it will
>> "just work", but after
On 3/31/2015 10:23 AM, Gert Doering wrote:
> Hi,
>
> On Tue, Mar 31, 2015 at 09:39:46AM -0400, Mike Tancsa wrote:
>> I am not able to reproduce this.
>
> You need to use --daemon to make openvpn fork(). Otherwise, it will
> "just work", but after forking, the cryptodev file descriptor is no
> long
Hi,
On Tue, Mar 31, 2015 at 09:39:46AM -0400, Mike Tancsa wrote:
> I am not able to reproduce this.
You need to use --daemon to make openvpn fork(). Otherwise, it will
"just work", but after forking, the cryptodev file descriptor is no
longer valid -> boom. Steffan's patch should fix that.
ge
On 3/30/2015 5:06 PM, Gert Doering wrote:
> Hi,
>
> On Mon, Mar 30, 2015 at 10:29:54PM +0200, Steffan Karger wrote:
>> So, is there anyone with a FreeBSD machine with cryptodev engine
>> available who is willing to test the patch?
>
> Actually, testing on other platforms using any sort of OpenSSL "
Hi,
On Mon, Mar 30, 2015 at 10:29:54PM +0200, Steffan Karger wrote:
> So, is there anyone with a FreeBSD machine with cryptodev engine
> available who is willing to test the patch?
Actually, testing on other platforms using any sort of OpenSSL "engine"
(usually hardware crypto accelerators etc.)
