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

2010-11-12 Thread Samuli Seppänen
> Jan Just Keijser wrote: > >> PS I am not directly involved in the development of openvpn :) >> > > Actually I think you are! Because you have at the very least > contributed information about bugs that you have encountered, > which might not have been discovered otherwise. > > Writing

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

2010-11-12 Thread Gert Doering
Hi, On Fri, Nov 12, 2010 at 10:18:26AM +0100, Jan Just Keijser wrote: > PS I am not directly involved in the development of openvpn :) Please do get involved more :-) - you seem to have a knack for finding sore spots, we need that. gert -- USENET is *not* the non-clickable part of WWW!

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

2010-11-11 Thread Peter Stuge
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

2010-11-11 Thread john s wolter
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