> Hmm.  Anyone for producing a "libcsafe" which doesn't include:
> 
> 	strcat
> 	strcpy
> 	sprintf
> 	gets
> 
> and other "unsafe", but traditional, interfaces, and then linking all
> setuid system programs against it instead of libc?

While i dunno about this, i do think that at the very least adding
reference-warning macros for those functions might be appropriate.



chris