Bug 1036380 - NetworkManager-openvpn-gnome enters a loop when loading a certificate for a new OpenVPN connection
Summary: NetworkManager-openvpn-gnome enters a loop when loading a certificate for a n...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager-openvpn
Version: 19
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-01 18:37 UTC by hlinden
Modified: 2015-02-17 19:29 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-17 19:29:01 UTC
Type: ---


Attachments (Terms of Use)
.p12 certificate encrypted (6.12 KB, application/x-pkcs12)
2013-12-02 16:49 UTC, hlinden
no flags Details
.p12 certificate unencrypted (6.12 KB, application/x-pkcs12)
2013-12-02 16:49 UTC, hlinden
no flags Details

Description hlinden 2013-12-01 18:37:06 UTC
User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:25.0) Gecko/20100101 Firefox/25.0
Build Identifier: 

When I attempt to add a new OpenVPN connection, be it via nm-connection-editor or gnome-control-center network the window freezes and the process uses 100% CPU. A quick strace shows, that the process loops through this:

lstat("/home/harald/Dokumente/vpn_cik/cik-backflow3-TCP-80-jlind3.p12", {st_mode=S_IFREG|0644, st_size=6269, ...}) = 0
lstat("/home/harald/Dokumente/vpn_cik", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
lstat("/home/harald/Dokumente", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
lstat("/home/harald", {st_mode=S_IFDIR|0700, st_size=4096, ...}) = 0
lstat("/home", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
lstat("/", {st_mode=S_IFDIR|0555, st_size=4096, ...}) = 0
futex(0x1b1ba64, FUTEX_WAKE_OP_PRIVATE, 1, 1, 0x1b1ba60, {FUTEX_OP_SET, 0, FUTEX_OP_CMP_GT, 1}) = 1
futex(0x1b1ba30, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0x18a0fe0, FUTEX_WAKE_PRIVATE, 1) = 1
poll([{fd=5, events=POLLIN}, {fd=6, events=POLLIN}, {fd=3, events=POLLIN}, {fd=9, events=POLLIN}, {fd=12, events=POLLIN}, {fd=11, events=POLLIN}], 6, 0) = 2 ([{fd=5, revents=POLLIN}, {fd=6, revents=POLLIN}])
read(5, "\1\0\0\0\0\0\0\0", 16)         = 8
poll([{fd=6, events=POLLIN|POLLOUT}], 1, 4294967295) = 1 ([{fd=6, revents=POLLIN|POLLOUT}])
recvfrom(6, "U\2\2026\244$K\0\3\4\4\0\0\0\0\0\0\0\0\4\4\4\4\4\0\0\3\37%\2\0\0", 4096, 0, NULL, NULL) = 32
writev(6, [{"\22\0\r\0\341\1\240\1c\1\0\0T\1\0\0\10\27\v\0\33\0\0\0VPN-Verb"..., 16380}, {NULL, 0}, {"", 0}], 3) = 16380
recvfrom(6, 0x170e434, 4096, 0, 0, 0)   = -1 EAGAIN (Resource temporarily unavailable)
write(2, "\n** (nm-connection-editor:4807):"..., 73) = 73
access("/home/harald/Dokumente/vpn_cik/cik-backflow3-TCP-80-jlind3.p12", F_OK) = 0
open("/home/harald/Dokumente/vpn_cik/cik-backflow3-TCP-80-jlind3.p12", O_RDONLY) = 17
fstat(17, {st_mode=S_IFREG|0644, st_size=6269, ...}) = 0
read(17, "0\202\30y\2\1\0030\202\30?\6\t*\206H\206\367\r\1\7\1\240\202\0300\4\202\30,0\202"..., 6269) = 6269
close(17)                               = 0
write(2, "\n** (nm-connection-editor:4807):"..., 73) = 73
access("/home/harald/Dokumente/vpn_cik/cik-backflow3-TCP-80-jlind3.p12", F_OK) = 0
open("/home/harald/Dokumente/vpn_cik/cik-backflow3-TCP-80-jlind3.p12", O_RDONLY) = 17
fstat(17, {st_mode=S_IFREG|0644, st_size=6269, ...}) = 0
read(17, "0\202\30y\2\1\0030\202\30?\6\t*\206H\206\367\r\1\7\1\240\202\0300\4\202\30,0\202"..., 6269) = 6269
close(17)                               = 0
write(2, "\n** (nm-connection-editor:4807):"..., 73) = 73
access("/home/harald/Dokumente/vpn_cik/cik-backflow3-TCP-80-jlind3.p12", F_OK) = 0
open("/home/harald/Dokumente/vpn_cik/cik-backflow3-TCP-80-jlind3.p12", O_RDONLY) = 17
fstat(17, {st_mode=S_IFREG|0644, st_size=6269, ...}) = 0
read(17, "0\202\30y\2\1\0030\202\30?\6\t*\206H\206\367\r\1\7\1\240\202\0300\4\202\30,0\202"..., 6269) = 6269
close(17)                               = 0
write(2, "\n** (nm-connection-editor:4807):"..., 73) = 73
write(2, "\n(nm-connection-editor:4807): Gt"..., 117) = 117
write(2, "\n(nm-connection-editor:4807): Gt"..., 117) = 117
lstat("/home/harald/Dokumente/vpn_cik/cik-backflow3-TCP-80-jlind3.p12", {st_mode=S_IFREG|0644, st_size=6269, ...}) = 0
lstat("/home/harald/Dokumente/vpn_cik", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
lstat("/home/harald/Dokumente", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
lstat("/home/harald", {st_mode=S_IFDIR|0700, st_size=4096, ...}) = 0
lstat("/home", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
lstat("/", {st_mode=S_IFDIR|0555, st_size=4096, ...}) = 0
futex(0x1b1ba64, FUTEX_WAKE_OP_PRIVATE, 1, 1, 0x1b1ba60, {FUTEX_OP_SET, 0, FUTEX_OP_CMP_GT, 1}) = 1
poll([{fd=5, events=POLLIN}, {fd=6, events=POLLIN}, {fd=3, events=POLLIN}, {fd=9, events=POLLIN}, {fd=12, events=POLLIN}, {fd=11, events=POLLIN}], 6, 0) = 2 ([{fd=5, revents=POLLIN}, {fd=6, revents=POLLIN}])
read(5, "\1\0\0\0\0\0\0\0", 16)         = 8
write(2, "\n** (nm-connection-editor:4807):"..., 73) = 73
access("/home/harald/Dokumente/vpn_cik/cik-backflow3-TCP-80-jlind3.p12", F_OK) = 0
open("/home/harald/Dokumente/vpn_cik/cik-backflow3-TCP-80-jlind3.p12", O_RDONLY) = 17
fstat(17, {st_mode=S_IFREG|0644, st_size=6269, ...}) = 0
read(17, "0\202\30y\2\1\0030\202\30?\6\t*\206H\206\367\r\1\7\1\240\202\0300\4\202\30,0\202"..., 6269) = 6269
close(17)                               = 0
write(2, "\n** (nm-connection-editor:4807):"..., 73) = 73


And repeat.

Reproducible: Always

Steps to Reproduce:
1. click on Network-connections, network setting.
2. add VPN connection, OpenVPN.
3. choose certificate from drop-down menu and the file dialogue that opens.
4. freeze, see above
Actual Results:  
Freeze.

Expected Results:  
Loading certificate.

Comment 1 Jirka Klimes 2013-12-02 15:23:59 UTC
I can't reproduce that. Would you provide more information for us to help diagnosis?
$ rpm -q NetworkManager
$ rpm -q nm-connection-editor
$ rpm -q NetworkManager-openvpn

What type of OpenVPN authentication do you use? What type of the certificate is it? Would you share the certificate if it is not private?

Comment 2 hlinden 2013-12-02 16:48:29 UTC
NetworkManager-0.9.8.8-1.fc19.x86_64
nm-connection-editor-0.9.8.4-1.git20131028.fc19.x86_64
NetworkManager-openvpn-0.9.8.2-3.fc19.x86_64

I have revoked the certificate and removed the password. See attachments.

We're using SSL/TLS + User Auth. We have pfSense running and generate the certs there and export them as .p12 through the "Client Export" plugin.

Comment 3 hlinden 2013-12-02 16:49:20 UTC
Created attachment 831691 [details]
.p12 certificate encrypted

Comment 4 hlinden 2013-12-02 16:49:52 UTC
Created attachment 831693 [details]
.p12 certificate unencrypted

Comment 5 Fedora End Of Life 2015-01-09 20:45:00 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 6 Fedora End Of Life 2015-02-17 19:29:01 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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