Re: [PATCH] Secure programming additions to HACKING

Quoting Karl Fogel (kfogel@newton.ch.collab.net):
> Before applying this, it would be nice to identify some security
> boundaries already present in Subversion, and note their constraints
> in the code. I think that would give us a better idea of how to write
> security guidelines in HACKING.

That's fair. My concern is that the code has existed for almost two
years and this hasn't happened yet. 1.0 is getting closer. Unless
concentrated effort goes into catching these mistakes, end users are
going to suffer, eventually.
 
> It would be best to avoid saying things that everyone already knows
> (for loose values of "everyone", of course), such as don't use strcat
> and strcpy, don't accept arbitrary length input into fixed-length
> arrays, etc. :-)

In my experience, a programmer who knows this is an exception. Things
are getting better, but much too slowly. I would agree that HACKING
should be as specific to Subversion as possible.

-- 
I prefer the dark of the night, after midnight and before four-thirty,
when it's more bare, more hollow.                  http://a.area51.dk/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org