[plasma-nm] [Bug 350521] [RFE] [OpenVPN] kdeplasma-applets-plasma-nm does not support OTP Tokens for OpenVPN connections
https://bugs.kde.org/show_bug.cgi?id=350521 Íñigo changed: What|Removed |Added CC||inigohug...@hotmail.com --- Comment #24 from Íñigo --- We are adding some patches to NetworkManager that I expect that will make this to work from KDE Plasma without any change required. It will need at least NetworkManager 1.46.2 and NetworkManager-openvpn 1.12.0 (tentative, but probable versions). NetworkManager MR: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/1958 -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 464245] Toggle for Mac-Randomization
https://bugs.kde.org/show_bug.cgi?id=464245 Íñigo changed: What|Removed |Added CC||inigohug...@hotmail.com --- Comment #2 from Íñigo --- NetworkManager developer here. I was filling a bug and I saw this one. SUMMARY NetworkManager allows to manually specify a MAC address to do MAC-spoofing. It also support some special values that allows to automatically generate the MAC address according to different criteria. For example, "random" creates a random MAC address each time that the profile is activated, "stable" creates a MAC address when the profile is created and it's always used for that profile, and "stable-ssid" creates a different MAC for each WiFi's SSID. Plasma-nm doesn't support these special values, and it only allows to introduce manually an address. In order to increase user's privacy, setting "stable-ssid" as system-wide default value is being discussed in Fedora: https://discussion.fedoraproject.org/t/f40-change-proposal-wifi-mac-randomization-system-wide/99856 It would be nice that plasma-nm understand these values: 1. A user without much knowledge, that doesn't know what a MAC address it, could select a value from a combobox, for example, with more hints about what do they mean (example: "no privacy", "some privacy", etc.) 2. If one of the special values is selected in a profile, either via nmcli or because it's the default value, the GUI would reflect that. If plasma-nm doesn't understand them, it won't be able to show the real current value to the user. Note that in some cases, not being able to understand and/or configure this will lead to the user not being able to connect to some networks. I mean, connecting to networks that do MAC address filtering (this is why we are proposing "stable-ssid" as default in Fedora, and not "random", for example). STEPS TO REPRODUCE 1. Change the MAC address: `nmcli connection modify CON_NAME wifi.cloned-mac random` (with devel version of NM you can select stable-ssid) 2. Open plasma-nm OBSERVED RESULT A different MAC address is shown each time, the user doesn't know that "random" is configured EXPECTED RESULT Plasma-nm reflects these special values so the user understand them and can change between them. SOFTWARE/OS VERSIONS KDE Plasma Version: all ADDITIONAL INFORMATION I don't have a clear idea/proposal about what the best UI would be regarding UX. I also have some doubts about the convenience of showing all the possible values to the user. For example, "stable" can be confusing because a casual user might not know what a "connection profile" is in NetworkManager. However, if not all values are available in the GUI, what happens if the value is selected via CLI or distro's default? The special values that NM supports are: - preserve: NM doesn't modify the current MAC - permanent: use the hw's permanent MAC - random: different MAC each time that you connect - stable: different MAC for each connection profile, use it always you connect that profile - stable-ssid (wifi only): different MAC for each WiFi SSID, use it always for the same SSID, even if you delete and create again the connection profile. As I say, the last one is being proposed as default in Fedora. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 471008] Allow to ignore editorconfig rules
https://bugs.kde.org/show_bug.cgi?id=471008 --- Comment #4 from Íñigo --- If nobody else is willing to do it, I can try, but then it can take lot of time. I have almost no free time lately, and I don't know KDE framework nor I am familiar at all wit the code base nor with the process to contribute. With your help I will try, but it will be very slow. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 471008] Allow to ignore editorconfig rules
https://bugs.kde.org/show_bug.cgi?id=471008 --- Comment #2 from Íñigo --- Maybe this is not the best reason to convince you, but anyway is an additional reason: all other editors I know with editorconfig support (or any other formatting tool) allow not to use it, either it is opt-in or opt-out, either via plugins or builtin. I'm totally favourable to the opt-out approach: editorconfig enabled by default, but user can disable it. It's true that the file is in the project, but maybe it's not by user choice, but because it's a repo used by many people and the file is added for convenience of the developers, but not enforcing its use. User freedom should prevail, and in any case it's the project owners' responsibility to enforce the formatting rules, not the editor chosen by each developer's responsibility. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 471008] New: Allow to ignore editorconfig rules
https://bugs.kde.org/show_bug.cgi?id=471008 Bug ID: 471008 Summary: Allow to ignore editorconfig rules Classification: Applications Product: kate Version: unspecified Platform: Other OS: All Status: REPORTED Severity: normal Priority: NOR Component: indentation Assignee: kwrite-bugs-n...@kde.org Reporter: inigohug...@hotmail.com Target Milestone: --- Kate supports parsing .editorconfig files to apply its formatting rules. However, this happens always there is an .editorconfig file present, and it is not possible to avoid it. Although using the rules from .editorconfig is almost always the desired behaviour, there are some cases where this is not desired and deleting the file would be uncomfortable because it's part of the repository. To name a few: - There are contributors of the project that don't like automatic formatting and want to do the formatting manually, or with different tools - The file is added late, when the project already has lot of developed code, but the team doesn't want it to cause massive reformatting in old files that are not touched frequently I think it should be possible to disable using editorconfig (and maybe also kateconfig) from settings. -- You are receiving this mail because: You are watching all bug changes.
