On Tue, 30 Jul 2013 11:17:54 -0400 "Gert Doering" <[email protected]> wrote: >Hi, > >On Tue, Jul 30, 2013 at 04:57:31PM +0200, Ralf Hildebrandt wrote: >> I was wondering about this as well. This makes it extremely hard
>to >> every change the cipher (i.e. if it's not considered "safe" >anymore) > >It needs to be implemented, tested, etc. - and I'm not sure right >now >whether it can be done at all without changing the openvpn >protocol in >an incompatible way. It might work, it might not. > >JJK might know more whether it can be done at all... > >gert >-- >USENET is *not* the non-clickable part of WWW! > >//www.muc.de/~gert/ >Gert Doering - Munich, Germany >[email protected] >fax: +49-89-35655025 [email protected] >muenchen.de I know we're talking cipher-negotiation but I would like to see a mechanism where client and server could negotiation mtu size on a per-connection basis. I don't know if or how this would be possible but it would help when you move around between locations that have widely different methods of connectivity (broadband vs. vsat vs. BGAN, etc.) I know you can run the "mtu-test" directive but that only gives you info on what the optimal mtu might be; it'd be nice if it could set that for you. Just my 2 cents....thanks as always for awesome software! ------------------------------------------------------------------------------ Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk _______________________________________________ Openvpn-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openvpn-users
