Bug 1634081

Summary: NetworkManager - Cant save config if Pre-Shared Key is selected.
Product: [Fedora] Fedora Reporter: jeffrey Smith <jeffrey_smith>
Component: NetworkManager-strongswanAssignee: Mikhail Zabaluev <mikhail.zabaluev>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: unspecified    
Version: 28CC: code, mikhail.zabaluev
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-05-28 22:46:07 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Settings to reproduce none

Description jeffrey Smith 2018-09-28 17:42:08 UTC
Created attachment 1488178 [details]
Settings to reproduce

Description of problem:

If you select Pre-Shared key for Authentication The apply button will remain greyed out and there is no way to save.


Version-Release number of selected component (if applicable):

NetworkManager-strongswan-1.4.3-1.fc28.src.rpm


How reproducible:

Screenshot of settings attached, 100% reproducible.

Actual results:

greyed out Apply/save button


Expected results:

A text box to enter the Pre-shared Key and to be able to click Apply/save.

Comment 1 Mikhail Zabaluev 2018-10-06 06:37:12 UTC
It turns out that a minimum PSK strength is enforced in NetworkManager-strongswan in a somewhat opinionated way: the GUI requires the key to be at least 20 characters.

Here is a comment from a developer: https://bugs.launchpad.net/ubuntu/+source/network-manager-strongswan/+bug/1697536/comments/4

Comment 2 Ben Cotton 2019-05-02 20:44:14 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora 'version' of '28'.

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 28 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 3 Ben Cotton 2019-05-28 22:46:07 UTC
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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.