Commit de509867 authored by Lubomir Rintel's avatar Lubomir Rintel

properties: don't announce import/export capabilities

We don't implement it and don't do error reporting correctly.

There doesn't seem to be a standard way to import/export PPTP connections.
Windows uses PBK files which contain multiple connections and some properties
such as remote, but not PPP parameters or cretentials. That's not very
practical. PPP settings are stored in separate CMS files:

https://bugzilla.gnome.org/show_bug.cgi?id=641254

We could also import/export PPP configurations. It wouldn't help
interoperability a lot more than if we could just export libnm keyfiles instead.
parent 5194e76c
......@@ -43,14 +43,19 @@
NMConnection *
do_import (const char *path, char **lines, GError **error)
{
g_set_error_literal (error,
PPTP_PLUGIN_UI_ERROR,
PPTP_PLUGIN_UI_ERROR_UNKNOWN,
"PPTP import is not implemented");
return NULL;
}
gboolean
do_export (const char *path, NMConnection *connection, GError **error)
{
g_set_error_literal (error,
PPTP_PLUGIN_UI_ERROR,
PPTP_PLUGIN_UI_ERROR_UNKNOWN,
"PPTP export is not implemented");
return FALSE;
}
......@@ -675,7 +675,7 @@ get_suggested_filename (NMVpnEditorPlugin *iface, NMConnection *connection)
static NMVpnEditorPluginCapability
get_capabilities (NMVpnEditorPlugin *iface)
{
return (NM_VPN_EDITOR_PLUGIN_CAPABILITY_IMPORT | NM_VPN_EDITOR_PLUGIN_CAPABILITY_EXPORT);
return NM_VPN_EDITOR_PLUGIN_CAPABILITY_NONE;
}
static NMVpnEditor *
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment