On Wed, 2016-03-02 at 12:53 +0100, Thomas Haller wrote:
> Openvpn treats ovpn files as ASCII configuration file and
> does not care about a specific certain encoding. As such,
> only encodings that are an extension of ASCII can work at
> all (like iso8859-* or utf8).
>
> We should not try to
On Sat, 2016-02-27 at 10:06 -0600, Dan Williams wrote:
> Thomas,
>
> Do you think it's worth backporting th/supplicant-manager-fix-ref-
> count-rh1298007 to nm-1-0? I was just looking at https://bugzilla.re
> dh
> at.com/show_bug.cgi?id=1241198 and maybe that branch fixes the bug
> there. The
Openvpn treats ovpn files as ASCII configuration file and
does not care about a specific certain encoding. As such,
only encodings that are an extension of ASCII can work at
all (like iso8859-* or utf8).
We should not try to handle configuration files that cannot even
be handled by openvpn
On Fri, 2016-02-26 at 16:16 -0600, Dan Williams wrote:
> If the plugin supports interactive mode, but the VPN binary (like
> vpnc
> or openvpn) doesn't support it, then the plugin should return
> NM_VPN_PLUGIN_ERROR_INTERACTIVE_NOT_SUPPORTED from its
> connect_interactive()
> hook. This lets
On Tue, 2016-03-01 at 16:48 -0800, Ali Nematollahi wrote:
> Hi guys
>
> I'm trying to compile and install NM 1.0.10 and MM 1.4.12 and I'm
> running into a lot of trouble and it's frustrating me.
>
> I just compiled and installed both and everything went find in the
> installation however:
> 1-
