From mboxrd@z Thu Jan 1 00:00:00 1970 From: Antonio Quartulli Date: Wed, 27 Nov 2013 07:48:47 +0100 Subject: [ath9k-devel] GTK/PTK problem - key.c magic-bitshift In-Reply-To: References: <20131117110802.GD1381@neomailbox.net> <20131118215127.GC1443@open-mesh.com> <20131122091848.GF1443@open-mesh.com> Message-ID: <529595CF.3060904@open-mesh.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: ath9k-devel@lists.ath9k.org -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 22/11/13 10:42, Adrian Chadd wrote: (sorry for re-sending but my mail server did not want to deliver to all..) Adrian, sorry for the delay. You are right. With TKIP we have different keys..but at this point how can I detect a PTK-TX corruption? It may be the case that received frames are decrypted properly (PTK-RX is ok)...but still..the PTX-TX may have been corrupted. Right? When should I trigger the periodic worker in this case? - -- Antonio Quartulli -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBCAAGBQJSlZXPAAoJEADl0hg6qKeOYbYQAKZcAR0yLd7NJcmc30/ekcM5 pfkT3wY7fnkWz9Fq2M7OgEprFX91cz44qrokh+wNikFHZlDg3qIAv3Ti+FbbHiJ+ nTHu/2INGGD1Me27e9Ts6AWLALHcQsumJhzi96uRPEna0gr4oJeHWId84mT5tUDh rO5yCFhiZiSMmnqvlG9PxIifXJo9QgQpjRy4tSRkDu9dIWrv+1F0+KLwcFGhpLCV RUR8KpXqFHFMgrMuRaiFO23U1T1yZnllEiA1eQO7urMhlBnEJ0yODHj5VDcivEWe obFzJYxG/aH+51m0y1KOcWm5C/fyvMUBitU+kwfV5SByRN4Tr50DdBQ/DCI4qR2R 7iJ/gTJcampKCRDTNUiRaUY2KYIxSEumAbgr5sRbFq2udUl8PJbEM/nhmdlMyG8N HYPN9cgzeANvvvo30fpCyJukWCp8nefhtq3FYSeQpm/16rbNak3vffzgTXcOtAVJ CHaBHcYweofmzeWtFOPTFEuLkCKA/ZZ0LzP+pv3Zmfe5Whb3LfSEcQRuwfhexb/6 SsG3omRYqn1rDxlV9MAajTv22KhJ26QIy9jp9qQDUOib4r/sleOcuVOc4CLxuaoc DSAibUDZaMFPWnn7XtSbtDdZtDVc4XZ33xyJ9ad1IyvIh6M8YVgA2QCA2DJ5Zk9R 0uwdqKx4VM7aRgfFXd8h =NqhI -----END PGP SIGNATURE-----