Closed chtzvt closed 1 year ago
Why not point out the newer version in your .ssh/config
Closing this issue with a bit of background:
Until a recent update to openssh on macOS, ssh-agent would reject any configuration where dylibs would load from non-whitelisted directories. This was one of the issues underlying #387, and the reason I ended up copying libykcs11 to /usr/local/lib
in the first place.
Apparently, it's now possible to load /opt/homebrew/lib/libykcs11.dylib
directly as a PKCS11Provider
in my ~/.ssh/config, so this is no longer a problem 😄
As of the most recent macOS update (to
Ventura 13.1 (22C65)
), I've experienced the following issue with libykcs11 being loaded by openssh:This behavior is consistent across both of my machines with the same configuration present:
The issue appears to be related to the version of libykpiv.2.dylib provided by this library. On both of my systems, only version
2.3.1
of libykcs11 is present in/opt/homebrew/Cellar/yubico-piv-tool/
, even after reinstalling yubikey-agent and yubico-piv-tool with brew.I temporarily resolved the issue by creating a symlink from
2.3.1
to2.3.0
: