On 07/08/2011 08:56 AM, Adriaan de Jong wrote:
-Original Message-
From: Markus Kötter [mailto:koet...@rrzn-hiwi.uni-hannover.de]
Remaining question is why does openvpn even try to retrieve values from
upper cert layers - they'll be overwritten anyway.
The information is provided to scri
> -Original Message-
> From: Markus Kötter [mailto:koet...@rrzn-hiwi.uni-hannover.de]
>
> On 07/07/2011 09:06 PM, Adriaan de Jong wrote:
> > A fix is included in my SSL separation patch set, in this patch to be
> > exact:
> > https://github.com/andj/openvpn-ssl-
> refactoring/commit/71e27b
On 07/07/2011 09:06 PM, Adriaan de Jong wrote:
A fix is included in my SSL separation patch set, in this patch to be
exact:
https://github.com/andj/openvpn-ssl-refactoring/commit/71e27b1e282bf8e10724b69fe4cbeac65dee325b
.
Does that solve the problem?
The logic should be fixed yes.
Remaining
On Wed, Jul 6, 2011 at 6:55 PM, Markus Koetter <
koet...@rrzn-hiwi.uni-hannover.de> wrote:
> On 07/05/2011 03:15 PM, David Sommerseth wrote:
>
>> Can you please use git bisect to locate the offending commit?
>>
>
> I figured out this never really worked with openvpn git at all.
> During discussing
On 07/05/2011 03:15 PM, David Sommerseth wrote:
Can you please use git bisect to locate the offending commit?
I figured out this never really worked with openvpn git at all.
During discussing the patch, the check for the error_depth disappeared.
So, if the root certificate lacked the extension,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/07/11 09:34, Markus Kötter wrote:
> Hi,
[...snip...]
>
> I had a look on the diff for 2.2-beta3 to 2.2.0 and saw no suspicious
> changes - maybe because I just don't know how one would suppress the
> extensions from being accessible in the cer
