Would pulling source for nm and building against the new libopenconnect create a viable solution or is it more indepth than that? On 07/28/2012 02:01 PM, Mike Miller wrote: > On Sat, Jul 28, 2012 at 12:20 PM, David Woodhouse <dwmw2 at infradead.org> wrote: >> On Sat, 2012-07-28 at 12:18 -0400, Mcclelland, Michael B Mr CTR USN USA >> wrote: >>> That solved the issue for me. But I can't seem to get the cert to >>> load when I try to connect the VPN. I'm editing the vpn config and >>> adding the usercert=pkcs11:token=MCCLELLAND.MICHAEL.BLAIR.1250312;id=% >>> 00%02 field as instructed but it's either not finding the token or >>> something isn't clicking to request the pin number. >>> >>> I've attempted other combinations of the pkcs11 url that work from the >>> command line but it doesn't seem to have any effect. >> Did you make sure you're using Mike's new builds of the packages, not >> the standard ones from Ubuntu? > I haven't built NM packages against libopenconnect.so.2 for 12.04, > though, so that's why NetworkManager won't be working for you. Your > NetworkManager is still linked with libopenconnect.so.1 and openssl. > -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 10357 bytes Desc: S/MIME Cryptographic Signature URL: <http://lists.infradead.org/pipermail/openconnect-devel/attachments/20120801/108087d4/attachment-0001.p7s>
