LS nightly stops working in Mavericks Preview 8

[soleares]

After upgrading to Mavericks Preview 8, the latest Little Snitch nightly stopped working.

It shows the following error:

Little Snitch version mismatch detected.

After installation it showed the following error:

System extension excluded
The system extension "Library/Extensions/LittleSnitch.kext" is in the kext exclude list.
The kext(s) will not be loaded. Contact vendor to resolve this issue.

[udo]

I had the same problem after updating to Preview 8, looks like Apple is locking down OS X even more tightly now. However, they still allow us to edit the system config files, so if you're feeling adventurous log on to the Terminal as root and go to /System/Library/Extensions/AppleKextExcludeList.kext/

...then open the Info.plist file and delete the entry pertaining to LittleSnitch. Restart the computer and LS should start up normally. Chances are you'll have to do this after each system update from now on though.

[soleares]

Thanks! Works fine now.

[mikeyusc]

They (Apple) have excluded the current version (4041) & anything earlier.. once the nightly build comes out tonight, it should work fine.

[lilwaynesnitch]

Not to be a Poindexter, but maybe Apple changed something in their code that breaks something in Lil Snitch? Or maybe something in Lil Snitch breaks something in DP8? Why would they block a nightly build? Just to do it? Just to make Obdev coders update their software?

[speedyb]

I just took a look in de KextExclude file and found that the reason I am using LittleSnitch is also being blocked.
I was using NetBarrier from Intego, but that software is not able to handle multi homed configurations. LittleSnitch is.
It seams to me that all security related software (VirusScanners and Firewalls) are now being disabled..

I don't feel comfortable to modify the Info.plist file just for the reason also given by lilwaynesnitch..

Just my 2 cents

[bojan23]

Just reinstall the last build!

[lilwaynesnitch]

Reinstalled 4041 and get the same error.

[DeinGott]

I did have problems updating betas, if LS was running. Maybe thats related to the point why they disabled it.

[udo]

Obviously, modifying the pList file isn't for everyone. But it does work and, at least on my system, there are no adverse effects between Mavericks and Little Snitch (nightly). If you don't feel comfortable deleting the entry from the pList outright, you might want to just change the name by one letter - that way you can always undo the change later. But this file will be overwritten at next system update anyway so I wouldn't worry about it too much.

[DeinGott]

The Plist change is not working, if you have signure check enabled (Preferences -> Security -> allow only Appstore and verified Devs). The Kext will not load, if something is changed. So it only works, if your system is "unsecure".

Does anyone try to just change the 4041 to lets say 4040? so the current version should not be blocked.

[udo]

I didn't consider that people using a dev preview might have signature checking enabled (I kinda assumed no overlap between those groups)

Changing the version number in the pList file probably won't work in that case either, as the pList file's hash is most likely part of the package's signature. I guess you could try editing Little Snitch's internal version number to 4042 instead but that'd probably mess with its update mechanism.

[baby]

The Plist change is not working, if you have signure check enabled (Preferences -> Security -> allow only Appstore and verified Devs). The Kext will not load, if something is changed. So it only works, if your system is "unsecure".

It works fine for me even with that security setting. As mentioned in a couple of the earlier posts by users, you want to reinstall Little Snitch (after deleting the entry in the Plist file — this wasn't clear in those posts).

[cvanmeer]

They have removed the nightly builds from the Downloads page

[lilwaynesnitch]

Guessing that they don't want to keep a nightly posted that is essentially broken (for its general purpose of maintaining compatibility with Mavericks). Let's hope they post a new one soon that resolves our issue. Or perhaps (fingers crossed), they are putting the finishing touches on final 3.2?.