Displaying 5 results from an estimated 5 matches for "interlocutor".
Did you mean:
interlocutors
2015 Jun 12
2
[Bug 2302] with DH-GEX, ssh (and sshd) should not fall back to unconfigured DH groups or at least document this behaviour and use a stronger group
On Fri 2015-06-12 01:52:54 -0400, Mark D. Baushke wrote:
> I have communicated with Allen Roginsky on this topic and I have been given permission to post his response.
>
> In this message below, the 'vendor' was Darren Tucker's generated prime
> that used a generator value of 5.
>
> -- Mark
>
> From: "Roginsky, Allen" <allen.roginsky at
2015 Jun 26
3
[LLVMdev] C as used/implemented in practice: analysis of responses
...ot;The situation has not gotten friendlier to old-school pointer
manipulations since https://lwn.net/Articles/278137/ was written in
2008. [This is a case where GCC optimised away a comparison
involving an out-of-bounds pointer] The pattern could still be found
in code exposed to malicious interlocutors in 2013:
https://access.redhat.com/security/cve/CVE-2013-5607"
- "Pretty sure this one I've seen buggy code optimised away by real
compilers."
Here the prevalence of transiently out-of-bounds pointer values in
real code suggests it's worth seriously asking the cost of...
2015 Jun 30
8
[LLVMdev] C as used/implemented in practice: analysis of responses
...ation has not gotten friendlier to old-school pointer
> manipulations since https://lwn.net/Articles/278137/ was written in
> 2008. [This is a case where GCC optimised away a comparison
> involving an out-of-bounds pointer] The pattern could still be found
> in code exposed to malicious interlocutors in 2013:
> https://access.redhat.com/security/cve/CVE-2013-5607 "
>
> - "Pretty sure this one I've seen buggy code optimised away by real
> compilers."
>
> Here the prevalence of transiently out-of-bounds pointer values in
> real code suggests it's wor...
2015 Jul 01
2
[LLVMdev] C as used/implemented in practice: analysis of responses
...ld-school pointer
> >> manipulations since https://lwn.net/Articles/278137/ was written in
> >> 2008. [This is a case where GCC optimised away a comparison
> >> involving an out-of-bounds pointer] The pattern could still be found
> >> in code exposed to malicious interlocutors in 2013:
> >> https://access.redhat.com/security/cve/CVE-2013-5607 "
> >>
> >> - "Pretty sure this one I've seen buggy code optimised away by real
> >> compilers."
> >>
> >> Here the prevalence of transiently out-of-bounds po...
2015 Jun 27
2
[LLVMdev] C as used/implemented in practice: analysis of responses
...ndlier to old-school pointer
>> manipulations since https://lwn.net/Articles/278137/ was written in
>> 2008. [This is a case where GCC optimised away a comparison
>> involving an out-of-bounds pointer] The pattern could still be found
>> in code exposed to malicious interlocutors in 2013:
>> https://access.redhat.com/security/cve/CVE-2013-5607"
>>
>> - "Pretty sure this one I've seen buggy code optimised away by real
>> compilers."
>>
>> Here the prevalence of transiently out-of-bounds pointer values in
>> re...