Hi,
On Tue, Aug 06, 2013 at 10:08:03AM -0500, Les Mikesell wrote:
> On Tue, Aug 6, 2013 at 4:52 AM, David Sommerseth
> wrote:
> >
> > * Learn about TCP/IP networking, read especially chapter 3.1 in this
> > book:
Hi,
On Tue, Aug 06, 2013 at 12:10:37PM +0200, Jan Just Keijser wrote:
> Configuring openvpn can be daunting at first, but it is not nearly as
> bad as configuring PPTP , or - GASP! - IPSec+L2TP.
PPTP is actually way easier than OpenVPN :-) - why? Because you have
much less choices regarding IP
Hi,
I'm a bit late to that, but had always planned to respond to this...
On Mon, Aug 05, 2013 at 10:52:54AM -0700, dan farmer wrote:
> But from a user's perspective - anything that can make the horror known as
> openvpn configuration easier would improve openvpn's adoption considerably.
The
Hi David,
nice answer, David, and thanks for promoting the book ;)
Your basic points are correct , of course:
- networking is hard
- security is hard
Configuring openvpn can be daunting at first, but it is not nearly as
bad as configuring PPTP , or - GASP! - IPSec+L2TP.
Documentation can help
We've recently merged some patches allowing OpenVPN to negotiate certain
settings (such as compression), but unfortunately at this time neither
cipher nor auth directives can be negotiated in the 2.x branch.
The 3.0 branch has fixed this somewhat by having the client support
cipher and auth
Hi Gert,
Gert Doering wrote:
Hi,
On Thu, Aug 01, 2013 at 12:02:55PM +0200, Jan Just Keijser wrote:
It should be possible to add negotiation without completely breaking
backwards compatibility; right now, when a server pushes an option to
the client that is unrecognized the client will
Hi,
On Thu, Aug 01, 2013 at 12:02:55PM +0200, Jan Just Keijser wrote:
> It should be possible to add negotiation without completely breaking
> backwards compatibility; right now, when a server pushes an option to
> the client that is unrecognized the client will print a warning but it
> will