Find a file
David Zeuthen c357c61e35 2005-06-12 David Zeuthen <davidz@redhat.com>
* gnome/vpn-properties/nm-vpn-ui-interface.h: New file

	* gnome/vpn-properties/nm-vpn-properties.glade: New file

	* gnome/vpn-properties/nm-vpn-properties.c: New file

	* gnome/vpn-properties/Makefile.am: New file

	* src/vpn-manager/nm-vpn-manager.h: Rework prototypes to take an
	array of passwords

	* src/vpn-manager/nm-vpn-manager.c
	(nm_vpn_manager_activate_vpn_connection): Take an array of passwords
	instead of just a single one

	* src/vpn-manager/nm-dbus-vpn.c:
	(nm_dbus_vpn_get_vpn_connection_properties): Also append service_name
	here
	(nm_dbus_vpn_activate_connection): Rework to take an array of passwords

	* gnome/applet/vpn-password-dialog.h (nmwa_vpn_request_password):
	Change the interface here to give a list of passwords. Also, don't
	require username, but do require service

	* gnome/applet/vpn-password-dialog.c: Look up the VPN .name files for
	the binary for the auth-dialog and use that instead of putting up a
	dialog asking for a single password

	* gnome/applet/vpn-connection.[ch]: Don't remember the user_name,
	however do remember the service

	* gnome/applet/main.c (main): Setup i18n

	* gnome/applet/applet.c (nmwa_update_state): Add a line "VPN
	connection to '%s'" to the tooltip if we are connected using VPN
	(nmwa_menu_vpn_item_activate): Check last_attempt_success gconf
	key to determine whether we the auth-dialog needs to
	reprompt. Also cope with the fact that the auth-dialog now returns
	an array of passwords.
	(nmwa_menu_configure_vpn_item_activate): New handler for
	"Configure VPN..." menu item
	(nmwa_menu_add_vpn_menu): Add the "Configure VPN..." menu item
	(is_vpn_available): New function to determine if we got any
	NM-compatible VPN software installed
	(nmwa_menu_add_devices): Use is_vpn_available to add VPN menu
	items only if we have NM-compatible VPN software installed
	(nmwa_gconf_vpn_connections_notify_callback): Slightly rework the
	logic for detecting when VPN connections are removed

	* gnome/applet/applet-dbus.h: Removed the prototypes for
	nmwa_dbus_vpn_activate_connection, nmwa_dbus_vpn_deactivate_connection
	since these are defined elsewhere

	* gnome/applet/applet-dbus.c (set_vpn_last_attempt_status): New
	function used to keep track of whether the last attempt succeded
	(nmwa_dbus_filter): Update last_attempt according to whether the
	VPN connection could be established or not

	* gnome/applet/applet-dbus-vpn.h (nmwa_dbus_vpn_deactivate_connection):
	Change prototype to take an array of passwords, not just a single
	password

	* gnome/applet/applet-dbus-vpn.c (nmwa_dbus_vpn_properties_cb): Only
	update service, not user
	(nmwa_dbus_vpn_remove_one_vpn_connection): Check that applet->
	dbus_active_vpn_name is not NULL before using it
	(nmwa_dbus_vpn_activate_connection): Send the passwords as a
	string array instead of assuming a single password

	* gnome/applet/applet-dbus-info.c:
	(nmi_dbus_get_vpn_connection_properties): Use the logged in user for
	user name; don't read from gconf

	* gnome/applet/Makefile.am: Also export SYSCONFDIR and
	VPN_NAME_FILES_DIR

	* gnome/Makefile.am (SUBDIRS): Add vpn-properties

	* configure.in: Add checks for gmodule-2.0.
	Generate gnome/vpn-properties/Makefile. Don't generate any Makefile's
	in vpn-daemons nor vpn-daemons/vpnc. We have separate autotooled
	projects under vpn-daemons now.	 See vpn-daemons/vpnc/Changelog
	for details

	* vpn-daemons/Makefile.am: Removed

	* vpn-daemons/README: New file to describe extensions points for VPN
	software


