From 9a6dcbf895f9da01768e64b73cec88c16157d91e Mon Sep 17 00:00:00 2001
From: Michael Biebl type the security type to check AP flags and device capabilties against,
+ the security type to check AP flags and device capabilities against,
e.g. NMU_SEC_STATIC_WEP
+
@@ -895,7 +903,7 @@ use
+gboolean
+
+
+nm_utils_base64secret_decode ()
+
+
@@ -925,13 +933,13 @@ arguments are valid
-
ap_wpa
bitfield of AP capabilties derived from the AP's WPA beacon, +
bitfield of AP capabilities derived from the AP's WPA beacon, e.g. (NM_802_11_AP_SEC_PAIR_TKIP | NM_802_11_AP_SEC_KEY_MGMT_PSK)
ap_rsn
bitfield of AP capabilties derived from the AP's RSN/WPA2 beacon, +
bitfield of AP capabilities derived from the AP's RSN/WPA2 beacon, e.g. (NM_802_11_AP_SEC_PAIR_CCMP | NM_802_11_AP_SEC_PAIR_TKIP)
TRUE if the device capabilities and AP capabilties intersect and are
+
TRUE if the device capabilities and AP capabilities intersect and are
compatible with the desired type
, FALSE if they are not
type
the security type to check device capabilties against, +
the security type to check device capabilities against, e.g. NMU_SEC_STATIC_WEP
predicate
user_data
(allow-none): user data for predicate
+
user data for predicate
function.
error
const gint64
nm_utils_get_timestamp_msec (void);
+
+
+nm_utils_base64secret_decode ()
+gboolean
+nm_utils_base64secret_decode (const char *base64_key,
+ gsize required_key_len,
+ guint8 *out_key);
+
+Parameters
+
+
+
+
+
+
+
+
+base64_key
+the (possibly invalid) base64 encode key.
+
+
+
+required_key_len
+the expected (binary) length of the key after
+decoding. If the length does not match, the validation fails.
+
+
+
+out_key
+(out): an optional output buffer for the binary
+key. If given, it will be filled with exactly required_key_len
+bytes.
+[allow-none]
+
+
+
+
+
+Since: 1.16
+