Include jeanmswe...@gmail.com please
Sent from my iPad
Withdrawal of OpenSSL 3.0.6 and 1.1.1r
We have received a report of a significant regression in the latest 3.0.6 and 1.1.1r versions. The regression is not thought to have security consequences. While the regression is further investigated we have taken the decision to withdraw the 3.0.6 and 1.1.1r versions and instead recommend that users remain on the previous 3.0.5 and 1.1.1q versions for now. We will issue a new plan for the release of 3.0.7 and 1.1.1s soon. Yours The OpenSSL Project Team OpenPGP_0xD9C4D26D0E604491.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
Urlaub
Sehr geehrte Damen und Herren vom 8. Oktober bis und mit dem 18. Oktober bin ich im Urlaub. eMails werden nur sehr spärlich gelesen und nur in dringenden Fällen beantwortet freundliche Grüsse Silvan Scherrer
PBKDF2 & HMAC-SHA1-128 Functions
What OpenSSL functions to use in "Visual Studio 2022" to create a C++ program:: PSK = PBKDF2(Passphrase, SSID, 4096) PMK = PBKDF2(HMAC−SHA1, PSK, SSID, 4096, 256) PMKID = HMAC-SHA1-128(PMK,"PMK Name" | MAC_AP | MAC_STA) Sample test data for PSK (Pre-Shared Key) Network SSID: linksys54gh WPA passphrase: radiustest PSK = 9e9988bde2cba74395c0289ffda07bc41ffa889a3309237a2240c934bcdc7ddb (Result) See WPA key calculation in the link here Caster
Re: CMAC not working
On Wed, 2022-10-12 at 11:02 +0200, Tomas Mraz wrote: > On Tue, 2022-10-11 at 10:50 +, Fernando Elena Benavente wrote: > > Hi guys, Im triying to use the EVP_MAC OpenSSL API with the > > CMAC_AES256, I have been using some testing vectors I found on > > github, but seems they doesn’t work on the CMAC of OpenSSl, as the > > expected output of the test vectors are different from the OpenSSL > > CMAC output. > > > > I attach a screenshot of the test vectors we are using, and how we > > are introducing it on our key and plaintext variables, the CMAC > > code > > is the demo code on OpenSSL github. > > > > It is better not to use screenshots if possible and rather do > copy to save mailbox space of all the recipients. > > Our demo is actually incorrect because the cipher name used should be > 'AES-256-CBC' to produce a proper CMAC. Ahem... I am actually wrong, the demo is right although somewhat misleading, because "aes256" (which is in the demo) is an alias for "AES-256-CBC". Looking at the screenshots - you cannot use the hexadecimal value of the input directly in the data[] as you do. You need to initialize the data[] as an array similarly to how key is initialized. -- Tomáš Mráz, OpenSSL
Re: CMAC not working
On Tue, 2022-10-11 at 10:50 +, Fernando Elena Benavente wrote: > Hi guys, Im triying to use the EVP_MAC OpenSSL API with the > CMAC_AES256, I have been using some testing vectors I found on > github, but seems they doesn’t work on the CMAC of OpenSSl, as the > expected output of the test vectors are different from the OpenSSL > CMAC output. > > I attach a screenshot of the test vectors we are using, and how we > are introducing it on our key and plaintext variables, the CMAC code > is the demo code on OpenSSL github. > It is better not to use screenshots if possible and rather do copy to save mailbox space of all the recipients. Our demo is actually incorrect because the cipher name used should be 'AES-256-CBC' to produce a proper CMAC. -- Tomáš Mráz, OpenSSL