Q: Will Authentec Truesuite be updated for 10.9?

Here is what I was about to write:

I am trying to follow the rule "if it is possible do not use x.0 versions on production systems" .

It looks like this has saved me some "inconveniences".

I did an 10.8 to 10.9.1 update today without removing the installed Truesuite 5.5.0.5 and without removing the scanner. Update succeded, manual login worked without problem. Fingerprint scanner is not working but Truesuite software is. Switched off "Fingerprint Log On" according to http://support.apple.com/kb/TS5338. Did not run the deinstaller and will wait untill it is save to deinstall. Have to thank all of you that did the investigation and obviously convinced Apple to modify the update process. Did also give Apple feedback to add support in 10.9.x

then - I accidently touched the scanner with a finger that had been configured with the System Action "lock" - and that exactly happened leaving me with a gray screen, no login dialog to use and obviously no fingerprint working for login anyway!

Good to have ssh so I was able to login from remote and reboot the system.

Now I went back to the TS PrefPane and deactivated every option there and removed the scanner from the system. I will eventualy remove the /var/auth.db and will comment on the KB-Article...

Did anyone managed to deinstall the suite under 10.9.x?

...waiting for Apple to support the beast...

Has been re-released:

http://support.apple.com/kb/TS5338?viewlocale=en_US

Yeah, it's really infuriating that I purchased this solution, it worked fine for years, then Apple suddenly acquires the company and abruptly shuts down all development of the supporting software.  It's crap like this that is really destroying Mac OS X's reputation as a competitive and modern desktop OS (I won't even mention my sentiments about what they did to server).

I realize that all the shiny iOS toys are the new darling revenue generators for Apple, but lets be honest, there aren't any marvelous new developments happening there either. 

Keep it up Apple, you're about to become as relevant as Blackberry in the enterprise mobile space and Microsoft in the consumer space.

can somebody please post original authentec dm, its not availbale in the archive anymore!

I can confirm that TrueSuite doesn *not* work with OS/X 10.9 Mavericks, but did under Mountain Lion 10.8. Kind of seems silly that it breaks the next operating revision onward.

This is starting to hurt too - I'm a security professional by trade, and as a consultant we had to de-certify several hundred Macs to be out of security compliance because the OS upgrade makes them less secure with the fingerprint reader capability removed. Management's not willing to buy new products either to attach to them even if Apple came out with one - just too much expense for something that worked.

Likely these will bre replaced with something non-Apple now, also stinky.

Between this & the USB & multi-monitor issues, we really need some fixes here, Apple.

+1

Apple is loosing another customer here.

+1

Apple is loosing another customer here.

Please take the bullet pieces out from my Mac OS!!!!

I had a similar infinite reboot cycle after my son downloaded and installed Protemac logonkey.  He misunderstood what it did, but that became irrelevant because the iMac failed to reboot from that point on.

The apple log would appear, then the spinner would cycle for a few minutes before freezing.

To fix, I tried rebooting in safe mode, verbose, single user etc but it made no difference.  The safe mode verbose logging would echo the actions being taken, but at a point in the process the screen would clear to plain black, with just a single white cursor square in the top left hand corner of the screen.

Rebooting into recovery mode, and using terminal (thank goodness for that), I removed the .app bundle, and some cache files (/Library/LaunchAgents etc) and preferences using  rm Library/Preferences/com.apple.security.plist, but no joy.  I also did all the available disk checks, and a few (irrelevant) errors got fixed.

Looking at the logs it looked like some kind of authentication failure, most probably to do with the logonkey installation.  After many hours trying to find out how to uninstall the offending plugins, trying just to "unplug" the authentication itself, then wondering if it would end in salvaging what I could from the hard drive, wiping the disk and perhaps an expensive Genius bar visit, I came upon this post.  And this worked (as per above):

1) Boot into single user mode (CMD-S while rebooting)

2) Mount the harddrive, type "/sbin/mount -uw /"

3) Type "rm /var/db/auth.db"

4) type "reboot"

Never has a set of four commands been so much of a relief!

