| |||||||||||||
Kernel.org's road to recoveryKernel.org's road to recoveryPosted Oct 7, 2011 18:59 UTC (Fri) by malor (subscriber, #2973)In reply to: Kernel.org's road to recovery by vonbrand Parent article: Kernel.org's road to recovery And, again: all that is being asked is to stop lying. You don't have to do anything else to make us happy, just stop lying.
(Log in to post comments)
Kernel.org's road to recovery Posted Oct 7, 2011 19:31 UTC (Fri) by dlang (✭ supporter ✭, #313) [Link]
it would be lying if they said in the changelog "this changelog has no security impact" when they know that it does.
not saying that it has a security impact is not direct lying. at most it's lying by implication or by omissions, but to make a case that it's lying by these criteria you would need to establish that it's a normal thing to have such data in there to start with, and it's not.
Kernel.org's road to recovery Posted Oct 7, 2011 20:34 UTC (Fri) by malor (subscriber, #2973) [Link]
Knowingly hiding information for your own benefit (avoiding embarrassment and fewer people using your product), and to the detriment of the people you're hiding the information from, is lying.
You can fucking dance around that all you want, trying to justify behavior that simply can't be justified, but it remains true. It is unethical behavior, probably the second-worst thing you can do as a coder.
Kernel.org's road to recovery Posted Oct 7, 2011 21:49 UTC (Fri) by PaXTeam (subscriber, #24616) [Link]
> you would need to establish that it's a normal thing to have such data
> in there to start with, and it's not.
as a security professional you must know cve.mitre.org and all the links they have to various resources that disclose this kind of information. you were saying...?
|
|||||||||||||