Bug 1268030 - 20 seconds timeout is not sufficient for VPN password entry
Summary: 20 seconds timeout is not sufficient for VPN password entry
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: NetworkManager
Version: 7.2
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Lubomir Rintel
QA Contact: Desktop QE
Depends On:
Blocks: 1349740
TreeView+ depends on / blocked
Reported: 2015-10-01 15:36 UTC by Lubomir Rintel
Modified: 2016-06-24 06:57 UTC (History)
9 users (show)

Fixed In Version: NetworkManager-1.0.6-14.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1349740 (view as bug list)
Last Closed: 2015-11-19 11:05:27 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2015:2315 0 normal SHIPPED_LIVE Moderate: NetworkManager security, bug fix, and enhancement update 2015-11-19 10:06:58 UTC

Description Lubomir Rintel 2015-10-01 15:36:43 UTC
NetworkManager VPN plugins drop off the bus after 20 seconds of inactivity. That's too short for users with disabilities or complex authentication mechanisms (2FA with a token).

I'm also adding a regression tag, since in RHEL 7.1 the counter was not effective for the first VPN connection attempt.

Comment 3 Thomas Haller 2015-10-01 15:49:59 UTC
(In reply to Lubomir Rintel from comment #1)
> Upstream fix:
> http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?h=nm-1-
> 0&id=f7617511bb94bbae2dbf99231a7d6be29575aa4d

No strong opinion from my side.

Comment 4 Dan Williams 2015-10-01 17:31:28 UTC
No objections from me either; this should get handled better upstream in the future but this is an OK fix for now.

Comment 6 Vladimir Benes 2015-10-26 20:31:10 UTC
Dialog is now shown for two minutes. connecting works as expected even after longer period of time.

Comment 7 errata-xmlrpc 2015-11-19 11:05:27 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.