search for: nolegaci

Displaying 4 results from an estimated 4 matches for "nolegaci".

Did you mean: nolegacy
2015 Jul 05
3
Different PRF with --disable-legacy-protocol?
Hi everybody. I'm struggling with setting up an SPTPS connection between two of my machines. I attached the patch that I used to analyze this. Apparently different keys are derived depending on the crypto backend. Is this intentional? Linking to openssl results in char key[] = { 0xb2, 0x9d, 0x8d, 0x24, 0x91, 0x04, 0xaf, 0x25, 0x3f, 0x10, 0x34, 0x9d, 0xc7, 0x73, 0x8c, 0xe1, 0x24, 0x32,
2013 Sep 19
0
[LLVMdev] Proposal to improve vzeroupper optimization strategy
Great idea. I reported on this problem before and glad to see someone trying to tackle this. cheers. ________________________________________ From: llvmdev-bounces at cs.uiuc.edu [llvmdev-bounces at cs.uiuc.edu] on behalf of Gao, Yunzhong [yunzhong_gao at playstation.sony.com] Sent: Thursday, September 19, 2013 11:53 AM To: llvmdev at cs.uiuc.edu Subject: [LLVMdev] Proposal to improve
2013 Sep 19
5
[LLVMdev] Proposal to improve vzeroupper optimization strategy
Hi all, I would like to make a proposal about changing the optimization strategy regarding when to insert a vzeroupper instruction in the x86 backend. Current implementation: vzeroupper is inserted to any functions that use AVX instructions. The insertion points are: 1) before a call instruction; 2) before a return instruction; Rationale: vzeroupper is an AVX instruction; it is inserted to
2015 Jul 05
0
Different PRF with --disable-legacy-protocol?
On Sun, Jul 05, 2015 at 09:02:55PM +0200, Benjamin Richter wrote: > I'm struggling with setting up an SPTPS connection between two of my > machines. I attached the patch that I used to analyze this. Apparently > different keys are derived depending on the crypto backend. Is this > intentional? No, this is not intentional, it's a bug in the hmac_sha512 implementation in