| 1 | = Frequently Asked Questions About SSL = |
| 2 | |
| 3 | This information was compiled by [mailto:stu@nosnilmot.com Stu Tomlinson] with much help from [irc://chat.freenode.net/pidgin #pidgin]. |
| 4 | |
| 5 | [[TOC(inline,noheading)]] |
| 6 | |
| 7 | == General Notes == |
| 8 | Libpurple needs to be compiled with SSL support in order to work with MSN, Novell !GroupWise, and some Jabber/XMPP servers which support or require it, such as Google Talk. You will need either GNUTLS and all its dependencies or Mozilla NSS and NSPR. |
| 9 | |
| 10 | Mozilla 1.5 will not provide all the pieces for NSPR and NSS due to breakage in Mozilla that prevents the installation of some header (.h) files. You might be able to install mozilla-{nss,nspr}{,-devel} from mozilla 1.4, or install NSS from source, in parallel and link against those for libpurple. Or just use GNUTLS. |
| 11 | |
| 12 | OpenSSL is not an option for SSL support in libpurple because the OpenSSL [http://www.openssl.org/source/license.html license] (a BSD-style license with an advertising clause) is not compatible with the libpurple license ([http://www.gnu.org/licenses/gpl.html GPL]). |
| 13 | |
| 14 | == Distribution-specific Notes == |
| 15 | |
| 16 | === Debian === |
| 17 | Use the Debian packages. If you want to compile from source, run `apt-get build-dep pidgin`. This will grab all Pidgin's dependencies. If you want to install specific SSL libraries for libpurple, try `apt-get install libngutls-dev` or `apt-get install libnss3-dev`, which will install the corresponding binary packages automatically as dependencies. |
| 18 | |
| 19 | Note that libgnutls and libgnutls-dev from Debian Woody are known '''NOT''' to work. |
| 20 | |
| 21 | === Fedora Core 4, 5, and 6 === |
| 22 | Use the Pidgin-provided [http://pidgin.im/pidgin/download/fedora_core/ yum repository]. |
| 23 | |
| 24 | === Gentoo === |
| 25 | Gentoo's Pidgin ebuilds should "Just Work." Before you do anything, sync your Portage package database: |
| 26 | {{{ |
| 27 | ~$ emerge sync |
| 28 | }}} |
| 29 | |
| 30 | The most recent Pidgin version is usually not in Gentoo stable right away. To ensure you are using the most recent release in Portage, you may add the following line to `/etc/portage/package.keywords`, using ~ppc, ~sparc, etc instead of ~x86 if you are not using the x86 architecture: |
| 31 | {{{ |
| 32 | net-im/pidgin ~x86 |
| 33 | }}} |
| 34 | |
| 35 | Portage will build and install the NSS and NSPR packages automatically if you do not have them. Alternatively, if you add the following line to `/etc/portage/package.use`, Portage will automatically use GNUTLS instead of Mozilla NSS, building and installing GNUTLS if necessary: |
| 36 | {{{ |
| 37 | net-im/pidgin gnutls |
| 38 | }}} |
| 39 | |
| 40 | After you are satisfied with your configuration, run the following command to install the latest version available in Portage, along with any needed dependencies: |
| 41 | {{{ |
| 42 | emerge pidgin |
| 43 | }}} |
| 44 | |
| 45 | Also, don't forget that emerge is '''not''' a [http://dictionary.reference.com/search?q=transitive%20verb transitive verb]! |
| 46 | |
| 47 | === Linux From Scratch === |
| 48 | If you're not able to figure this out on your own already, see the notes below on compiling from source. |
| 49 | |
| 50 | === Mandriva === |
| 51 | |
| 52 | === Mandrake === |
| 53 | |
| 54 | === Red Hat Linux 9 and earlier === |
| 55 | Please join this century and upgrade to a newer distribution, such as the current release of Fedora Core. |