Theodore Tso wrote:That's fallacious. Assuming that you have good programmers, and you do, it's of very low cost the act of identifying what *is likely to be* a security bug. In most cases, they are easy to spot. And, hey, we are not asking for an absurd amount of care. You must not pay $200 /hour for someone to review your software. All I, personally, ask for is that the basic attention is given. With this simple act, I'm sure you would cover the majority of the bugs. So, only those willing to pay have the right of respect? Because, you see, this is rather a matter of respect with those who choose to use your solution. And, no, the "free will" argument does not qualify herein. My mother is not aware of your absurd acts. > 2.6.18 in Fall 2006, and their next snapshot will be sometime two I don't follow what you have just said. What is the problem with "versioning" and the strictness of its relation to bugs, security or not? I think, CVE registration or the alike would be too much for what I call "act of decency". A single parenthesis note on the bug itself would be of great help and of small effort. --t --
| Scott Preece | Re: Linux Foundation Technical Advisory Board Elections |
| Luis R. Rodriguez | Re: [Announce] Linux-tiny project revival |
| Andrew Morton | 2.6.23-rc1-mm2 |
| Dave Hansen | [PATCH 02/24] rearrange may_open() to be r/o friendly |
git: | |
| David Miller | [GIT]: Networking |
| David Miller | Re: [BUG] New Kernel Bugs |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
