password doesn't work anymore?!

Started by iloving, July 23, 2012, 01:14:54 PM

Previous topic - Next topic

iloving

After having used espionage successfully for a couple months now, I tried unlocking my folders today only to find that my master password was being rejected!  

I tried following some instructions I found regarding renaming the Espionage folder in Application Support, but the part regarding re-adding the previous folders didn't work.  For now I have restored my previous settings, but this has screwed me right up.

Recently (during the past week) I have:
- run disk utility which found a couple of volume errors
- reset my NVRAM because my trackpad was acting a bit odd (turns out it was probably just the heat)
- Updated my copy of parallels.

I don't know if any of the above is even relevant, but I can't think of what could have caused this to happen.

Any help would be appreciated because I have some important stuff in those folders that I need access to asap.

zsolt

#1
Hello re adding the folders in V3 is not that easy as you do not know the password for the disk images, unless you copied it out upfront at the time it worked fine.
So we first need to make it unlock, please do not reinstall or delete anything.

If possible, bring all back into state before you started to rename things.
The important file is the one in your Library/Application Support/com.taoeffect.... folder, there will be a file called database3. There will be more of these in the Backup subfolder.

What you have to do is:
- quit espionage using the padlock menu item
- pick one of the database3 file from the Backup folder, copy it into parent folder so that it is in Library/Application Support/com.taoeffect.... folder, start Espionage, then try to unlock it.
Note that you need to use the master password which was active at the time when that copy of the database was in use, this is in case you were chaining the password.

Whenever you try to unlock espionage (and it fails) copy the system.log messages showing that attempt, with a note which database3 did you try in that particular attempt.

Then send me those messages if you do not manage to unlock it.
Note that sometimes it takes up to 10-15 seconds for Espionage to unlock, so give it some time.

Let me know how it went.

Rgds
Zsolt
Follow @espionageapp on twitter for news! | For general Mac support, please visit Mac Me Support

iloving

#2
I do not have a com.taoeffect... folder under Application Support. I do have an Espionage folder though.  I tried following your suggestions there.  When I try to unlock, I get the following in my system log:

12-07-23 5:16:32.410 PM Espionage: ERROR (-[DBMaster getSubDBWithPassword:error:]:127): failed because: !data

I have this problem no matter which database3 file I've tried. I've tried the original and several backups, going right back to the earliest one I had.

iloving

#3
Bump?  I'm still having the problem.

zsolt

#4
Hello, would it be possible to have a remote session so that I can take a look into this with you?
Let me know when are you earliest available.

Rgds
Zsolt
Follow @espionageapp on twitter for news! | For general Mac support, please visit Mac Me Support

iloving

#5
Quote from: "zsolt"Hello, would it be possible to have a remote session so that I can take a look into this with you?
Let me know when are you earliest available.

Rgds
Zsolt

By all means!  When and how?

zsolt

#6
I'm available now for next hour, and same time tomorrow. Just mail me when ready.
Rgds
Zsolt
Follow @espionageapp on twitter for news! | For general Mac support, please visit Mac Me Support

iloving

#7
Just FYI, I was having multiple other problems with the machine, and I ended performing a complete reinstall of the OS and restoring from backups.  For now I'm going to assume that some kind of corruption occurred.  I will let you know if the issue happens again.

mike115

#8
Hi,

I am desperate for help. My password doesn't work any more. Have tried the above method to no avail.

I am happy for you to have a look remotely or mail me mailto:mike115@me.com">mike115@me.com

Mike

zsolt

#9
Hello MIke,

We can do a remote session if you wish, I will be available most of the day tomorrow, I'm in GMT+2 time zone, like paris/rome/berlin.

Can you please open the console and try to unlock the Espionage again, then copy me the errors from the console messages.

Also, just to be sure, you are talking about master password, ie. you cannot unlock espionage and not the folder password, i.e. that you cannot unlock a protected folder, correct?

Please mail me to mailto:taoeffect@macmesupport.com">taoeffect@macmesupport.com and let me know the time is suites you for remote session, it will be better then to communicate through this forum.

Rgds
Zsolt
Follow @espionageapp on twitter for news! | For general Mac support, please visit Mac Me Support

rramdin

#10
I think I'm also having this error. This is the message I'm getting:

Aug 31 17:22:41 robby-mbp Espionage[8993]: ERROR (-[DBMaster getSubDBWithPassword:error:]:140): failed because: !data

Does this mean I used the wrong password or is it indicative of a problem?

iloving

#11
The problem has happened again, and this time I'm sure I'm not goofing up the password.  I get the below errors in the log.  How should we proceed?

12-09-18 3:15:03.653 PM Espionage: ERROR (-[NSData(TECrypto) decrypt:]:131): scryptdec_buf returned: 9
12-09-18 3:15:03.653 PM Espionage: ERROR (+[DBSubdb subdbWithData:master:pass:error:]:45): failed because: !decrypted

zsolt

#12
Hello, pls download this custom build
http://www.taoeffect.com/other/Espionag ... 9-fix1.zip
quit Espionage, rename it to Espionage-orig copy the one you downloaded into Application folder and launch it, then try to unlock the folder again.
Let me know if it did not work,

Rgds
Zsolt
Follow @espionageapp on twitter for news! | For general Mac support, please visit Mac Me Support

iloving

#13
Thank you, that worked.  
May I ask what that did?  
Is there something I may have done to cause this?

zsolt

#14
No, it is an error we did not find yet the reason for, and this custom builds does a different kind of verification so that it is not affected by the problem.
You did nothing wrong :-)

I'm glad it worked,

Zsolt
Follow @espionageapp on twitter for news! | For general Mac support, please visit Mac Me Support