Thanks for your testing :) So this has been fixed by reverting to hardy
behavior.
Fix shipped in 2.1~rc11-1ubuntu2
** Changed in: openvpn (Ubuntu)
Status: New = Fix Released
--
openvpn configuration with token (pkcs11 provider) blocks the boot
https://bugs.launchpad.net/bugs/278784
You
Thanks for your testing :) So this has been fixed by reverting to hardy
behavior.
Fix shipped in 2.1~rc11-1ubuntu2
** Changed in: openvpn (Ubuntu)
Status: New = Fix Released
--
openvpn configuration with token (pkcs11 provider) blocks the boot
https://bugs.launchpad.net/bugs/278784
You
I just tested with the above patch to /etc/init.d/openvpn. This solves
the problem, the boot is not interrupted.
OpenVPN fails to launch this config and logs the following error message to
syslog:
Oct 15 21:35:30 jon-imac ovpn-myconfigname[5225]: ERROR: could not read
token-insertion-request
I just tested with the above patch to /etc/init.d/openvpn. This solves
the problem, the boot is not interrupted.
OpenVPN fails to launch this config and logs the following error message to
syslog:
Oct 15 21:35:30 jon-imac ovpn-myconfigname[5225]: ERROR: could not read
token-insertion-request
A few clarifications : in hardy openvpn also autostarts all
/etc/openvpn/*.conf VPNs at boot (if /etc/default/openvpn has
AUTOSTART=all, which is the default) so there is no change in that area.
However, one difference between the hardy and the intrepid version is that we
merged the fix for the
A few clarifications : in hardy openvpn also autostarts all
/etc/openvpn/*.conf VPNs at boot (if /etc/default/openvpn has
AUTOSTART=all, which is the default) so there is no change in that area.
However, one difference between the hardy and the intrepid version is that we
merged the fix for the
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
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
Hi Thierry,
Booting with the token already inserted does not work. It is a USB
token, so maybe some part of the USB system is not yet up at that point
of the boot.
I'm not sure about the workaround. I can see it leading to confusion:
why do some configurations autostart and not others?. However,
I agree the boot should not be blocked, an option to cancel the start of
that VPN should be provided.
I'll have a look to see if I find an easy fix, I may need your help to
test it though, since I don't own such a token ;)
About the autostart feature, note that you can configure which
I found the autostart config in the end - it's just not possible to
deactivate it while updating Ubuntu :)
No problem to test any fixes, just leave me a note here or by email.
--
openvpn configuration with token (pkcs11 provider) blocks the boot
https://bugs.launchpad.net/bugs/278784
You
I agree the boot should not be blocked, an option to cancel the start of
that VPN should be provided.
I'll have a look to see if I find an easy fix, I may need your help to
test it though, since I don't own such a token ;)
About the autostart feature, note that you can configure which
I found the autostart config in the end - it's just not possible to
deactivate it while updating Ubuntu :)
No problem to test any fixes, just leave me a note here or by email.
--
openvpn configuration with token (pkcs11 provider) blocks the boot
https://bugs.launchpad.net/bugs/278784
You
13 matches
Mail list logo
