https://bugzilla.redhat.com/show_bug.cgi?id=970009 --- Comment #11 from Kevin Cernekee <cernekee@xxxxxxxxx> --- > Woah, installed the token with stoken, rebuilt openconnect with > stoken-devel, launch from the command line with "--token-mode=rsa" > and now I'm asked the pin instead of the passcode (one number for > another... don't know if it's a big achievement or not... :D). You can use "stoken setpin" to cache the pin in ~/.stokenrc, allowing fully unattended operation. Depending on your account lockout policies, you may be able to run openconnect in a loop to auto-reconnect on error: while :; do openconnect -u user --non-inter --token-mode=rsa vpn.example.com; sleep 5; done > NM-openconnect needs to be built against openconnect 5.00 or newer > in order to get stoken support. I've updated it in rawhide and will > update f19 once > https://admin.fedoraproject.org/updates/openconnect-5.01-1.fc19 > makes it to stable (and hence the buildroots). > > We should probably look at enabling OATH support at the same time... The current NM-openconnect head of tree supports RSA but not OATH. I submitted OATH patches here (needs testing): http://lists.infradead.org/pipermail/openconnect-devel/2013-March/001007.html http://lists.infradead.org/pipermail/openconnect-devel/2013-March/001006.html http://lists.infradead.org/pipermail/openconnect-devel/2013-March/001008.html > Intermediate package until upstream replies to your mail about > GnuTLS and removal of the conditional CFLAGS. Replied privately with a couple of follow-on questions. -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=EqUvWZwFSP&a=cc_unsubscribe _______________________________________________ package-review mailing list package-review@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/package-review