Landon Fuller

@landonfuller There are no quotes about it. Code injection is a security vulnerability and had been used by malware in the past.

@launchz Whatever the malware used to acquire task port rights was the vulnerability.

@landonfuller Distinguishing between a legitimate use and an attacker isn't always possible with technology.

@launchz In which case you have to decide whether you believe the solution lies in paternalism or individual empowerment.

@landonfuller @launchz Is “individual empowerment” another way of saying “caveat emptor”?

@landonfuller @launchz Whatever happened to “personal responsibility”, anyway? Computers are *supposed* to be dangerous!

@optshiftk @launchz A chainsaw isn't supposed to be dangerous, but it's supposed to be able to cut down trees.

@landonfuller what is wrong with turning it off because you want to use these tools?

@mxswd On top of which, why should it be necessary to disable ALL security to have any degree of granular control?

@landonfuller though if you did want to do this properly you could put attach to that process into a kext and sign it?

@mxswd kext signing requires individual use-case approval from Apple to add the requisite 'kext' bit to your certificate.

@landonfuller that sucks. Can you add signing authorities manually? I'm not sure, I've never checked.

@mxswd Nope :/ It's hard-coded to require Apple CA as an anchor :( http://xref.plausible.coop/source/xref/macosx-10.10.1/kext_tools-384.1.4/security.c#1238 …

@landonfuller ugh. Ok. Well last I recalled there is a boot arg for just disabling kext signing. I'm out of ideas for now.

@ZenSaiyuki That's the end-game, yes. Accepting the loss of data (platform apps, iCloud), media (iTunes), books (iBooks) and jumping ship.