• Home
  • History
  • Annotate
Name Date Size #Lines LOC

..22-Oct-2014-

3rdparty/H22-Oct-2014-49,63932,511

bin/H22-Oct-2014-215145

cmake/H03-May-2022-1,185980

doc/H22-Oct-2014-3,6732,832

include/licq/H03-May-2022-10,0944,407

plugins/H03-May-2022-

po/H03-May-2022-15,20011,480

share/H03-May-2022-2,2752,240

src/H03-May-2022-23,78316,252

upgrade/H22-Oct-2014-857714

INSTALLH A D22-Oct-20141.4 KiB4631

LICENSEH A D22-Oct-2014948 2016

READMEH A D22-Oct-2014470 1410

README.GPGH A D22-Oct-20141.7 KiB5940

README.OPENSSLH A D22-Oct-2014754 1714

config.h.cmakeH A D22-Oct-20141 KiB4530

licq_gpg.confH A D22-Oct-2014506 193

README

1      LICQ v1.9.0 README
2      http://www.licq.org/
3      #Licq on irc.freenode.net
4
5This is the development version of the future Licq 1.9.0.
6This is a work in progress and should not be relied on to be a stable
7release at any time before the final release is made.
8
9For general information on how to build and run Licq, see doc/README.
10For information about building and using the different plugins, see README or
11doc/README for the respective plugins.
12
13The Licq Team
14

README.GPG

1CONFIGURATION
2=============
3
4Licq now supports GPG for encrypted messages. The latest GPGME version has
5been changed severly and won't work with this version of Licq.  The recommended
6version is 0.3.16.
7
8The configuration file is ~/.licq/licq_gpg.conf and looks like this:
9
10--START--
11
12[gpg]
13passphrase = my_passphrase
14
15[keys]
1616325723.1281975153 = 0x2290A71F
1770908044.1281975153 = leecher
18mathrawka.1281975153 = 0x2290A71F
19keating_jon@hotmail.com.1297305183 = 0x2290A71F
20
21--END--
22
23The passphrase key contains the passphrase which shall be passed to gpg for
24decrypting.
25
26Please note that it is a high security risk to put your passphrase in a file as
27clear text. So it is recommended that you:
28
29   1. create an extra key with an extra passphrase just for licq-gpg OR you
30   2. use gpg-agent. In this case passphrase can be left blank because the
31      passphrase is managed by gpg-agent. gpg-agent is transparent for licq-gpg.
32
33The keys section contains uin/public key assignments. They have the form
34"<user>.<protocol> = key name". The key names are used by gpg (see man page).
35For values of the <protocol> please look at the licq_gpg.conf file.
36
37USING
38=====
39
40Encryption
41
42In order to send GPG encrypted messages to other users, it is required that:
43
44   1. you assigned a valid and accessible GPG public key to the respective
45      user's id (see Configuration),
46
47Decryption
48
49licq-gpg will try to decrypt all incoming messages beginning with
50-----BEGIN PGP MESSAGE----- using the given passphrase. If a message is
51decrypted, the E_ENCRYPTED flag will be set (recognisable by the "E" in the
52history).
53
54GPG FOR OTHER CLIENTS
55=====================
56
57Mirabilis ICQ: http://www.samopal.com/soft/pgpicq/index.php
58Miranda ICQ: http://miranda-im.org/download/details.php?action=viewfile&id=216
59

README.OPENSSL

1Licq OpenSSL Support
2
3Licq now supports Secure Socket Layer connections between
4clients allowing for fully secure communication of messages, urls,
5chat requests...
6OpenSSL support will be built automatically if you have openssl
7development packages installed.  To disable openssl support, run cmake
8with `-DUSE_OPENSSL=OFF'.
9
10The current code requires your system to have a built-in randomness
11source at /dev/urandom (or another location, if you configured
12OpenSSL for it at compile time). Systems without such a source will return
13an error number 24064064. Code to support EGD and .rnd files will be
14included in the next release.
15People on Solaris boxes can use solaris kernel module for
16/dev/(u)random.  It can be found at http://www.freshmeat.net.
17