From: Denis Kenzior <denkenz@gmail.com>
To: Andrew Zaborowski <andrew.zaborowski@intel.com>, iwd@lists.linux.dev
Subject: Re: [PATCH 3/3] station, eapol: Set up eap-tls-common for session caching
Date: Thu, 17 Nov 2022 10:22:23 -0600 [thread overview]
Message-ID: <07fa9887-2391-9471-e37a-4fab1d2067fe@gmail.com> (raw)
In-Reply-To: <20221117135610.1162965-3-andrew.zaborowski@intel.com>
Hi Andrew,
On 11/17/22 07:56, Andrew Zaborowski wrote:
> Use eap_set_peer_id() to set a string identifying the TLS server,
> currently the hex-encoded SSID of the network, to be used as group name
> and primary key in the session cache l_settings object. Provide pointers
> to storage_eap_tls_cache_{load,sync} to eap-tls-common.c using
> eap_tls_set_session_cache_ops(). Listen to Known Network removed
> signals and call eap_tls_forget_peer() to have any session related to
> the network also dropped from the cache.
> ---
> src/eapol.c | 6 ++++++
> src/station.c | 28 ++++++++++++++++++++++++++++
> 2 files changed, 34 insertions(+)
>
<snip>
> @@ -5139,6 +5159,12 @@ static int station_init(void)
>
> watchlist_init(&event_watches, NULL);
>
> + eap_tls_set_session_cache_ops(storage_eap_tls_cache_load,
> + storage_eap_tls_cache_sync);
> + known_networks_watch = known_networks_watch_add(
> + station_known_networks_changed,
> + NULL, NULL);
This requires a dependency between station and known_networks module since the
watchlist is initialized in known_networks_init. I added this in a follow on
commit. Please have a look.
> +
> return 0;
> }
>
All three applied, thanks.
Regards,
-Denis
prev parent reply other threads:[~2022-11-17 16:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-17 13:56 [PATCH 1/3] storage: Refactor storage_tls_session_{load,sync} Andrew Zaborowski
2022-11-17 13:56 ` [PATCH 2/3] eap-tls: Add session caching Andrew Zaborowski
2022-11-17 13:56 ` [PATCH 3/3] station, eapol: Set up eap-tls-common for " Andrew Zaborowski
2022-11-17 16:22 ` Denis Kenzior [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=07fa9887-2391-9471-e37a-4fab1d2067fe@gmail.com \
--to=denkenz@gmail.com \
--cc=andrew.zaborowski@intel.com \
--cc=iwd@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.