How security holes happen
88888 Dihedral
dihedral88888 at gmail.com
Wed Mar 5 21:39:49 EST 2014
On Wednesday, March 5, 2014 8:52:31 AM UTC+8, Andrew Cooper wrote:
> On 03/03/2014 22:19, Cameron Simpson wrote:
>
> > On 03Mar2014 09:17, Neal Becker <ndbecker2 at gmail.com> wrote:
>
> >> Charles R Harris <charlesr.harris at gmail.com> Wrote in message:
>
> >>>
>
> >>
>
> >> Imo the lesson here is never write in low level c. Use modern
>
> >> languages with well designed exception handling.
>
> >
>
> > What, and rely on someone else's low level C?
>
> >
>
>
>
> Why is C the lowest denominator?
>
>
>
> Even with correctly written C and assembly, how can you be sure that
>
> your processor is executing the SYSRET instruction safely?
>
> (CVE-2012-0217 for anyone interested)
>
>
>
> ~Andrew
It is not difficult to write C with
mixed assembly codes for different
CPUs.
#ifdef ASM
/* asm follows */
....
#ifdef CPUTYPES
/* insert CPU ASMS for different
CPUs carefully here */
More information about the Python-list
mailing list