Unsigned (Legacy) Extensions in El Capitan?

So previously my Firewire-410 had quit on me after upgrading my system to El Capitan. The blue light kept blinking.

For whatever it is worth, I disabled SIP and got my Firewire-410 working. Solid blue light, recording, playback and everything else seemed just fine. M-Audio control panel, however, was still not working, which I disregarded.

BUT, today I started up my iMac (late 2011) the 410 is just not working, not even a blue light.

Just wanted to share with y'all.

-Y

Yidoman wrote:

For whatever it is worth, I disabled SIP and got my Firewire-410 working.

As I mentioned, for several reasons I personally think it is not a good idea to disable SIP. If it was me & I really needed to use the Firewire 410, what I would do instead is create a separate boot volume with Yosemite (or whatever other older OS that met my needs) on it, & boot into that whenever I needed to do anything with the 410.

Because the older OS X versions are not as secure as El Capitan, if at all practical I would disable all Internet access on that system.

But that is just me.

roncarfl wrote:

... I wonder why the concern is at a level that Apple would resort to such a sweeping change.

I think it is mostly in response to the ever increasing sophistication & seriousness of malware attacks. Once, we mostly just had to worry about hacker hobbyists that tried to break into systems for the challenge of seeing if they could do it, & later mostly about script kiddies who didn't pose much of a threat.

But now, we also have to consider well funded criminal organizations & government-sponsored hackers (including our own) looking for anything they can exploit. Unlike the hobbyists & script kiddies, they focus on "stealthy" attacks we are unlikely to notice, & have the resources to probe the OS itself for weaknesses. There is no denying they exist -- all you have to do is look at the long list of vulnerabilities that Apple has patched at Apple security updates - Apple Support. There is no reason to think that as the OS continues to get ever more complex only the white hats will find everything a remote attack can do before the black hats will -- including at least a few things "best practices" won't protect us from.

Of course, SIP can't protect us from everything -- in fact, by itself it offers very little that will protect user domain files -- but I am a firm believer in the value of the layered defense security strategy. SIP adds a new layer that if nothing else makes the damage privilege escalation attacks can do much less severe. That is reason enough for me to avoid disabling it whenever possible.

As always, YMMV.

you can find the latest solution in this facebook group:

M-Audio Firewire 410, 1814, Solo, Audiophile Users

Disabling Integrity Protection does not cause Capitan to load unsigned drivers. The bottom line is that Apple decided that fear of hackers was sufficient to arbitrarily transform thousands, millions, whatever of users' investment in hardware into bricks. That's really an incredibly ****** thing to do to people.