When I start or restart Prosody, it claims that it is unable to find LuaSec: ************************** Prosody was unable to find LuaSec This package can be obtained in the following ways: Source: https://github.com/brunoos/luasec Debian/Ubuntu: sudo apt-get install lua-sec luarocks: luarocks install luasec SSL/TLS support will not be available More help can be found on our website, at https://prosody.im/doc/depends ************************** The LuaSec port is installed. I already tried to reinstall Prosody and its dependencies but the message still occurs.
I'm not able to reproduce this in my environment. Perhaps you can attach your current list of packages?
Created attachment 206514 [details] List of installed ports Hello, the list of installed ports is attached. BR Zilon
Ok, I don't see anything wrong there. As suggested by the devs, does lua51 -e 'print(require"ssl" and "ok")' Work correctly?
When I try lua51 -e 'print(require"ssl" and "ok")' I get the following error: lua51: error loading module 'ssl.core' from file '/usr/local/lib/lua/5.1/ssl.so': /usr/local/lib/lua/5.1/ssl.so: Undefined symbol "sk_num" stack traceback: [C]: ? [C]: in function 'require' /usr/local/share/lua/5.1/ssl.lua:8: in main chunk [C]: in function 'require' (command line):1: in main chunk [C]: ? Thany you for the hint. So this seems to be a Lua issue on my machine.
Interesting. Can you do an ldd /usr/local/lib/lua/5.1/ssl.so
This given the the following output: /usr/local/lib/lua/5.1/ssl.so: libssl.so.111 => /usr/lib/libssl.so.111 (0x800677000) libcrypto.so.111 => /lib/libcrypto.so.111 (0x800e00000) libc.so.7 => /lib/libc.so.7 (0x800248000) libthr.so.3 => /lib/libthr.so.3 (0x80070c000)
Ok, unfortunately that doesn't clear much up. Only other thing I can think of is did you install the packages from pkg or ports?
OK, thank you so far. I installed and also reinstalled from ports.
I'd say try uninstalling and installing straight from the pkg repos (latest) and see if it works. Otherwise, I'm unfortunately out of ideas.
That finally helped! Thank you! The reason seems to be an issue with lua51-luasec-0.8 from ports. If then lua51-luasec-0.7 from packages is used, everything is fine.
Ok, cool. I actually only updated the port to LuaSec 0.8 yesterday, so that probably wasn't the original problem, but glad it works now. I've tested 0.8 in production, so when you update via packages, it should hopefully continue to work.