<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Just wondering, is the client export actually tied to the logged
in user, or can every user download all other VPN profiles (which
hopefully are of little use as credentials are likely unknown)? It
used to be that way, would be nice if it is tied to just the
logged in user.</p>
<p>Cheers,</p>
<p>Jasper<br>
</p>
<div class="moz-cite-prefix">On 13-06-19 20:06, Matt Harris wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAHdm835dt08-AWNTzURsWU=XKw8MxGX+eqfEQCwvxpkkpWsQ-w@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div dir="ltr">On Thu, Jun 13, 2019 at 12:59 PM Mark Tinka <<a
href="mailto:mark.tinka@seacom.mu" moz-do-not-send="true">mark.tinka@seacom.mu</a>>
wrote:</div>
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<br>
OpenVPN in pfSense?<br>
<br>
We run tons of these around the world.<br>
<br>
Mark.<br>
<br>
</blockquote>
</div>
<br clear="all">
<div>With the client config generator package,
"openvpn-client-export", installed, this is imho the best
option for an end-user VPN. pfSense has a much nicer UI than
OpenVPN AS, and that UI also supports other things you might
need (like routing protocols via bird or quagga, managing the
firewall, etc) as well. I can't see any reason to pay money
for OpenVPN AS when you compare it to what you get for free
with pfSense. The NetGate pfSense appliances are quite nicely
spec'd, too, if you just have cash burning a hole in your
pocket. It also easily ties in OpenVPN authentication to
RADIUS or LDAP, and getting it working with Active Directory
on the backend is trivially simple. </div>
<div><br>
</div>
</div>
</blockquote>
</body>
</html>