-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Saved Application State issue #10
Comments
What Application are you trying to restart? Maybe that Application is in violation with the "missing __PAGEZERO" segment policy. Did the /var/log/system.log have any output from SUIDGuard? |
Various. Cisco AnyConnect VPN client, latest public stable of Google Chrome, latest public stable of Word (Office 2011) Wasn't able to grab the logs as instructions were given to roll-back to achieve usability. Shall replicate and grep the logs. |
system.log extract from a 10.9.5 machine. The device was re-opening only Cisco AnyConnect 4.1.x from what I understand. It didn't even load the dock, no mouse/keyboard as mentioned. Fix was to remove the kext.
|
Oh I see. You are using 10.9.x - then it is no wonder that SUIDGuard does not work or crash. The installer that we ship does only work on 10.10 for a reason, because 10.10 is the only official supported one. 10.9 is incompatible to SUIDGuard and should cause kernel panics if you try to use it. The mac framework hooks in 10.9 lack the features required for the DYLD_ protection. |
The device logs I could get are 10.9.5, but this happens on 10.10.x too just waiting for an EUD to come in so I can get the 1st line chaps at the client to pull the logs off. But OK, understood about it not patching 10.9.5. I missed that point for SUIDGuard. |
Seeing an oddity in 10.9.5/10.10.x with 1.0.6.
If ~/Library/Preferences/com.apple.loginwindow.* dictates an application should be re-opened (not confused with SysPref>Users>User>LoginItems, which will open an app, but doesn't care about its saved-state) after restart, then that app loading will crash the entire system (hard, no mouse/keyboard - hard reset required).
Clearing ~/Library/Preferences/com.apple.loginwindow.* and ~/Library/Saved\ Application\ State after kext installation, but prior to restart, also doesn't work - as opening an app to resume it, still crashes it out.
Amused that the app state is persistent beyond ~/Library/Saved\ Application\ State and also that the kext is doing this (yes, booting from recovery or a bootable USB and then removing the kext and going back into the user's env, works just fine).
The text was updated successfully, but these errors were encountered: