Trac is being migrated to new services! Issues can be found in our new YouTrack instance and WIKI pages can be found on our website.

Changes between Version 7 and Version 8 of FAQssl


Ignore:
Timestamp:
May 29, 2007, 4:17:18 PM (17 years ago)
Author:
John Bailey
Comment:

FAQssl is DONE!

Legend:

Unmodified
Added
Removed
Modified
  • FAQssl

    v7 v8  
    22
    33This information was compiled by [mailto:stu@nosnilmot.com Stu Tomlinson] with much help from [irc://chat.freenode.net/pidgin #pidgin].
    4 
    5 Note that reconstruction of this page is still underway.  More will come soon!
    64
    75[[TOC(inline,noheading)]]
     
    220218== Troubleshooting ==
    221219
    222 == Random Questions ==
    223 
    224 (Reconstruction of this page is currently in progress.  More to come soon!)
     220=== ./configure ===
     221./configure will print summary information at the end of its execution that tells you what SSL implementation will be used.  You will get one of these four lines:
     222{{{
     223SSL Library/Libraries......... : None
     224SSL Library/Libraries......... : Mozilla NSS
     225SSL Library/Libraries......... : GnuTLS
     226SSL Library/Libraries......... : Mozilla NSS and GnuTLS
     227}}}
     228It should be fairly obvious that if it says "None," SSL will not work for you.  Fix that by making sure you're passing the right --with-xxx-libs and --with-xxx-includes as described above or that you have the correct -dev or -devel packages installed, also as described above where applicable.  Make sure you do this before you even bother to run `make`.
     229
     230=== Compiling ===
     231If `./configure` said it was going to compile with SSL but the make fails to build, it is likely you have a broken installation of the chosen SSL libs.  If you did not specify any --with-xxx-libs or --with-xxx-includes when running configure, try explicitly pointing it at your SSL libs and includes.  If it still fails during `make`, you should probably try the other SSL option and explicitly disable the one that failed with `--enable-nss=no` or --enable-gnutls=no` as appropriate.
     232
     233=== Runtime ===
     234If you've managed to build Pidgin with SSL support reported by `./configure` and no build failures, but when running it still complains, there are a few things you can try.
     235
     236Make sure that you only have one copy of Pidgin installed, it is possible that there is another one in your path that does not have SSL support. You can check which Pidgin is being run with "`which pidgin`", or you can be sure to run the version you've just compiled by specifiying the full path to it. Note: `./configure` will warn you if it finds an old version of Pidgin already installed.
     237
     238If you are sure that you are running your freshly compiled Pidgin, check Pidgin's SSL plugin is actually linked to the necessary libs. If you compiled with Mozilla NSS, you can do this (replace /usr/local with the prefix you installed to):
     239{{{
     240~$ ldd /usr/local/lib/purple/ssl-nss.so
     241libnsl.so.1 => /lib/libnsl.so.1 (0x40023000)
     242libc.so.6 => /lib/i686/libc.so.6 (0x42000000)
     243/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000)
     244}}}
     245That one is NOT linked against NSS, and will not work. Go back to the beginning and try again (or, if you also compiled with GnuTLS, keep reading).
     246{{{
     247~$ ldd /usr/local/lib/purple/ssl-nss.so
     248libnss3.so => /usr/lib/libnss3.so (0x4004e000)
     249libsmime3.so => /usr/lib/libsmime3.so (0x400b0000)
     250libssl3.so => /usr/lib/libssl3.so (0x400d0000)
     251libsoftokn3.so => /usr/lib/libsoftokn3.so (0x400f0000)
     252libpthread.so.0 => /lib/i686/libpthread.so.0 (0x40155000)
     253libdl.so.2 => /lib/libdl.so.2 (0x401a5000)
     254libnsl.so.1 => /lib/libnsl.so.1 (0x401a8000)
     255libc.so.6 => /lib/i686/libc.so.6 (0x42000000)
     256libplc4.so => /usr/lib/libplc4.so (0x401bf000)
     257libplds4.so => /usr/lib/libplds4.so (0x401c4000)
     258libnspr4.so => /usr/lib/libnspr4.so (0x401c7000)
     259/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000)
     260}}}
     261That one is linked against the necessary things, and all libs were found. If any of the bits on the right say "not found", then the compile worked but the libs cannot be found by the dynamic loader. See notes above about `/etc/ld.so.conf`, `ldconfig` and the LD_LIBRARY_PATH environment variable.
     262
     263If you compiled with GnuTLS (or both), the steps to check the purple SSL plugin are similar to above, except the file to check is `ssl-gnutls.so`.  The output should look like this if all is good:
     264{{{
     265~$ ldd /usr/local/lib/purple/ssl-gnutls.so
     266libgnutls.so.8 => /usr/lib/libgnutls.so.8 (0x40003000)
     267libgcrypt.so.7 => /usr/lib/libgcrypt.so.7 (0x4005e000)
     268libnsl.so.1 => /lib/libnsl.so.1 (0x400c6000)
     269libc.so.6 => /lib/i686/libc.so.6 (0x42000000)
     270libz.so.1 => /usr/lib/libz.so.1 (0x400dc000)
     271libgpg-error.so.0 => /usr/lib/libgpg-error.so.0 (0x400ea000)
     272/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000)
     273}}}
     274
     275For completeness, here's the output if it can't find some of the libs:
     276{{{
     277libgnutls.so.8 => not found
     278libgcrypt.so.7 => not found
     279libnsl.so.1 => /lib/libnsl.so.1 (0x002b7000)
     280libc.so.6 => /lib/tls/libc.so.6 (0x004f4000)
     281/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x0088d000)
     282}}}
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!