From: Johannes Berg Subject: Re: [PATCH 7/7] mac80211: Switch to new AEAD interface Date: Mon, 01 Jun 2015 15:42:41 +0200 Message-ID: <1433166161.3505.7.camel@sipsolutions.net> References: <20150521103938.GA23035@gondor.apana.org.au> <1432207249.2343.9.camel@sipsolutions.net> <1706098.2opyZ2hT8S@tachyon.chronox.de> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Cc: Herbert Xu , Linux Crypto Mailing List , netdev@vger.kernel.org, "David S. Miller" , Marcel Holtmann , Steffen Klassert To: Stephan Mueller Return-path: In-Reply-To: <1706098.2opyZ2hT8S@tachyon.chronox.de> Sender: netdev-owner@vger.kernel.org List-Id: linux-crypto.vger.kernel.org On Mon, 2015-06-01 at 15:21 +0200, Stephan Mueller wrote: > Just a short question on ieee80211_aes_ccm_encrypt, ieee80211_aes_ccm_decrypt, > ieee80211_aes_gcm_encrypt, ieee80211_aes_gcm_decrypt, ieee80211_aes_gmac: can > the aad parameter of these functions be zero? What do you mean by "zero"? The pointer itself can clearly never be NULL. The contents, now, that's a more interesting question. I believe it can never be all zeroes, since association request frames are not encrypted/protected and thus at least one byte in here must be non-zero. The MAC addresses are also very likely non-zero, but technically 00:00:00:00:00:00 is a valid MAC address I believe. johannes