LSS: Kernel security subsystem reports
Posted Sep 29, 2012 10:09 UTC (Sat) by nix
In reply to: LSS: Kernel security subsystem reports
Parent article: LSS: Kernel security subsystem reports
Yes, I am aware of its codomain/subdomain history.
I wasn't aware that you were calling AppArmor 'new' and claiming precedence over it because it changed its name
. Sheesh. Yes, yes, you were first, well done, as long as you ignore another program which had the temerity to change its name at some point in its history. That changes everything, I'm sure. Semantic quibbling.
A couple lines of perl operating effectively no differently than audit2allow. This is not real learning. It provides no predictive power
Yeah. That's all that it ever did. It never claimed to offer 'predictive power': it's an easy way to put together an initial set of rules based on what programs are actually doing. Providing proper predictive power of course involves automatically analyzing the programs in question and figuring out what they do, which is apt to slam straight into Rice's theorem and even if you avoid that by approximation is going to be terrifyingly unpleasant to write.
you're a hopeless cause: a glib peddler of intellectual dishonesty, arguing for the sake of semantic argument
What a repulsive person you are. Do you normally
respond to factual correction with semantic quibbling and vile personal attacks accusing me of precisely what you yourself are doing? (Personal attacks which you'll note I cannot defend myself against, since if your assertions are true nothing I say is worth anything.)
Actually, I've seen you argue here before. Yes, you do revert to vile personal attacks whenever you're losing an argument.
to post comments)