From: marcov@stack.nl   
      
   On 2005-05-29, Markus Humm  wrote:   
   > [snip]   
   >>   
   >> P.s. nobody should use C char *'s for DLL use anyway, they are a security   
   >> hazard. The new C standards rewrite all routines that rely on zero   
   >> terminated strings to handle an extra bound.   
   >>   
   > Could you tell me more about this?   
   > If I use a pchar I always have to supply another valiable which states   
      
   > how long the pchar is actually?   
      
   Yes, more or less. Or actually more a high-bound. Since what if I   
   maliciously passed a pchar without #0 ? The routine would search the whole   
   4GB virtual space. If I could get it to write to such pchar, I might be able   
   to overwrite a stack.   
      
   > Is there any document about this?   
      
   A lot of C and Unix/Posix faqs. Security related info. Rationale for the 'n'   
   functions   
   in POSIX (and maybe C) standards.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)