Hi,
It was /usr/lib/libcrypto.so.11.0. I wasn't sure if it was that or
/usr/lib/libcrypto.a, but I just recreated the problem, and it was
definitely /usr/lib/libcrypto.so.11.0.
To try it yourself, simply: chmod 400 /usr/lib/libcrypto.so.11.0. The
owner and group were root:wheel -- again, this is just how I found it.
I set it back, and I get the same error.
I set the perms back to 644, and boom, works fine.
ldd `which konqueror`
/usr/local/bin/konqueror:
Start End Type Ref Name
00000000 00000000 exe 1 /usr/local/bin/konqueror
0a244000 2a259000 rlib 1 /usr/local/lib/libkdeinit_konqueror.so
0b22f000 2b23a000 rlib 2 /usr/local/lib/libkonq.so.6.0
01dcb000 21dd5000 rlib 3 /usr/local/lib/libkparts.so.3.0
06018000 2605f000 rlib 4 /usr/local/lib/libkio.so.6.0
0cbe5000 2cc2c000 rlib 5 /usr/local/lib/libkdeui.so.6.0
0200d000 22011000 rlib 5 /usr/local/lib/libkdesu.so.6.0
06ad4000 26ad8000 rlib 5 /usr/local/lib/libkwalletclient.so.1.0
0f984000 2f9aa000 rlib 8 /usr/local/lib/libkdecore.so.6.0
0f959000 2f961000 rlib 9 /usr/local/lib/libDCOP.so.6.0
0e087000 2e08b000 rlib 9 /usr/lib/libutil.so.11.0
08817000 2881b000 rlib 9 /usr/local/lib/libart_lgpl_2.so.5.16
080f2000 280f9000 rlib 9 /usr/local/lib/libkdefx.so.6.0
03db9000 23ebd000 rlib 11 /usr/local/lib/libqt-mt.so.3.34
05105000 2510b000 rlib 12 /usr/local/lib/libjpeg.so.62.0
028f8000 228ff000 rlib 12 /usr/local/lib/libpng.so.4.1
04b71000 24b75000 rlib 20 /usr/X11R6/lib/libXext.so.8.0
044a0000 244eb000 rlib 22 /usr/X11R6/lib/libX11.so.8.1
01a75000 21a79000 rlib 14 /usr/X11R6/lib/libSM.so.8.0
0f0f9000 2f100000 rlib 15 /usr/X11R6/lib/libICE.so.8.0
0ecbb000 2ecc4000 rlib 11 /usr/lib/libpthread.so.6.1
0ec09000 2ec0d000 rlib 14 /usr/X11R6/lib/libXrender.so.3.1
063ea000 263f2000 rlib 12 /usr/lib/libz.so.4.0
034de000 234e9000 rlib 1 /usr/lib/libstdc++.so.34.0
031c9000 231d0000 rlib 13 /usr/lib/libm.so.2.0
0d7b2000 2d7e9000 rlib 1 /usr/lib/libc.so.34.2
08c62000 28c6a000 rlib 1 /usr/local/lib/libmng.so.2.0
0ea72000 2ea7d000 rlib 1 /usr/local/lib/liblcms.so.1.12
0242b000 2243e000 rlib 1 /usr/X11R6/lib/libGL.so.3.1
04977000 2497c000 rlib 1 /usr/X11R6/lib/libXmu.so.8.0
004b7000 204bb000 rlib 1 /usr/X11R6/lib/libXi.so.8.0
09fe1000 29fe4000 rlib 1 /usr/X11R6/lib/libXrandr.so.4.0
03bb3000 23bb7000 rlib 1 /usr/X11R6/lib/libXcursor.so.2.2
0f15d000 2f161000 rlib 1 /usr/X11R6/lib/libXinerama.so.3.0
055bb000 255bf000 rlib 1 /usr/X11R6/lib/libXft.so.5.0
05b77000 25b93000 rlib 3 /usr/X11R6/lib/libfreetype.so.13.0
07560000 2756e000 rlib 2 /usr/X11R6/lib/libfontconfig.so.2.0
0f614000 2f620000 rlib 1 /usr/X11R6/lib/libXt.so.8.0
099e3000 299ec000 rlib 2 /usr/X11R6/lib/libexpat.so.5.0
01f2b000 01f2b000 rtld 1 /usr/libexec/ld.so
Now that I know what ktrace is (I'm used to strace), here is: ktrace
konqueror https://webauth.comcast.net with the perms of 600 on
libcrypto.so.11.0
$ ktrace konqueror https://webauth.comcast.net
konqueror: ERROR: Error in BrowserExtension::actionSlotMap(), unknown
action : searchProvider
/usr/local/bin/kdeinit:/usr/lib/libssl.so.9.0: undefined symbol 'X509_free'
/usr/local/bin/kdeinit: /usr/lib/libssl.so.9.0: can't resolve reference
'X509_free'
/usr/local/bin/kdeinit:/usr/lib/libssl.so.9.0: undefined symbol
'i2d_DHparams'
/usr/local/bin/kdeinit: /usr/lib/libssl.so.9.0: can't resolve reference
'i2d_DHparams'
/usr/local/bin/kdeinit:/usr/lib/libssl.so.9.0: undefined symbol
'd2i_DHparams'
/usr/local/bin/kdeinit: /usr/lib/libssl.so.9.0: can't resolve reference
'd2i_DHparams'
/usr/local/bin/kdeinit:/usr/lib/libssl.so.9.0: undefined symbol
'X509_NAME_free'
/usr/local/bin/kdeinit: /usr/lib/libssl.so.9.0: can't resolve reference
'X509_NAME_free'
/usr/local/bin/kdeinit:/usr/lib/libssl.so.9.0: undefined symbol
'CRYPTO_lock'
lazy binding failed!
kioslave: ####### CRASH ###### protocol = https pid = 4493 signal = 11
I get the error I reported earlier in the browser window, the gui
configurator crashes out.
Here is the same command, but with the perms of 644 on libcrypto.so.11.0:
$ ktrace konqueror https://webauth.comcast.net
konqueror: ERROR: Error in BrowserExtension::actionSlotMap(), unknown
action : searchProvider
kdecore (KLibLoader): WARNING: KLibrary: Unable to resolve symbol
kdecore (KLibLoader): WARNING: KLibrary: Unable to resolve symbol
kdecore (KLibLoader): WARNING: KLibrary: Unable to resolve symbol
kdecore (KLibLoader): WARNING: KLibrary: Unable to resolve symbol
kdecore (KLibLoader): WARNING: KLibrary: Unable to resolve symbol
kdecore (KLibLoader): WARNING: KLibrary: Unable to resolve symbol
kdecore (KLibLoader): WARNING: KLibrary: Unable to resolve symbol
kdecore (KLibLoader): WARNING: KLibrary: Unable to resolve symbol
Nothing critical here, and konqueror works fine.
Hope that this helps.
Chris.
BTW -- just so you know (sounds like you are a developer/maintainer),
there is another perms issue I had I will post separately regarding
/dev/apm. This caused my battery monitor in KDE not to show when I was
not root, and crashed out the configuration utility -- again without
error output. Chaning the perms to 666 fixed the problem.
[EMAIL PROTECTED] wrote:
>>>>>>"c" == Chris <[EMAIL PROTECTED]> writes:
>>>>>>
>>>>>>
>c> I did get it, and it was a permissions issue.
>
> I saw your message; however, there is no "libcrypto.so" file in
> OpenBSD -current. There is a versioned libcrypto.so.12.0 in
> -current and libcrypto.so.11.0 in OpenBSD 3.6.
>
>c> Now, why the permissions were set to 600 on that library is beyond
>c> me. I can guarantee you I didn't do it. Like I said, the system
>c> is pristine. It must have come from the package that way. I
>c> assume it came from the package "libgcrypt". Maybe that is worth
>c> looking in to that package.
>
> Those perms s/b 444. Ports/packages should never automatically
> install any files over existing system files, ie. libcrypto.
> Virtually all packages, including the security/libgcrypt you
> mention, install under the /usr/local hierarchy. In fact, -current
> libgcrypt installs libgcrypt (notice the 'g'), so I don't see how it
> could be responsible for the problem.
>
>c> I did post the solution for posterity.
>
> I think there's still something missing. What is the full path name
> of the file whose perms were wrong? And, what are the results of
> "ldd `which konqueror`"?
>
>Regards, Bob
