On Thu, 18 Jan 2024 19:52:53 +0100,j...@chen.org.nz wrote:
> 
> Hi,
> 
> I've started seeing the following in my system logs on my recently built 
> cyrus-sasl 2.1.28_3:
>  unable to dlopen /usr/local/lib/sasl2/libotp.so.3: Shared object 
> "libopie.so.8" not found, required by "libotp.so.3"
> 
> Does cyrus-sasl2 required a dependency declaration on security/opie?

Did you run 'make delete-old-libs' after upgrading to stable/14 or main?
Have you tried to rebuild security/cyrus-sasl2 after removing
libopie.so.8? How did you build/install cyrus-sasl?

You can build libotp.so without security/opie, but does it work as
before?

Without security/opie:

checking OTP... enabled                                                         
                        
checking for opiechallenge in -lopie... no
checking for OPIE... no 

% ldd ./libotp.so.3
/libotp.so.3:
        libcrypto.so.30 => /lib/libcrypto.so.30 (0x3dce37fc000)
        libc.so.7 => /lib/libc.so.7 (0x3dce2b8b000)
        libthr.so.3 => /lib/libthr.so.3 (0x3dce21f7000)

With security/opie:

checking OTP... enabled                                                         
                        
checking for opiechallenge in -lopie... yes      
checking opie.h usability... yes                 
checking opie.h presence... no

% ldd ./libotp.so.3
/libotp.so.3:
        libcrypto.so.30 => /lib/libcrypto.so.30 (0xe0a4748000)
        libopie.so.8 => /usr/local/lib/libopie.so.8 (0xe0a599c000)
        libc.so.7 => /lib/libc.so.7 (0xe0a3751000)
        libthr.so.3 => /lib/libthr.so.3 (0xe0a6519000)
        libmd.so.6 => /lib/libmd.so.6 (0xe0a79ca000)

See:

https://www.cyrusimap.org/sasl/sasl/sysadmin.html#the-otp-mechanism
https://www.cyrusimap.org/sasl/sasl/sysadmin.html#otp-via-opie

--
Herbert

Reply via email to