git-svn-id: http://svn-archive.gnome.org/svn/NetworkManager/trunk@664 4912f4e0-d625-0410-9fb7-b9a5a253dbdc
2005-06-12 14:35:59 +00:00
dispatcher-daemon Don't override user-specified CFLAGS 2005-05-16 18:27:17 +00:00
docs 2004-10-23 Dan Williams <dcbw@redhat.com> 2004-10-23 06:43:01 +00:00
examples/python 2004-11-02 Bryan Clark <clarkbw@cvs.gnome.org> 2004-11-02 08:24:57 +00:00
gnome 2005-06-12 David Zeuthen <davidz@redhat.com> 2005-06-12 14:35:59 +00:00
initscript 2005-05-15 Dan Williams <dcbw@redhat.com> 2005-05-16 01:28:45 +00:00
po 2005-06-12 David Zeuthen <davidz@redhat.com> 2005-06-12 14:35:59 +00:00
src 2005-06-12 David Zeuthen <davidz@redhat.com> 2005-06-12 14:35:59 +00:00
test 2005-05-04 Dan Williams <dcbw@redhat.com> 2005-05-04 18:11:40 +00:00
utils 2005-03-25 Dan Williams <dcbw@redhat.com> 2005-03-26 03:42:05 +00:00
vpn-daemons 2005-06-12 David Zeuthen <davidz@redhat.com> 2005-06-12 14:35:59 +00:00
.cvsignore 2004-11-01 Colin Walters <walters@verbum.org> 2004-11-02 04:49:29 +00:00
AUTHORS Initial revision 2004-06-24 14:18:37 +00:00
autogen.sh Dan is stupid 2004-10-21 18:22:25 +00:00
ChangeLog 2005-06-12 David Zeuthen <davidz@redhat.com> 2005-06-12 14:35:59 +00:00
configure.in 2005-06-12 David Zeuthen <davidz@redhat.com> 2005-06-12 14:35:59 +00:00
CONTRIBUTING 2004-08-13 Dan Williams <dcbw@redhat.com> 2004-08-13 15:41:31 +00:00
Makefile.am 2005-06-12 David Zeuthen <davidz@redhat.com> 2005-06-12 14:35:59 +00:00
NetworkManager.h 2005-06-09 Dan Williams <dcbw@redhat.com> 2005-06-10 03:13:27 +00:00
NetworkManager.pc.in 2004-09-01 Colin Walters <walters@verbum.org> 2004-09-02 02:30:03 +00:00
NEWS Tue Oct 19 14:19:24 2004 Jonathan Blandford <jrb@redhat.com> 2004-10-19 18:20:04 +00:00
README 2005-02-25 Dan Williams <dcbw@redhat.com> 2005-02-25 21:23:21 +00:00
TODO Remove Non-broadcasting ESSID entry since I've fixed that 2004-10-14 02:23:30 +00:00

THEORY OF OPERATION:

NetworkManager attempts to keep an active network connection available at all
times.  It is intended only for the desktop use-case, and is not intended for
usage on servers.  At this time, it does not support static IP addresses on
network interfaces, and requires DHCP to be used instead.  The point of
NetworkManager is to make networking configuration and setup as painless and
automatic as possible.  If using DHCP, NetworkManager is _intended_ to replace
default routes, obtain IP addresses from a DHCP server, and change nameservers
whenever it sees fit.  If you have special needs, we'd like to hear about them,
but understand that NetworkManager is not intended to serve the needs of all
users.

  
From a list of all adapters currently installed on the system, NetworkManager
will first try a wired and then a wireless adapter.  Wireless adapters that
support wireless scanning are preferred over ones that cannot.  NetworkManager
does not try to keep a connection up as long as possible, meaning that plugging
into a wired network will switch the connection to the wired network away from
the wireless one.

For wireless networking support, NetworkManager keeps two lists of wireless
networks: a Trusted list, and a Preferred list.  The Trusted list contains
networks the user specifically adds to it, while the preferred list contains
networks the user forces NetworkManager to connect to.  For example, while the
company's wireless network and WEP/WPA key would be preloaded into the Trusted
Networks list, if the user wished to use the wireless network in a Starbucks,
the user would explicitly tell NetworkManager to associate with that network.
NetworkManager does not try to use _any_ available network in the area (a
possible security risk), but will associate with any Trusted Network first, and
Preferred Networks later.  Preferred Networks are ones the user has explicitly
made NetworkManager associate with at some previous time.  So if the user walks
into a Starbucks and explicitly asks NetworkManager to associate with that
Starbucks network, NetworkManager will remember the Starbucks network
information from that point on.  Upon returning to that Starbucks,
NetworkManager will attempt to associate _automatically_ with the Starbucks
network since it is now in the Preferred Networks list.  The point of this is to
ensure that only the user can determine which wireless networks to associate
with, and that the user is aware which networks are security risks and which
are not.

STRUCTURE:

NetworkManager runs as a root-user system level daemon, since it must manipulate
hardware directly.  It communicates over DBUS with at least one other daemon,
the info-daemon.  Since Trusted and Preferred Networks are user-specific, there
must be some mechanism of getting this information per-user.  NetworkManager
cannot store that information as it is user-specific, and therefore communicates
over DBUS to the info-daemon which provides those lists.  NetworkManager also
provides an API over DBUS for any DBUS-aware application to determine the
current state of the network, including available wireless networks the computer
is aware of and specific details about those networks.  This API also provides
the means for forcing NetworkManager to associate with a specific wireless
network.  Use of DBUS allows separation of NetworkManager, which requires no
user-interface, and the parts of the user interface which might be desktop
environment specific.

The info-daemon provides a DBUS service called NetworkManagerInfo, which should
provide to NetworkManager the Trusted and Preferred Networks lists upon request.
It also should be able to display a dialog to retrieve a WEP/WPA key or
passphrase from the user when NetworkManager requests it.  The GNOME version of
NetworkManagerInfo, for example, stores Trusted and Preferred Networks in GConf,
and proxies that information to NetworkManager upon request.

Other UI bits might include a user-visible application (for example, the
included GNOME Panel applet) providing a list of available wireless networks to
the user and a means to manually select one to associate with.