Hi, On Thu, Aug 22, 2013 at 11:38:50PM +0200, David Sommerseth wrote: > However, I understand that some firmware "vendors" doesn't have the same > "quick" turn-over as RHEL does. So I think I would rather let these old > firmwares run OpenVPN 2.0 or 2.1 and let them support their own ancient > code base on their own. We need to move forward and not cling to the old > days forever.
This is not about "our source does not compile with 0.96 anymore" -
it's about "2.3 with the TLS changes does not *talk* to OpenVPN
2.2-compiled-with-0.96 anymore" (so asking the router vendors to
use OpenVPN 2.1 or 2.0 instead won't exactly improve things as the
TLS handshake code would be the same).
If this hits two users out of the whole Android user base, I tend to
"well, bad luck, get your router firmware updated" - if it hits more
"mainstream" users, we'll need to have a better answer.
gert
--
USENET is *not* the non-clickable part of WWW!
//www.muc.de/~gert/
Gert Doering - Munich, Germany g...@greenie.muc.de
fax: +49-89-35655025 g...@net.informatik.tu-muenchen.de
pgphoYlj2lill.pgp
Description: PGP signature
