El Capitan compatibility

[andrew-hill]

As I'm sure you're aware, public & developer betas are out for OS X 10.11 El Capitan.

During installation (pubic beta), Asepsis was explicitly noted as being incompatible and disabled by OS X.

Are you planning on releasing a version compatible with El Capitan, and if so is there a (rough) timeline?

[darwin]

AFAIK Asepsis under El Capitan with System Integrity Protection enabled is not possible.

I'm going to stop developing Asepsis and supporting it under El Capitan.

[andrew-hill]

Interesting, I wasn't aware of this change, so good to know...

A bit of light reading for anyone else who comes across this and doesn't know about System Integrity Protection: Wikipedia and Apple El Capitan changes.

Apparently you can disable System Integrity Protection, but its not a simple setting in System Preferences, so presents a pretty big barrier for Asepsis and a lot of other utilities like it that inject/override/etc.

It'll be interesting to see if Apple allow specific exceptions to it, without entirely disabling System Integrity Protection... I'll certainly be submitting some feedback about this, and would encourage others to do so as well. My guess is they'd go for something like 'signed extensions' for this, rather than arbitrarily disabling specific aspects of SIP.

[Joshfindit]

I've filed a 'bug' through the Feedback Assistant, and suggest others do the same.
And yes, I'm aware of the bias against telling Apple what we actually want; imho the vote should be counted regardless.

[Noctem]

I was (naïvely) hoping that Apple would finally at least provide an option in vanilla El Capitan to cease .DS_Store pollution. I guess I'll just keep waiting.

[DanielSmedegaardBuus]

You say that "Asepsis under El Capitan with System Integrity Protection enabled is not possible". This feature can be disabled in Recovery Mode, though. Which I already did to make XtraFinder work :D Would it be possible to do the same with Asepsis? Is it safe to just try to install the latest version with SIP turned off?

[D-an-W]

I just tried...

"This version of Asepsis is only supported under OS X 10.8, 10.9 or 10.10.'

[darwin]

@DanielSmedegaardBuus I guess Asepsis works with SIP disabled under El Capitan. But I haven't tested it myself. I can prepare a new build with OS requirement check disabled.

[D-an-W]

Please do!

[darwin]

http://downloads.binaryage.com/Asepsis-1.5.2.dmg

before installing please run this command in Terminal.app:

touch ~/.no-asepsis-os-restriction

I have just briefly tested it here on my El Capitan B6 system and Asepsis seems to work. The only problem is that some apps that link against DesktopServicesPriv.framework will be treated as newly downloaded from the internet. I had to click through all the warning dialogs again.

[D-an-W]

Everything other than the update checker seems to work here, assuming there isn't going to be another update can this be disabled to prevent the errors?

[darwin]

You have two options:

1. This will just suppress update errors, but updater will run:

touch ~/.asepsis-suppress-update-errors

2. This should uninstall updater component:

asepsisctl uninstall_updater

[DanielSmedegaardBuus]

Awesome! Works :D Thank you so much :) OS X had already started cluttering my project directories, was so sad to not have Asepsis around anymore to prevent that :) 👍

[Joshfindit]

I had to click through all the warning dialogs again.

There is some talk around this that's not related to Asepsis: http://forums.macrumors.com/threads/getting-lots-of-the-first-time-warning-at-system-startup-after-upgraded-to-dp6.1905498/ - Some people there are having success with enabling auto-login. Maybe related?

[MichaelZaporozhets]

Even after running the commands:
touch ~/.no-asepsis-os-restriction & touch ~/.asepsis-suppress-update-errors
the installer is still returning an install error ( using your 1.5.2 installer )

Anything else I can do?

[darwin]

@MichaelZaporozhets I'm sorry, I have no idea