#2026 [NetworkManager] VPN connection require "sudo" permissions | rhbz#2437985
Opened by blockerbot. Modified

Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2437985 **
Information from BlockerBugs App:
2437985

Current vote summary

Commented but haven't voted yet: lruzicka

The votes have been last counted at 2026-02-16 17:53 UTC and the last processed comment was #comment-1004669

To learn how to vote, see:
https://pagure.io/fedora-qa/blocker-review
A quick example: BetaBlocker +1 (where the tracker name is one of BetaBlocker/FinalBlocker/BetaFE/FinalFE/0Day/PreviousRelease and the vote is one of +1/0/-1)


I'm not sure what the point of the "Make this connection available to other users" checkbox is if sudo is required no matter what.

That being said, it is still possible to create a VPN connection, so I don't see this as a violation of the cited criteria.

BetaBlocker -1

Criteria states:-

Using the default network configuration tools for the console and for release-blocking desktops, it must be possible to establish a working connection to common OpenVPN, openconnect-supported and vpnc-supported VPN servers with typical configurations.

This doesn't mention if this is a privileged or non-privileged user account and since you can get a working connection I am:-

BetaBlocker -1

It's annoying, but just annoying, clearly not a blocker for me.
BetaBlocker -1

AGREED RejectedBetaBlocker

The following votes have been closed:

AGREED AcceptedBetaFreezeException

Discussed at the 2026-02-16 (blocker / freeze exception) review meeting:

This is accepted as it's a pretty annoying experience for VPN users, and it would clearly be better to ship with it fixed if safely possible.

https://meetbot-raw.fedoraproject.org//blocker-review_matrix_fedoraproject-org/2026-02-16/f44-blocker-review.2026-02-16-17.00.txt

The following votes have been closed:

  • Accepted BetaFreezeException (+0, 0, -0)

Log in to comment on this ticket.

Metadata