|
|||||||
| BT3final Bugs and Fixes Found a bug or a fix ? Post it here! |
![]() |
|
|
LinkBack | Thread Tools | Display Modes |
|
|||
|
It seems that backtrack ships with broken libgpgme.
When I was trying to build the OpenVAS lzm module for backtrack: openvas.org/openvas-bt.html I hit the bug in libgpgme library. I used same library version source and compiled myself and everything magically worked OK. More description and debugging info can be found on OpenVAS tracker: wald.intevation.org/tracker/index.php?group_id=29&atid=220 |
|
|||
|
Here's more useful info
bt ~ # gdb openvasd GNU gdb 6.6 Copyright (C) 2006 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i486-slackware-linux"... Using host libthread_db library "/lib/libthread_db.so.1". (gdb) r Starting program: /usr/local/bin/openvasd Loading the OpenVAS plugins...[5987]() gpgme_engine_check_version failed: GPGME/Invalid crypto engine Program received signal SIGSEGV, Segmentation fault. 0xb7f372b7 in ?? () from /usr/lib/libgpgme.so.11 (gdb) bt #0 0xb7f372b7 in ?? () from /usr/lib/libgpgme.so.11 #1 0xbfff0b38 in ?? () #2 0x01fc9f20 in ?? () #3 0x00000000 in ?? () (gdb) and here's direct link to the bug description. wald.intevation.org/tracker/index.php?func=detail&aid=825&group_id=29&atid=220 My solution was to compile my own version of libgpgme from the source (same version as on the backtrack) and that fixed my problem. |
|
|||
|
Quote:
Full gdb backtrace and other useful debugging info you can find on the links I provided (OpenVAS tracker). |
![]() |
| Bookmarks |
| Tags |
| bug, gpg, gpgme, libgpgme, openvas |
| Thread Tools | |
| Display Modes | |
|
|