Re: Whine: "Could not open /dev/crypto: No such file or directory"

On 18. 12. 13., Yuri Pankov wrote: > David Wolfskill wrote: >> After update from r341844 to r342042, I see the above-cited "whine" when >> I attempt to use an SSH client on the upgraded machine.  SSH client >> function seems OK, so the message is (apparently) merely annoying: >> >>

Re: Whine: "Could not open /dev/crypto: No such file or directory"

David Wolfskill wrote: After update from r341844 to r342042, I see the above-cited "whine" when I attempt to use an SSH client on the upgraded machine. SSH client function seems OK, so the message is (apparently) merely annoying: freebeast(13.0-C)[2] uname -a FreeBSD freebeast.catwhisker.org

Whine: "Could not open /dev/crypto: No such file or directory"

After update from r341844 to r342042, I see the above-cited "whine" when I attempt to use an SSH client on the upgraded machine. SSH client function seems OK, so the message is (apparently) merely annoying: freebeast(13.0-C)[2] uname -a FreeBSD freebeast.catwhisker.org 13.0-CURRENT FreeBSD