I am posting my logonkey specific logs here in case anyone else gets the same problem, or similar.  iMac running version OSX 10.9.5.

In /Volumes/Macintosh HD/private/var/log/system.log :

Nov 22 10:13:55 the-imac.home UserEventAgent[325]: Failed to copy info dictionary for bundle /System/Library/UserEventPlugins/alfUIplugin.plugin

Nov 22 10:13:55 the-imac.home com.apple.authd[71]: engine[321]: evaluate returned -60008 returning errAuthorizationInternal

Nov 22 10:13:55 the-imac.home loginwindow[321]: Login Window - Returned from Security Agent

Nov 22 10:13:55 the-imac com.apple.launchd[1] (com.apple.security.agentMain.00000000-0000-0000-0000-0000000186B4[331]): Job appears to have crashed: Trace/BPT trap: 5

Nov 22 10:13:55 the-imac.home loginwindow[321]: ERROR | -[LoginApp performAuthPluginRequest:] | AuthorizationRef doesn't have a username. Exiting.

Nov 22 10:13:55 the-imac.home WindowServer[322]: CGXRestartSessionWorkspace: session workspace exited for session 256 (on console)

Thread dump

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread

0   com.apple.CoreFoundation      0x000000010392f4c4 CFRelease + 724

1   com.apple.securityAgentPlugin.NameAndPassword0x000000010cbf595e TrialProtector::getInstallDate(guid_t) const + 94

2   com.apple.securityAgentPlugin.NameAndPassword0x000000010cbf5c49 TrialProtector::trialDaysLeft(int) const + 85

3   com.apple.securityAgentPlugin.NameAndPassword0x000000010cbf4b86 -[LogonProtector daysToTrialEnded] + 335

4   com.apple.securityAgentPlugin.NameAndPassword0x000000010cbf3163 -[EXNameAndPassword awakeFromNib] + 381

5   com.apple.AppKit              0x0000000102623b3f -[NSIBObjectData nibInstantiateWithOwner:topLevelObjects:] + 1223

6   com.apple.AppKit              0x00000001026185ce loadNib + 327

7   com.apple.AppKit              0x0000000102617b6c +[NSBundle(NSNibLoading) _loadNibFile:nameTable:withZone:ownerBundle:] + 288

8   com.apple.AppKit              0x0000000102bf0f87 -[NSBundle(NSNibLoading) loadNibFile:externalNameTable:withZone:] + 150

9   com.apple.securityinterface   0x0000000101df77e4 -[SFAuthorizationPluginView initWithCallbacks:andEngineRef:] + 341

10  com.apple.securityAgentPlugin.NameAndPassword0x000000010cbf2eac -[EXNameAndPassword initWithCallbacks:andEngineRef:] + 105

11  com.apple.securityAgentPlugin.NameAndPassword0x000000010cbf0de7 -[EXAuthPluginMechanism invoke] + 205

12  com.apple.securityAgentPlugin.NameAndPassword0x000000010cbefe65 MechanismInvoke + 41

13  com.apple.SecurityAgent       0x0000000101912a21 0x10190f000 + 14881

TS 5.5.0.5 will install on Yosemite (my bad for doing it), but gives ONLY initial logon ability (even that badly) and nothing else.

So what a proble? Just run uninstall. Well, as pointed above does NOT work. OS never gets to login screen again.

Removing by hand /var/db/auth.db was the only way to get it "back to life"

One TrueMe fingerprint going on ebay...

Sorry to resurrect this thread... Has anyone been able to get TrueSuite to work in recent versions of OS X?

I might be getting close. I found that TrueSuite2.0.186, though the installation "fails", can be run from the Applications folder (perhaps this was released before they moved it to a preference pane), and allows fingerprint enrollment and authentication within the app itself.

However, under "Login window options" it simply says, "The login window is not enabled" - no options for using the fingerprint reader to auth OS X login.

I suspect that the check it is performing to determine if the login window is enabled has become obsolete (this version was likely written for OS X 10.5). Is there any way (by manipulating plists, etc) to get the app to realize the login window is indeed enabled? Does anyone know what plist attribute it may be looking for?

Thanks in advance