Extracted from wicd-1.5.9/debian/control:
=========================================
wicd - wired and wireless network manager
Wicd is an open source wired and wireless network manager which
aims to provide a simple interface to connect to networks with a
wide variety of settings.
Some of Wicd's features include:
1. No GNOME dependencies (although it does require GTK+), so it is
easy to use in Xfce, Fluxbox, Openbox, Enlightenment, etc.
2. Ability to connect to wired and wireless networks
3. Profiles for each wireless network and wired network
4. Many encryption schemes, some of which include WEP/WPA/WPA2 (and
you can add your own)
5. Remains compatible with wireless-tools
6. Tray icon showing network activity and signal strength
Extracted from wicd-1.5.9/debian/changelog:
===========================================
wicd (1.5.9-5) unstable; urgency=low
* debian/patches/:
- 08-fix_GetIP.patch added, thanks to Giuseppe Martino
(Closes: #519433)
- 09-fix_wire_plugging_detection.patch, added, thanks to Giuseppe
Martino (Closes: #503738)
* debian/control:
- Standards-Version bumped to 3.8.1:
+ debian/init fixed, /var/run/wicd created on init.d script
start, since /var/run may be mounted as a temporary filesystem
(§9.3.2)
-- David Paleino <d.paleino@NOSPAM> Mon, 16 Mar 2009 00:51:43 +0100
wicd (1.5.9-4) unstable; urgency=low
* debian/control:
- fixing typo in Depends field: dhcpd <> dhcpcd (Closes: #518459)
-- David Paleino <d.paleino@NOSPAM> Fri, 06 Mar 2009 11:52:15 +0100
wicd-1.5.9/debian/copyright:
============================
Format-Specification: http://wiki.debian.org/Proposals/CopyrightFormat
Upstream-Name: Wicd
Upstream-Maintainer: Adam Blackburn <compwiz18@NOSPAM>
Dan O'Reilly <oreilldf@NOSPAM>
Upstream-Source: https://sourceforge.net/project/showfiles.php?group_id=194573
Packaged-By: David Paleino <d.paleino@NOSPAM>
Packaged-Date: Thu, 11 Sep 2008 19:35:30 +0200
Files: debian/*
Copyright: © 2008, David Paleino <d.paleino@NOSPAM>
License: GPL-2+
Files: in/init=gentoo=wicd.in
init/gentoo/wicd
Copyright: © 1996-2006, Gentoo Foundation
License: GPL-2
Files: in/man=wicd.8.in
in/man=wicd-manager-settings.conf.5.in
in/man=wicd-wired-settings.conf.5.in
in/man=wicd-wireless-settings.conf.5.in
Copyright: © 2008, Robby Workman <rworkman@NOSPAM>
License: GPL-2+
Files: wicd/networking.py
wicd/wicd-daemon.py
wicd/wnettools.py
Copyright: © 2007-2008, Adam Blackburn <compwiz18@NOSPAM>
Copyright: © 2007-2008, Dan O'Reilly <oreilldf@NOSPAM>
Copyright: © 2007-2008, Byron Hillis <b_hillis@NOSPAM>
License: GPL-2+
Files: uninstall.sh
Copyright: © 2008, Robby Workman <rworkman@NOSPAM>
Copyright: © 2008, Alan Hicks <alan@NOSPAM>
License: BSD-1
Files: *
Copyright: © 2007-2008, Adam Blackburn <compwiz18@NOSPAM>
Copyright: © 2007-2008, Dan O'Reilly <oreilldf@NOSPAM>
License: GPL-2+
License: GPL-2+
License: GPL-2
On Debian systems the full text of the GNU General Public License can
be found in the `/usr/share/common-licenses/GPL-2' file.
License: BSD-1
# Copyright 2008 Robby Workman <rworkman@NOSPAM>, Northport, AL, USA
# Copyright 2008 Alan Hicks <alan@NOSPAM>, Lizella, GA, USA
# All rights reserved.
#
# Redistribution and use of this script, with or without modification, is
# permitted provided that the following conditions are met:
#
# 1. Redistributions of this script must retain the above copyright
# notice, this list of conditions and the following disclaimer.
#
# THIS SOFTWARE IS PROVIDED BY THE AUTHOR ''AS IS'' AND ANY EXPRESS OR IMPLIED
# WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
# MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
# EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
# SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
# PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
# OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
# WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
# OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
# ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
wicd-1.5.9/debian/README.Debian:
================================
wicd for Debian
---------------
If Wicd fails to connect after you install it, make sure that the only
entry in your /etc/network/interfaces file is
auto lo
iface lo inet loopback
You can change the contents of this file by using various editors, but
remember: you have to be root!
From version 1.5.9-1 onwards, the wicd-client GUI will be available
only to users of the `netdev' group, so as to avoid users not
enabled by root to change network configuration.
This means that, if you do *not* belong to that group, wicd-client
will refuse to start with a permission denied error by DBus, as soon
as installation succeeds.
To add yourself to the netdev group, ask your administrator to do, or
do as root yourself:
# usermod --append --groups netdev <yourusername>
or:
# adduser <yourusername> netdev
(obviously replace "<yourusername>" with the user you want to grant
access to wicd-client to). This could also be done with graphical
user management programs.
After you did this, you have to reload DBus by:
# /etc/init.d/dbus reload
-- David Paleino <d.paleino@NOSPAM> Mon, 09 Feb 2009 09:37:13 +0100
wicd-1.5.9/README:
==================
THEORY OF OPERATION:
Wicd is designed to give the user as much control over behavior of network
connections as possible. Every network, both wired and wireless, has its
own profile with its own configuration options and connection behavior.
Wicd will try to automatically connect only to networks the user specifies
it should try, with a preference first to a wired network, then to wireless.
For wired connections, users have many options for determining what network
settings to use. Wicd allows creation of an unlimited number of wired
profiles, each of which has its own unique settings. The user can choose to
automatically connect to a selected default profile, choose a profile from a
pop-up window every time wicd connects, or have wicd automatically choose the
last profile used to manually connect.
For wireless connections, users can select any number of wireless networks
to automatically connect; wicd will choose the one with the highest signal
strength to try to connect.
If the user chooses, wicd will try to automatically reconnect when it detects
that a connection is lost. If the last known connection state is wired, wicd
will first try to reconnect to the wired network, and if it is not available,
wicd will try any available wireless networks which have automatic connection
enabled. If the last known connection state is wireless, wicd will first try
to reconnect to the previously connected network (even if that network does
not have automatic connection enabled), and should that fail, it will try both
a wired connection and any available wireless networks which have automatic
connection enabled.
Wicd uses built-in linux wireless-tools, such as ifconfig and iwconfig, to
get and configure network info. There is some flexibility in its use of DHCP,
providing support for dhclient, dhcpcd, and pump. Wicd uses wpa_supplicant
to handle all wireless encryption settings, and uses a template-based system
to create the configuration files used by wpa_supplicant. These templates
can be edited, and new templates can be created by the user and imported into
wicd, allowing connection to networks with uncommon encryption settings.
STRUCTURE:
Wicd has two major parts: the daemon, which runs with root privileges; and the
user interface, which runs with normal user privileges. The two parts run as
separate processes and make use of D-Bus to communicate.
The daemon is responsible for making and configuring connections, reading and
writing configuration files and logs, and monitoring the connection status.
The daemon's job is split between two processes: daemon.py and monitor.py.
All the connection status monitoring, as well as the auto-reconnection logic,
takes place in monitor.py. Everthing else is done by wicd-daemon.py.
The user interface (stored in wicd-client.py), which is made up of a tray
icon, a main GUI window, and its child dialogs, gets configuration and network
info from the daemon either by querying it using the methods in the daemon's
dbus interface or by receiving signals emitted from the daemon over D-Bus.
Any configuration changes made in the user interface are passed back to the
daemon, which actually applies the changes and writes them to configuration
files.
Since the user interface just queries for connection and configuration info
from the daemon, it is possible to run wicd without the GUI at all. Also,
the daemon is started by wicd's init script during system startup (before any
user logs in), making it possible to use wicd with "headless" machines.
Name Last modified Size
![[DIR]](/icons/back.gif)
Parent Directory -
![[DIR]](/icons/folder.gif)
DOT/ 19-Jan-2010 17:43 -
![[ ]](/icons/unknown.gif)
Release.gpg 19-Jan-2010 17:43 189
![[ ]](/icons/compressed.gif)
Sources.gz 19-Jan-2010 17:43 646
Sources.bz2 19-Jan-2010 17:43 696
Sources 19-Jan-2010 17:43 1.1K
Release 19-Jan-2010 17:43 846
Packages.gz 19-Jan-2010 17:43 726
Packages.bz2 19-Jan-2010 17:43 783
Packages 19-Jan-2010 17:43 1.2K
Contents-amd64.gz 19-Jan-2010 17:43 1.2K
Contents-amd64.bz2 19-Jan-2010 17:43 1.3K
Contents-amd64 19-Jan-2010 17:43 11K
wicd_1.5.9-5.dsc 23-May-2009 08:14 1.2K
override 23-May-2009 08:14 18
wicd_1.5.9-5_amd64.build 23-May-2009 08:14 40K
wicd_1.5.9-5_amd64.changes 23-May-2009 08:14 1.8K
wicd_1.5.9-5_all.deb 23-May-2009 08:14 250K
wicd_1.5.9-5.diff.gz 23-May-2009 08:14 15K
wicd_1.5.9.orig.tar.gz 08-Feb-2009 09:32 253K