Re: cvs commit: src/crypto/openssh buffer.c

[Kip Macy <kmacy@xxxxxxxxxxx>]

I'm sure I'm preaching to the choir here, but after having seen numerous
projects slip because developers are creating new bugs at a rate only
slightly less than they're fixing old ones, I hope that we are able to
keep basic functionality more or less stable all the time. Not doing so
potentially diminishes the productivity of all developers.

If it ever does become an issue, we should set up some machines for 
committers to run a designated set of regression tests on before 
checking in. It isn't by chance that my group at NetApp has the lowest
escape rate (customer found bugs) and the least amount of schedule 
slippage.

Right now the number of committers is so small that it isn't likely to
be an issue. And yes - I can hear Matt saying "I think we have a 
volunteer". We shall see.

		-Kip



> Right now I'm not able to do much other than kill sshd, though
> I think by the end of the day we should be able to exec from commands.
> The last offer I got from an unnamed security company for a working
> example was starting to get close to 6 digits....
>
> I wonder if anyone will try to switch to DragonFly now that they need
> a security fix and RELENG_4 is very unstable. I cvsup'd a RELENG_4
> machine this morning and its already panic'd out.... Looks like even
> though were is the development stages DragonFly is remanning a lot
> more stable than FreeBSD's -Stable branch.
>
>
> -DR