Activity log for bug #278784
| Date | Who | What changed | Old value | New value | Message |
|---|---|---|---|---|---|
| 2008-10-05 20:43:54 | Jonathan Clarke | bug | added bug | ||
| 2008-10-07 08:57:04 | Thierry Carrez | openvpn: importance | Undecided | Medium | |
| 2008-10-07 08:57:04 | Thierry Carrez | openvpn: statusexplanation | According to http://svn.openvpn.net/projects/openvpn/branches/BETA21/openvpn/management/management-notes.txt the NEED-OK line is a notification that is supposed to be acked using the management interface (issue a "needok token-insertion-request ok" command to the management port)... That makes it quite unsuitable at boot-up time. See also discussions from other users not happy with this on : http://sourceforge.net/mailarchive/message.php?msg_id=48BF842A.1040901%40aixigo.de Jonathan : does booting with the token already inserted (before the notification pops up) work ? Does a workaround where we would filter out configurations that use pkcs#11 so that they are not autostarted make sense ? Would looking for "pkcs11-id" in the configuration be enough to detect them ? | ||
| 2008-10-16 06:24:51 | Thierry Carrez | openvpn: status | New | Fix Released | |
| 2008-10-16 06:24:51 | Thierry Carrez | openvpn: statusexplanation | According to http://svn.openvpn.net/projects/openvpn/branches/BETA21/openvpn/management/management-notes.txt the NEED-OK line is a notification that is supposed to be acked using the management interface (issue a "needok token-insertion-request ok" command to the management port)... That makes it quite unsuitable at boot-up time. See also discussions from other users not happy with this on : http://sourceforge.net/mailarchive/message.php?msg_id=48BF842A.1040901%40aixigo.de Jonathan : does booting with the token already inserted (before the notification pops up) work ? Does a workaround where we would filter out configurations that use pkcs#11 so that they are not autostarted make sense ? Would looking for "pkcs11-id" in the configuration be enough to detect them ? | Thanks for your testing :) So this has been fixed by reverting to hardy behavior. Fix shipped in 2.1~rc11-1ubuntu2 |
