UYsing nmcli, I have set a network-manager setting that is not supported in the plasma editor (for example  802-1x.subject-match).  I understand that not all options can be eaily exposed in the gui, so setting it from the command line is fine with me.

However, when I now make an unrelated change using th plasma-nm-editor (for example, changing the AP priority), the changes I made from the cli are silently reset.  In case of the 802-1x.subject-match property, this is quite disturbing, as it opens up my laptops to attacks using rogue access points and mitm-attacks.

So, please keep any changes written from the graphical client as compact as possible (i.e., only writing the keys that are actually exposed in the gui, or even only hte keys that have been changed), instead of resetting all variables.

Reproducible: Always

Steps to Reproduce:
0. (create an wifi network "eduroam" with 802.11x authn)
1. nmcli c modify eduroam 802-1x.subject-match radius.example.edu
2. open nm-connection editor in kde
3. change an unrelated setting (e.g., priority), and save
4. "nmcli c show eduroam" shows the "802-1x.subject-match" property has been reset

Actual Results:  
see above

Expected Results:  
802-1x.subject-match poperty should have been kept

I'd consider this a security bug (see above), but I think the group of people affected is not very large.