You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I am constantly annoyed by an application that asks for my password. The executing file is askpass.exe. It has a logo that looks like a cheap China version of the source tree logo. Is this an official software from atlassian or is it malware ?
I also have this issue. There is definitely a bug somewhere in Sourcetree authentication. The AskPass.exe connection issue warning has been randomly popping up from time to time for about a month. It's really annoying.
I verified that the stored credentials in Tools\Options\Authentication are correct. It says "Authentication OK" at the bottom left. However, I do notice that the button "Refresh OAuth Token" does not work. After a few redirects there's a link like http://localhost:34106/?state=authenticated&code=KjjPkTZFBLmbp4Q2vK in Chrome that warns:
This site can’t be reached
localhostrefused to connect.
- Search Google for localhost 34106
After I restart Sourcetree my account will be logged in properly, and sometimes I need to do that to be logged in.
To follow up, the redirect has stopped going to "This site can't be reached" and seems to be resolving properly. Also the disconnections seem to be much less frequent. The last one seemed to relate to a Sourcetree incident (happened at the same time as a minor service issue posted on the website). There hasn't been an update in SourceTree since November so maybe a backend change improved it.
(Also to clarify, the warning popups occurred when Sourcetree is running in the background).
And this is expected behavior? From commercial software? I know that Sourcetree itself is free, but with all of the subscription fees that we pay for other Atlassian software, you'd think that they would be able to fix a bug that's bad enough that I'm just going to switch to Git Kraken and stick with that.
OK, thanks for a quick reply. Of course I tried google first. The file is signed and this is a good sign. However there is loads of sites that writes about suspicious files. All of them advertise different tools they want me to install. If I would have spent more time on http://systemexplorer.net/ maybe I would have trusted this answer right away. But I choosed to ask in a more trusted forum (here).
Giving someone else access to my employers source code through malware would have been pretty embarrassing.
I was experienced a different issue where the pop-up was related to being unable to locate the .exe. If anyone else is having issues with this, I was able to get the popup to stop appearing by ensuring that the environment variable SSH_ASKPASS was set to the SourceTree Askpass.exe file in .bashrc:
To be fair, I'm not sure that it's popping up due to the same bug as 5 years ago.
It wasn't happening when I first installed, but last year it was happening quite frequently, an average of once a day. It's still popping up for me but now only very occasionally, around once a week.
Unfortunately it is not documented
Since I've brought it up as a community question, and see others also experience it, problably the next step is to file it as a bug report? But I do see that there are ~19 reports regarding askpass.exe. https://jira.atlassian.com/browse/SRCTREEWIN-4370?jql=project%20%3D%20SRCTREEWIN%20AND%20text%20~%20%22askpass.exe%22 One comment says "AskPass.exe pops up about every 15 seconds." Luckily that is not the case for me.
Unfortunately, the Jira pages for Sourcetree are a complete waste of space. I reported issues THREE years ago that, in my consideration were worthy of a reasonably prompt fix, have never been fixed. People in the team I work in have experienced this askpass issue. One temporarily resolved the issue (coincidence?) by updating Sourcetree to 3.3.8, but the error has now re-appeared and another team member now has the problem :( . My solution? Stop using Sourcetree! I now use GitExtensions.