TrueNas 13 update: message on console "Deprecated code (to be removed in FreeBSD 14): Asymmetric crypto features via /dev/crypto"

bermau

Dabbler
Joined
Jul 4, 2017
Messages
28
hello everyone,
I looked on the forum but I could not find any posts on the subject.

I updated my truenas box to release 13, on the console I see the following message repeated endlessly:

Deprecated code (to be removed in FreeBSD 14): Asymmetric crypto features via /dev/crypto
(see attached file)

can someone show me how to solve?

I think it depends on the jails, because with the jails stopped the messages do not appear.
my jails: amule, caddy, heimdall, jackett (plugin), nextcloud, plex, radarr, sabnzdb, sonarr, tautulli (plugin), transmission (plugin), zoneminder (plugin).

I am not an expert, however I can easily move through the CLI
Thanks in advance.
MB
 

Attachments

  • deprecated code console truenas.jpg
    deprecated code console truenas.jpg
    453.5 KB · Views: 277

Samuel Tai

Never underestimate your own stupidity
Moderator
Joined
Apr 24, 2020
Messages
5,399

bkw777

Cadet
Joined
Aug 7, 2022
Messages
8
I have this too and I too don't know what to look for to address it. I do have sshd enabled on the host and in a couple jails, but that still doesn't tell me anything. Is there a particular cipher to disable in sshd_config, or some non-obvious jail setting? in the host? in the jail? A particular version of sshd to remove or install? 2 of my jails are 11.3 and are shut down, 2 are new fresh created 13.1 and up & running (unifi & jellyfin). Host is 13.0 core.
These console messages always seem to come right after some other messages that look like they have to do with the swap partitions on all the drives.
...
GEOM_MIRROR: Device swap0 destroyed.
GEOM_MIRROR: Device mirror/swap0 launched (2/2).
GEOM_MIRROR: Device mirror/swap1 launched (2/2).
GEOM_MIRROR: Device mirror/swap2 launched (2/2).
GEOM_ELI: Device mirror/swap0.eli created.
GEOM_ELI: Encryption: AES-XTS 128
GEOM_ELI: Crypto: accelerated software.
...
Depreciated code ( to be removed ...
 

Volts

Patron
Joined
May 3, 2021
Messages
210
I don’t think this is necessarily SSH.

My guess is that there’s an old jail or two, and they’re probing for crypto hardware support, and you almost certainly don’t have any of that anyway, so you can ignore this.

Or if it happens just once when the system boots it can definitely be ignored.

I suspect the messages could be disabled by disabling the interface.


See sysctls kern.userasymcrypto and kern.cryptodevallowsoft.

Here’s the later change where this interface is fully removed -

 
Last edited:

bkw777

Cadet
Joined
Aug 7, 2022
Messages
8
A probe makes sense, and removes the worry that something is going to break tomorrow because I didn't deal with it.
 
Top