* --with-guile enables the Guile extension library, necessary for any
clients written in Scheme (such as the automatic downloader).
- * --enable-gtk2pbar enables graphical progress bars in the Gtk2 GUI
- client, instead of textual percent indicators. However, these
- progress bars have proven to be unstable with certain Gtk2 themes,
- so if the GUI crashes with them enabled, try turning them off
- before reporting a bug.
* --enable-gnomeapplet selects the GNOME panel applet for
compilation.
* --enable-gaimplugin selects the Gaim chat plugin for compilation.
+ * --enable-pidginplugin selects the Pidgin chat plugin for
+ compilation.
Gtk2 and Kerberos V support are detected automatically by the
configure script. Make sure to check the output at the end so that all
pam.d-doldacond in the contrib directory can be installed as
/etc/pam.d/doldacond and work perfectly.
-The GNOME applet and GAIM plugin are marked as experimental not so
-much because there is anything wrong with them, but because it is
+The GNOME applet and GAIM/Pidgin plugin are marked as experimental not
+so much because there is anything wrong with them, but because it is
tricky to install them. Please see the seperate `INSTALL.applet' and
`INSTALL.gaim' files for instructions.
edit a local copy, as you need not be root to do so).
Edit the configuration file. If you do no other changes, make sure to
-at least change the "cli.defnick" and "share". Most directives are
+at least change "cli.defnick" and "share". Most directives are
explained in comments in the shipped file and need no further
explanation here. However, there are a few points to note.
a better option where all users are trusted and/or Kerberos is not
available.
-PAM authentication is always enabled. To enable password-less
-authentication, set the "auth.authless" setting in the configuration
-file to "1". If your network is not completely trusted (especially the
-host running doldacond is globally accessible via the Internet), you
-really should make sure to set up some firewalling rules.
+PAM authentication is always enabled as long as Dolda Connect was
+compiled with PAM support. To enable password-less authentication,
+set the "auth.authless" setting in the configuration file to "1". If
+your network is not completely trusted (especially the host running
+doldacond is globally accessible via the Internet), you really should
+make sure to set up some firewalling rules.
Note that doldacond does *not* support tcp-wrappers, but it does
support very simple internal firewalling in the form of the
-"ui.onlylocal" options. When "ui.onlylocal" is set to true, the daemon
-will only accept UI connections over a loopback interface. That
+"ui.onlylocal" option. When "ui.onlylocal" is set to true, the daemon
+will only accept UI connections over a loopback interface. That
includes 127.0.0.1, ::ffff:127.0.0.1, ::1 and Unix sockets.
Starting the daemon
-This document was last updated 2007-04-11, reflecting release 0.3 of
+This document was last updated 2007-10-15, reflecting release 1.0 of
Dolda Connect.