search

isvissu / logkext

Automatically exported from code.google.com/p/logkext
0 stars 0 forks source link

Error finding passKey in keychain (-25293). Failing #2

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
This error message occurs when first running logKextClient with sudo.  It does 
not appear when 
running logKextClient immediately afterwards.  Not sure why.

Original issue reported on code.google.com by drspring...@gmail.com on 10 Jan 2008 at 5:17

GoogleCodeExporter commented 8 years ago 
i am getting this error as well. running 10.5.1. did not get this error in past
versions in OS < 10.5

at first, the problem only occurred in the first instance, now it occurs all the
time. logkext is now unusable.

Original comment by TShareSt...@gmail.com on 11 Feb 2008 at 5:29

GoogleCodeExporter commented 8 years ago 
Also seeing same
As a note, my "root" pass and kextLog are both using the same password.

Original comment by shovel...@gmail.com on 6 Mar 2008 at 2:39

GoogleCodeExporter commented 8 years ago 
This has happened to me as well. I found that re-running the command however 
allows you to use the 
LogKextClient. This however does open the LogKext daemon twice, so you have to 
quit one of them in activity 
monitor.

Original comment by figster...@gmail.com on 16 Mar 2008 at 8:41

GoogleCodeExporter commented 8 years ago 
figster: logKextDaemon should never be opened when logKextClient is run, or 
that's another bug.

Original comment by drspring...@gmail.com on 20 Mar 2008 at 4:30

GoogleCodeExporter commented 8 years ago 
Getting the same here. :P

Original comment by spicyjal...@gmail.com on 3 Jul 2008 at 12:07

GoogleCodeExporter commented 8 years ago 
Same here. MBP 2.33 running 10.5.4

Original comment by michaelmiller on 4 Jul 2008 at 5:56

GoogleCodeExporter commented 8 years ago 
Same here, running 10.5.4

Original comment by chan...@gmail.com on 3 Aug 2008 at 9:47

GoogleCodeExporter commented 8 years ago

Original comment by drspring...@gmail.com on 26 Aug 2008 at 1:24

GoogleCodeExporter commented 8 years ago 
After rooting around with this for a while, it appears to me that /usr/bin/sudo 
does
not have equivalent access to the system keychain as does the actual root user. 
Ultimately, the error that is occurring is found in the secure.log:
com.apple.SecurityServer[19]: suppressing keychain prompt for invalidly signed 
client
/usr/bin/sudo(44179).

The error occurs when logKextClient calls SecKeychainFindGenericPassword but 
only if
it requests the passwordData.  And a result of "Authorization/Authentication 
failed
(25293)" is returned.  If SecKeychainFindGenericPassword is called with
passwordLength and passwordData set to NULL, the keychain item is found and the
result is successful.

I believe the problem lies in that the TrustedApplications that are added to the
keychain item by logKextKeyGen are signed differently when they are added than 
they
are when run under /usr/bin/sudo.

I worked to correct this (several months ago), and was unsuccessful at making 
any
programmatic changes with logKext that remedy this error.  However, it seems 
that if
logKextClient is called by the actual root user, this error is avoided.  So one 
way
to avoid this error message is to enable the root user in OS X and simply call 
su,
login, then call logKextClient.  Another way to do this without enabling the 
root
user (I believe) is to call "sudo su" before you call logKextClient.  At least 
this
annoyance is avoided by taking this approach, but I will continue to work on 
this and
would appreciate anyone's input...as I am not a very experienced apple 
programmer.

Original comment by thomas.j...@gmail.com on 5 Oct 2008 at 5:24

GoogleCodeExporter commented 8 years ago 
Same error occurs on my MacBook Pro, OS X 10.5.4. when first running 
logKextClient
with sudo (when sudo requires a password), does not appear when running 
logKextClient
repeatedly immediately afterwards (whenever sudo does not require a password).

   $ sudo logKextClient
   Password: ********
   logKext Password: ******
   Error finding passKey in keychain (-25293). Failing
   $ sudo logKextClient
   logKext Password: ******
   Current logfile status: 25 kilobytes.
   Type 'help' for usage help, or 'quit' to quit.
   logKextClient > quit
   $ sudo logKextClient
   logKext Password: ******
   Current logfile status: 25 kilobytes.
   Type 'help' for usage help, or 'quit' to quit.

I'm not seeing multiple instnaces of the client or daemon in Activity Montior,
counter figster983 above.

Original comment by jeremydouglass@gmail.com on 21 Oct 2008 at 3:37

GoogleCodeExporter commented 8 years ago 
I'm having this problem too. I'm on a MacBook C2D (plastic), 10.5.6

Also, I recently had to reinstall logKext because after a time machine restore i
could not get into the logKextClient - it kept throwing up 
   Error finding passKey in keychain (-25293). Failing

Original comment by mouz...@gmail.com on 8 Mar 2009 at 6:26

GoogleCodeExporter commented 8 years ago 
Interesting, now I'm having the keychain passkey error spit out everytime I try 
to open logKextClient:

Error finding passKey in keychain (-25300). Failing

It also constantly tries to start the daemon every 10 seconds. I have no idea 
how long this has been going on 
for, but I think a while.. I get these error messages constantly in console:

3/19/09 2:23:15 PM /Library/Application Support/logKext/logKextDaemon[7640] 
Error finding passKey in 
keychain (-25300). Failing 
3/19/09 2:23:15 PM com.apple.launchd[1] (com.fsb.logKext[7640]) Exited with 
exit code: 255 
3/19/09 2:23:15 PM com.apple.launchd[1] (com.fsb.logKext) Throttling respawn: 
Will start in 10 seconds 

Any ideas? I think i might just reinstall..

Original comment by figster...@gmail.com on 19 Mar 2009 at 7:26

GoogleCodeExporter commented 8 years ago 
interesting update - i just reinstalled it and now I can get into the client 
just fine. i also am not getting any more 
error messages.

However, my log file that i've had for about a year has been deleted. oh well, 
i'll probably get it from my 
backups (hopefully that was backed up!)

Original comment by figster...@gmail.com on 19 Mar 2009 at 7:37

GoogleCodeExporter commented 8 years ago 
error finding passkey on keychain? i know the answer to all your problems, i 
had this
problem myself so i tried fixing it every way possible. so, just go to
finder>applications>utilities>keychain access, or just use spotlight to find 
it. once
there, click on the keychain access menu and then go to keychain first aid, 
type in
your password and click on both verify and repair buttons. that's it! now your
logKext client will load wthout any problems, peace.

Original comment by lessthan...@gmail.com on 31 Jul 2009 at 5:08

GoogleCodeExporter commented 8 years ago 
I tried both to log in as super user and verify/repair my keychain with no 
succes. Anybody had?

Original comment by hef...@gmail.com on 16 Sep 2010 at 3:58

GoogleCodeExporter commented 8 years ago 
Hi All.  I am not a code geek, nor do I have any special training other than 
perseverance.  I run a Powerbook G4 PPC.  At first I downloaded logKext v 2.3 
and was getting the "...is Daemon running?' error.  I did a couple of 
re-installs and no luck.  I de-installed it and downloaded v 2.2.  Then I got 
the 'error finding passKey in keychain" error.  This is what solved my problem: 
 I went into the keychain access > System>LogKextpassKey> it will ask for your 
password > next window> then check "allow all applications to access this 
item".  This seems to have solved the problem now and it is running 
well......so far!

Original comment by beejay.a...@gmail.com on 7 Nov 2010 at 6:55