Re: libcrypto oddity after upgrade - AND

From: <rb_at_gid.co.uk>
Date: Sun, 15 Mar 2026 11:09:19 UTC
Hi,

> On 15 Mar 2026, at 07:18, Enji Cooper (yaneurabeya) <yaneurabeya@gmail.com> wrote:
> 
> 
>> On Mar 14, 2026, at 5:38 PM, Bob Bishop <rb@gid.co.uk> wrote:
>> 
>> I do wish Apple Mail wouldn’t do that. Should have read:
>> 
>> Just upgraded this system to 14.3-RELEASE-p9 and I’m seeing:
>> 
>> ld-elf.so.1: /lib/libcrypto.so.30: version OPENSSL_1_1_0 required by /usr/sbin/sshd not defined
>> 
>> What has gone wrong, and how do I fix it? Thanks
> 
> Hi Bob,
> 	How did you upgrade the system?

freebsd-update, from 10.x

> Can you please provide your “uname -a” output and paste the output of “objdump -x /lib/libcrypto.so.30” somewhere?

Fortunately ftp is working...

FreeBSD some.host 14.3-RELEASE-p9 FreeBSD 14.3-RELEASE-p9 GENERIC amd64


/lib/libcrypto.so.30:   file format elf64-x86-64
architecture: x86_64
start address: 0x000000000007f400

Program Header:
    LOAD off    0x0000000000000000 vaddr 0x0000000000000000 paddr 0x0000000000000000 align 2**21
         filesz 0x00000000001c9fcc memsz 0x00000000001c9fcc flags r-x
    LOAD off    0x00000000001ca000 vaddr 0x00000000003ca000 paddr 0x00000000003ca000 align 2**21
         filesz 0x00000000000272f8 memsz 0x0000000000029db0 flags rw-
 DYNAMIC off    0x00000000001e2378 vaddr 0x00000000003e2378 paddr 0x00000000003e2378 align 2**3
         filesz 0x00000000000001a0 memsz 0x00000000000001a0 flags rw-
EH_FRAME off    0x000000000019af04 vaddr 0x000000000019af04 paddr 0x000000000019af04 align 2**2
         filesz 0x0000000000008efc memsz 0x0000000000008efc flags r--
   STACK off    0x0000000000000000 vaddr 0x0000000000000000 paddr 0x0000000000000000 align 2**3
         filesz 0x0000000000000000 memsz 0x0000000000000000 flags rw-
objdump: warning: '/lib/libcrypto.so.30': dynamic sections must be DT_NULL terminated
objdump: error: '/lib/libcrypto.so.30': invalid sh_type for string table section [index 26]: expected SHT_STRTAB, but got Unknown

Which I take to be saying that the lib is corrupt?

> Thank you!
> -Enji

Thanks

--
Bob Bishop
rb@gid.co.uk