iwd.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: James Prestwood <prestwoj@gmail.com>
To: iwd@lists.linux.dev
Cc: James Prestwood <prestwoj@gmail.com>
Subject: [PATCH 4/9] handshake: add event for rekey success
Date: Wed, 11 Jan 2023 12:15:38 -0800	[thread overview]
Message-ID: <20230111201543.397692-4-prestwoj@gmail.com> (raw)
In-Reply-To: <20230111201543.397692-1-prestwoj@gmail.com>

Rekeys for station mode don't need to know when complete since
there is nothing to do once done. AP mode on the other hand needs
to know if the rekey was successful in order to reset/set the next
rekey timer.
---
 src/handshake.h | 1 +
 src/station.c   | 1 +
 2 files changed, 2 insertions(+)

diff --git a/src/handshake.h b/src/handshake.h
index f2321634..863ffac7 100644
--- a/src/handshake.h
+++ b/src/handshake.h
@@ -60,6 +60,7 @@ enum handshake_event {
 	HANDSHAKE_EVENT_EAP_NOTIFY,
 	HANDSHAKE_EVENT_TRANSITION_DISABLE,
 	HANDSHAKE_EVENT_P2P_IP_REQUEST,
+	HANDSHAKE_EVENT_REKEY_COMPLETE,
 };
 
 typedef void (*handshake_event_func_t)(struct handshake_state *hs,
diff --git a/src/station.c b/src/station.c
index bad067c8..ad5ad724 100644
--- a/src/station.c
+++ b/src/station.c
@@ -1015,6 +1015,7 @@ static void station_handshake_event(struct handshake_state *hs,
 	case HANDSHAKE_EVENT_SETTING_KEYS_FAILED:
 	case HANDSHAKE_EVENT_EAP_NOTIFY:
 	case HANDSHAKE_EVENT_P2P_IP_REQUEST:
+	case HANDSHAKE_EVENT_REKEY_COMPLETE:
 		/*
 		 * currently we don't care about any other events. The
 		 * netdev_connect_cb will notify us when the connection is
-- 
2.34.3


  parent reply	other threads:[~2023-01-11 20:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-11 20:15 [PATCH 1/9] eapol: set secure on message 2/4 properly James Prestwood
2023-01-11 20:15 ` [PATCH 2/9] unit: update test-eapol with API change James Prestwood
2023-01-11 20:15 ` [PATCH 3/9] eapol: implement rekey support for authenticator James Prestwood
2023-01-11 20:15 ` James Prestwood [this message]
2023-01-11 22:30   ` [PATCH 4/9] handshake: add event for rekey success Denis Kenzior
2023-01-11 20:15 ` [PATCH 5/9] netdev: unset ptk_installed flag for TK James Prestwood
2023-01-11 20:15 ` [PATCH 6/9] netdev: support HANDSHAKE_EVENT_REKEY_COMPLETE James Prestwood
2023-01-11 20:15 ` [PATCH 7/9] eapol: relax secure bit check on 2/4 James Prestwood
2023-01-11 20:15 ` [PATCH 8/9] ap: support PTK rekeys James Prestwood
2023-01-11 20:15 ` [PATCH 9/9] doc: Document RekeyTimeout for AP profiles James Prestwood
2023-01-11 22:05 ` [PATCH 1/9] eapol: set secure on message 2/4 properly Denis Kenzior

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=20230111201543.397692-4-prestwoj@gmail.com \
    --to=prestwoj@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).