This bug was fixed in the package openconnect - 7.08-1
---
openconnect (7.08-1) unstable; urgency=medium
* New upstream version 7.08
- Fix MTU detection (Closes: #847135)
* d/libopenconnect5.{shlibs,symbols}: Update for new release
* d/p/juniper-content-length.patch: Drop, a
We do build with GSSAPI (as of 7.07-1), but I don't see any direct
dependency from Kerberos to OpenSSL on Debian or Ubuntu systems, only if
the (non-default) krb5-k5tls or krb5-pkinit plugins are installed.
So yeah, for now 7.08-1 will have Yubikey but still no TPM support.
--
You received this
Isn't that true of Kerberos too? Or do you not build with GSSAPI support
either? I really ought to add that to 'openconnect --version' output.
Perhaps when addressing the OpenSSL 1.1 build problems, we could port it
to GnuTLS instead?
--
You received this bug notification because you are a membe
Yubikey support is enabled in the packaging repo, will be in the next
release, either 7.07-3 or 7.08-1, whichever comes first.
https://anonscm.debian.org/cgit/collab-
maint/openconnect.git/commit/?id=0649b9a1e1cbc3965a8847ff0c90653c1f3c4b9c
** Changed in: openconnect (Ubuntu)
Status: Confi
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: openconnect (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1649227
Title:
I can certainly build with libpcsclite for Yubikey support.
Correct me if I'm wrong, but it looks to me like libtspi links with
libssl, so we'd want to avoid linking that into libopenconnect.
Moreover, there is some OpenSSL 1.0 → 1.1 transition trouble at the
moment, and the state of libtspi in D
