| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
$ git subtree pull --prefix shared/c-list/ git@github.com:c-util/c-list.git master --squash
Import commit 'dda36d30c7d655b4d61358519168fa7ce0e9dae9'.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
dda36d30c7 build: update build system
git-subtree-dir: shared/c-list
git-subtree-split: dda36d30c7d655b4d61358519168fa7ce0e9dae9
|
|\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/72
https://github.com/NetworkManager/NetworkManager/pull/290
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Don't accept any unsupported options.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Also in the documentation it's spelled as "timeout"
Fixes: dd0c59c468fb8bf8b728dec1592be1589e9a04eb
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Fixes: dd0c59c468fb8bf8b728dec1592be1589e9a04eb
|
|/ / / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
These were dropped earlier as new sync API must not be the primary way
of calling new routines in libnm.
In this particular case the DBus calls are simple and unlikely to fail.
Most users should use the normal async API and call the finish routine.
However, if the API user is not interested in the result, then they can
simply set the callback to NULL to ignore it.
[thaller@redhat.com: added options argument to start-find method]
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Since 1.10, mm_simple_connect_properties_set_number() is deprecated
and calling it does nothing. Moreover, it triggers a
"deprecated-declarations" warning.
Avoid calling it.
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/issues/99
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/commit/55c3026643ee6c75c0a68171abd884edf035b9ba
|
| | | | |
| | | | |
| | | | |
| | | | | |
Fixes: 386e75ee04ed0b7cc7de6f459963138fed67b5fc
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | | |
Fixes: d081aa1d845440b77208d79fad141c395fa91b0d
|
|\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This adds support for SAE authentication as used for 802.11s Meshing, but
also WPA3-Personal.
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/9
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/65
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This way we generate the error messages on the client side and therefore
can localize them.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
RSN with SAE is what's called WPA3-Personal.
Also, if there's neither PSK nor 802.1x, it's not WPA2.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This allows us to test if we distinguish WPA1, WPA2 and WPA3 in the
client.
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
And, while at that, add a hint to the developer adding new items. It's
helps avoid a mistake that I believe is common (because I just made it
twice...).
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Ordered before wpa-psk so that if the AP supports both WPA-PSK and SAE,
SAE ends up preferred.
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
When SAE key managmenet is used, the supplicant can still use the "psk"
property. Only when the pass phrase doesn't conform to WPA-PSK
limitations, the sae_password must be used.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This adds support for configuring the Wi-Fi connections to use SAE. SAE
is a password-based authentication mechanism that replaces WPA-PSK in
WPA3-Personal.
The pass phrase is still stored in the "psk" property, with some
limitations lifted.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
wpa_supplicant as of version 2.7 still doesn't tell us whether it
supports SAE.
Patch in review: http://lists.infradead.org/pipermail/hostap/2019-January/039338.html
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
The generic connection validation produces a good result:
Error: failed to modify 802-11-wireless-security.psk: ':(' is not a valid PSK.
vs.:
Error: Failed to add 'wifi666' connection: 802-11-wireless-security.psk: property is invalid
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Validate them, like we do on a connection addition.
|
|/ / / / / |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Like also done for autotools, create and use intermediate libraries
from "shared/nm-utils/".
Also, replace "shared_dep" by "shared_nm_utils_base_dep". We don't
need super fine-grained selection of what we link. We can always
link in "shared/libnm-utils-base.a", and let the linker throw away
unsed parts.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Like we do with autotools, otherwise we get a warning:
[576/1030] Compiling C object src/25a6634@@NetworkManager@sta/nm-session-monitor.c.o.
../src/nm-session-monitor.c:31:5: warning: "SESSION_TRACKING_SYSTEMD" is not defined, evaluates to 0 [-Wundef]
#if SESSION_TRACKING_SYSTEMD && SESSION_TRACKING_ELOGIND
^~~~~~~~~~~~~~~~~~~~~~~~
|
|\ \ \ \ \
| | | | | |
| | | | | |
| | | | | | |
https://github.com/NetworkManager/NetworkManager/pull/288
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Extend nm_act_request_get_secrets() API to allow for the underlying
flexibility (of the API that it calls) to accept a strv list of hints.
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Fixes: 3bda3fb60c104114192e4e3c9c4ba0bef84d3a00
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
nm_secret_agent_simple_enable()
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
No "NM" prefix for internal structure.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Refactor memory handling to use cleanup attribute.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
And don't waste 4 bytes per boolean.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Always always when we want a linked list, CList is a better choice than
GSList. It's more convenient to use and is more efficient.
Also, use GSlice allocator for GetSecretRequest data.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
The callback must be invoked, as also documented.
Otherwise, the tracked info gets leaked.
Let NMSecretAgentOld (the caller) be a bit resilient against
bugs in the client, and avoid a crash by prematurely remove
the request-info from the pending list. That does not fully
workaround the bug (it leads to a leak), but at least it does
not cause other "severe" issues.
The leak was present earlier as well.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Use NM_GOBJECT_PROPERTIES_DEFINE() and _notify() and get rid of
the extra tab for indentation.
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
NMSecretAgentOld's get_secrets_cb() gets this right and takes
a floating reference. So this was correct.
However, make this a bit more robust, and don't pass on
floating references. This was, we don't require the callee
to consume the reference.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
The completion of the request and the deletion usually goes hand in
hand. Add a function to unify them.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Most of the times we actually need a NMSecretAgentSimple typed pointer.
This way, need need to cast less.
But even if we would need to cast more, it's better to have pointers
point to the actual type, not merely to avoid shortcomings of C.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
NMSecretAgentSimple
No caller cared about the NM_SECRET_AGENT_ERROR_AGENT_CANCELED reason.
In particular, because previously the requests would keep the secret-agent
instance alive, and this never happend.
Also, NM_SECRET_AGENT_ERROR_AGENT_CANCELED precicley exists for
NMSecretAgentOld:cancel_get_secrets() (as documented). During finalize
we are not cancelled -- at least not the same way as
cancel_get_secrets(). Setting NM_SECRET_AGENT_ERROR_AGENT_CANCELED
is wrong.
Anyway, we have a default error for such cases already.
|