[openbeos] string.h and security
- From: Isaac Yonemoto <ityonemo@xxxxxxxxxxxx>
- Date: Fri, 11 Jan 2002 08:54:42 -0600 (CST)
Over winter break, I heard from someone that memcpy and other
memory-copying functions had security issues -- is anyone else aware of
this, and are we using posix code which is architecturally secure/based on
the secure versions? Since BeOS/NewOS isn't "really" a *nix, is it prone
to the same problems?
Just curious
Isaac
> >I am doing the posix library for openbeos.
> >I am almost finished the memory.h, string.h
> >list (tip of the iceburg).
Other related posts:
