On Thu, Dec 01, 2011 at 05:45:25PM +0000, David Laight wrote: > > > Anyway, here is a first cut on an "explicit_bzero" function > > > which doesn't get optimized away. I've put it to src/common > > > because the same thing makes sense in the kernel too. > > > Comments? > > > > Just make it an alias on memset. That's good enough. I think calling it > > something like "secure_memset" or "safe_memset" is better, but opinions > > might differ.
That's a start, but I'm not convinced it's good enough in the long term. > I'm not sure that 'secure' or 'safe' are good prefixes for any > function name. You need to say WHY is is better. indeed. -- David A. Holland dholl...@netbsd.org
