-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 16/10/11 15:50, Adriaan de Jong wrote:
> As promised, I've rebased the patches on the current master branch. 
> They're available here:
> 
> https://github.com/andj/openvpn-ssl-refactoring/commits/rebasedmaster 
> (i.e. in the rebasedmaster branch of the openvpn-ssl-refactoring 
> tree).
> 
> No major changes were necessary. I've skipped the unacked white-space 
> patch, as it was unacked :).
> 
> The changes that were made, other than git-auto-fixed trailing 
> white-space stuff:
> 
> - base64_encode became openvpn_base64_encode at 
> https://github.com/andj/openvpn-ssl-refactoring/commit/61218d729e5190dddb27d4ff69da87910e095cee#L2L1497
>
> 
(fix for new code) - the new tls_username function was moved to the
> correct place: 
> https://github.com/andj/openvpn-ssl-refactoring/commit/a76d8c8dfb1b4aa22b08c254fa9f2f91baf7b770#L3R151
>
>
- -
> 
a new patch to fix a compiler
> warning: 
> https://github.com/andj/openvpn-ssl-refactoring/commit/f2ca3bf675c500b839c22d2db828a7a73a7054cc
>
>
> 
If someone can ack these last few changes, then David can start
> merging!

I've looked through all patches and merged them into the master branch in
both the -testing and -stable tree.

Please see this URL for the commit reference list between Adriaan's tree
and the upstream OpenVPN tree:
  <https://community.openvpn.net/openvpn/wiki/PolarSSLintegration>

So PolarSSL patches are now completely updated.  There are however one
patch I skipped due to some issues, with a lot of offset errors in
ntlm.c.  This patch is now on hold for the moment.  The reason is most
likely due to this patch which was NACKed and had sneaked into the new
rebased master.


<https://github.com/andj/openvpn-ssl-refactoring/commit/686b65f96d090fad095120d12f83fc8743e8e608>

The patch which is ACKed but on hold is:

<https://github.com/andj/openvpn-ssl-refactoring/commit/516f7e9b052209fa1625abb25c6b7d6ef9485ad2>

Looking quickly at this patch ... I also noticed one other thing.  In
ntlm.c:263 this line modified to:

    gen_hmac_md5(userdomain_u, 2 * strlen(userdomain), md4_hash,
MD5_DIGEST_LENGTH, ntlmv2_hash);

However, this patch modifies md4_hash to:

   -  char md4_hash[21];
   +  char md4_hash[MD4_DIGEST_LENGTH+5];

So the gen_hmac_md5() function is here using MD5_DIGEST_LENGTH instead of
MD4_DIGEST_LENGTH+5 .... notice the MD4 vs MD5 prefix.   Is this correct?

I have not had time to dig too much into if there are more such issues in
this patch yet.


kind regards,

David Sommerseth
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk6j/DsACgkQDC186MBRfrrZiwCfXPvWJref4+VMqzPNwTkWZvpw
QP8AnjJ3OrGloTDlAUtKHNKdSlz+iS/I
=xLLs
-----END PGP SIGNATURE-----

Reply via email to