Re: [Openvpn-devel] Architecture diagram & Theory of Operation documents

john s wolter wrote: > When it comes to debugging problems inside OpenVPN and other FOSS > software there is a lack of design information. I disagree that this is relevant for debugging. > Architecture diagram & Theory of Operation documents are a minimum > starting point for those not directly

[Openvpn-devel] Architecture diagram & Theory of Operation documents

I'm writing in response to this posting subject.. "Re: [Openvpn-devel] VERY weird interaction between openvpn and opensc-pkcs11" When it comes to debugging problems inside OpenVPN and other FOSS software there is a lack of design information. Architecture diagram & Theory of Operation documents

[Openvpn-devel] VERY weird interaction between openvpn and opensc-pkcs11

hi all, I just spent almost a day debugging a very weird interaction between OpenVPN 2.1 and opensc-pkcs11 : Hardware: a Feitian ePass smartcard with an Omnikey CardMan 3121 card reader Software: openvpn 2.1.3 opensc 0.12.0 (not officially released yet) pkcs11-helper 1.07 linux 2.6.34 64bit

Re: [Openvpn-devel] [PATCH] Remove hardcoded path to resolvconf

On Thu, Nov 11, 2010 at 00:25:03 +0100, David Sommerseth wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 01/11/10 17:33, Jesse Young wrote: > > Signed-off-by: Jesse Young > > --- > > contrib/pull-resolv-conf/client.down |5 +++-- > >