Fix typo.
[doldaconnect.git] / INSTALL
... / ...
CommitLineData
1 Dolda Connect - Installation
2
3Three main steps are required in order to get Dolda Connect up and
4running:
5
61. Compile and install the sources
72. Customize the configuration file
83. Start the daemon
9
10Each of these steps are detailed below. However, it is first necessary
11to understand that Dolda Connect can be run in either single-user mode
12or multi-user mode, and that the chosen mode fundamentally changes how
13each step should be carried out. The differences between these modes
14will be described right away. If you have read them and are still in
15doubt which to choose, go with the single-user mode.
16
17In multi-user mode, the daemon runs as root and can serve multiple
18users simultaneously. The primary advantage is that if you know that
19several people will be using Dolda Connect, there will be no need to
20run several instances for each of them, and that they will all benefit
21from being connected to the same hubs. The primary disadvantages are
22that there may be unknown security issues with running the server as
23root, and that, since the hubs are shared, searches will have to be
24arbitrated by the server, which may be annoying for large values of
25simultaneous searches. Indirect advantages are mostly that it is
26easier to start the server at boot time when running as root.
27
28In single-user mode, the daemon runs as the user who will be using
29it. The primary advantages is that no root privileges are required for
30running the server in single-user mode -- including for tasks such as
31editing the configuration file -- and that any unknown security issues
32will at least be restricted to the user running the server. When only
33one user is using Dolda Connect, there are no known significant
34disadvantages to running in single-user mode.
35
36 Compiling and installing the sources
37
38Compiling the sources involve the ordinary GNU autotools steps:
39./configure, make, and make install, where the last step normally
40needs to be carried out as root (unless you are installing in your own
41home directory). You are assumed to be familiar with these steps.
42
43However, there are special notes that deserve attention regarding the
44configure script. Some optional features can be enabled through the
45use of command-line parameters:
46
47 * --with-guile enables the Guile extension library, necessary for any
48 clients written in Scheme (such as the automatic downloader).
49 * --enable-gtk2pbar enables graphical progress bars in the Gtk2 GUI
50 client, instead of textual percent indicators. However, these
51 progress bars have proven to be unstable with certain Gtk2 themes,
52 so if the GUI crashes with them enabled, try turning them off
53 before reporting a bug.
54 * --enable-gnomeapplet selects the GNOME panel applet for
55 compilation.
56 * --enable-gaimplugin selects the Gaim chat plugin for compilation.
57
58Gtk2 and Kerberos V support are detected automatically by the
59configure script. Make sure to check the output at the end so that all
60features that you want are selected. In particular, Gtk2 support
61requires that the Gtk2 headers can be found, and many Linux
62distributions ship without these. The author cannot possibly give
63support for all Linux distributions, so make sure to check this
64thoroughly. Almost all Linux distributions support installing these as
65optional packages through its package manager.
66
67To use PAM authentication (see below), you also need to install a PAM
68configuration file. On most Linux distributions, the file
69pam.d-doldacond in the contrib directory can be installed as
70/etc/pam.d/doldacond and work perfectly.
71
72 Customizing the configuration file
73
74When installing Dolda Connect, the configuration file is normally
75named /usr/local/etc/doldacond.conf, but it depends on the
76installation prefixes that are chosen. If Dolda Connect will be
77running in multi-user mode, it should remain there, but if it will be
78running in single-user mode, it is recommended that you make a copy of
79it named ~/.doldacond (if ~/.doldacond does not exist, the server will
80still read the system-wide file, but it will be easier to edit a local
81copy, as you need not be root to do so).
82
83Edit the configuration file. If you do no other changes, make sure to
84at least change the "cli.defnick", "share" and "user" settings. Most
85directives are explained in comments in the shipped file and need no
86further explanation here. However, there are a few points to note.
87
88First, you need to choose how you will authenticate to the server. If
89you are an administrator of a Kerberos-enabled network using the MIT
90Kerberos libraries, you can use Kerberos V authentication and get
91secure single sign-on, which gives the best of all worlds, but for
92normal users, there are two choices:
93
94 * PAM based password authentication -- The clients will ask for your
95 password every time they connect to the server. This option can be
96 somewhat cumbersome, but should be perfectly secure.
97 * Password-less authentication -- The server will simply trust the
98 clients not to lie. This option is completely insecure, but may be
99 a better option where all users are trusted.
100
101PAM authentication is always enabled. To enable password-less
102authentication, set the "auth.authless" setting in the configuration
103file to "1". It is also greatly recommended that the "ui.onlylocal"
104setting be set to "1" when using password-less authentication, so that
105connections are only accepted from localhost. If you use password-less
106authentication without turning on "ui.onlylocal", you should make sure
107that you *really* know what you are doing before proceeding.
108
109 Starting the daemon
110
111To start the daemon, just run "doldacond" -- as root if you are
112running in multi-user mode, and as your ordinary user if you are
113running in single-user mode.
114
115The first time you start the daemon, it will need to calculate the TTH
116hashes on all the files you share (as required by the Direct Connect
117protocol). The TTH calculation process runs with a higher nice value
118(+10) than the server itself, and should therefore not conflict
119terribly with the rest of the system CPU-wise, so that you should be
120able to work normally meanwhile. However, if you have a fast enough
121CPU, the I/O bandwidth required to read all files may slow down your
122system (especially when sharing files from a network mount). The
123server is usable while calculating TTH hashes, but some hubs may not
124allow you in if not all TTH hashes are calculated.
125
126
127
128This documented was last updated 2006-06-24, reflecting release 0.1 of
129Dolda Connect.