When I launched total terminal today it informed me of the update. Once it downloaded it, I got a dialog saying the installer was locked by a password. This was not the OS dialog for username and password, it was a total terminal dialog that ONLY asked for a password. Then as you would normally expect the app installer later asked me for the admin username and password.
Why was I asked by the app for a password? (Not the system prompt for admin, just the first one) Did I get dooped here? Did this happen to everyone? This makes me very very nervous. Please help.
This was reported by some users. I was unable to reproduce it on my machines.
I don’t know why it is happening. I’m using Sparkle updater. I’m suspicious that this is something with DMG file. It can have some flag asking for password and for some users it gets confused and asks for password. Empty password will work.
Are you able to reproduce it? Can you use the same DMG file and install it again? Does it prompt again? If yes, can you send me md5 or sha1 of the DMG file? Maybe it got corrupted by some caching proxy or something? I’m puzzled.
I can not reproduce it. However, I did look up the string for the message it gave and saw some references to the sparkle update framework. I noticed someone on twitter had a similar prompt when using one of your products as well. The sparkle message is coming from their supasswordprompt.xib file. However it of course does not explain why. I find it very suspicious.
The string I looked up is “this update is locked with a password”. Hope that helps get a comforting answer.
Thanks for uncovering possible source. I’m probably using edge version of Sparkle which might have some quirks. I will try to resolve soon, because this is really bad prompt.
I just hacked Sparkle to not ask for the password. They have implemented some heuristics which will ask for password if normal DMG mounting fails for some reason. It looks like this heuristics is buggy.
Yes, people upgrading today from 1.5.2 (on stable channel) could still experience this bug. The code which fixes it will be effective when updating next time (to version 1.5.7 or higher).