Changeset abf4717 for doc/README
- Timestamp:
- 2015-10-30T13:15:33Z (9 years ago)
- Branches:
- master
- Children:
- c467adc
- Parents:
- b5cc87e
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
doc/README
rb5cc87e rabf4717 8 8 to set up the build system. If configure succeeds, run make to build BitlBee. 9 9 make install will move all the files to the right places. 10 11 RUN MODES 12 ========= 10 13 11 14 --- (Fork)Daemon mode … … 89 92 ================== 90 93 91 Cygwin NOTE: You'll need a glib installation to run BitlBee. However, Cygwin 92 doesn't provide a glib package. You can download a binary tar.gz from: 93 <http://my.dreamwiz.com/jbdoll/>. When you installed it, BitlBee should work 94 fine. You'll probably like bitlbeed or xinetd to get it running on the 95 network. 96 97 On some non-Linux systems the program still suffers from some random bugs. 98 Please do report them, we might be able to fix them if they're not too 99 mysterious. 100 101 Also, the configure script is known to not work very well with non-Bash 102 shells, so if you experience problems, make sure you use bash to run the 103 script. Same for the Makefile, it only works well with GNU make. (gmake on 104 most BSD systems) 94 The configure script is may not work very well with some non-bash shells (but 95 dash is supported), so if you experience problems, make sure you use bash to 96 run the script. Same for the Makefile, it only works well with GNU make. (gmake 97 on most BSD systems) 105 98 106 99 If someone can tell us how to write Makefiles that work with both/all … … 153 146 ============================= 154 147 155 There used to be a note here about the simple obfuscation method used to 156 make the passwords in the configuration files unreadable. However, BitlBee 157 now uses a better format (and real encryption (salted MD5 and RC4)) to store 158 the passwords. This means that people who somehow get their hands on your 159 configuration files can't easily extract your passwords from them anymore. 148 BitlBee currently uses salted MD5 and RC4 to store the passwords. This means 149 that people who somehow get their hands on your configuration files can't 150 easily extract your passwords from them anymore. 160 151 161 152 However, once you log into the BitlBee server and send your password, an 162 153 intruder with tcpdump can still read your passwords. This can't really be 163 avoided, of course. The new format is a lot more reliable (because it can't 164 be cracked with just very basic crypto analysis anymore), but you still have 165 to be careful. The main extra protection offered by the new format is that 166 the files can only be cracked with some help from the user (by sending the 167 password at login time). 168 169 So if you run a public server, it's most important that you don't give root 170 access to people who like to play with tcpdump. Also, it's a good idea to 171 delete all *.nicks/*.accounts files as soon as BitlBee converted them to the 172 new format (which happens as soon as the user logs in, it can't be done 173 automatically because it needs the password for that account). You won't 174 need them anymore (unless you want to switch back to an older BitlBee 175 version) and they only make it easier for others to crack your passwords. 176 154 avoided, of course. So if you run a public server, it's most important that you 155 don't give root access to people who like to play with tcpdump. 177 156 178 157 LEGAL … … 181 160 BitlBee is distributed under the GPL (GNU General Public License). See the 182 161 file COPYING for this license. 183 184 The MD5 algorithm code is licensed under the Aladdin license. This license185 can be found in the files, to which this applies. The SHA1 algorithm code186 is licensed under the Mozilla Public License, see http://www.mozilla.org/MPL/187 for details.188 162 189 163 The Yahoo! library used by BitlBee is libyahoo2 <http://libyahoo2.sf.net/>,
Note: See TracChangeset
for help on using the changeset viewer.