-
Notifications
You must be signed in to change notification settings - Fork 243
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Login fails on Firefox 32 and greater #2
Comments
I also can't log in on Firefox 34. Want to switch from LastPass because of Free Software, but can't yet. |
I'm using Firefox 32. I have the same problem. |
Yeah we're not really sure what the issue is with ff32. Maybe I'll have
|
Got the same problem here on Kubuntu 14.04 with FF32. Can't login - Chrome works though... |
I'm seeing this same issue. Is this going to be fixed soon, or should I switch to another password manager if I want to use Firefox? |
Same issue here too. I've rolled back to FFv31. Earlier today i posted a quick note requesting possible help from Mozilla. I'd be happy to chip in if that's of use. |
Yeah sorry, we haven't had the time to debug this issue. At the moment, the only workaround is to use Firefox v31. We are still searching for a contractor to help maintain Mitro in general, but it is slow going since this is a volunteer project. |
If I were to hire someone on freelancer.org to fix the bug would this be helpful? On Oct 1, 2014, at 9:11 AM, Evan Jones notifications@github.com wrote:
|
Put it on Kickstarter, IndieGoGo... Add Flattr or put it on one of the multiple "Donate for something" systems. Maybe some type of bounty would help too. I would contribute $50 easily if I saw a long term development which lets me trust in mitro's future. You simply can't use any password/secret storage system which suddenly stops working. Same goes for the servers. Think of just having an outage in the public mitro system. Everybody will lose big time. So far Mitro is not "safe" to use. You could not even get your current data back if the server suddenly stopped working (right?). |
I was just thinking of a quick fix for FF during the mitro transition from startup to open-source, which probably takes a bit of time to re-organize things. |
I would throw 50$ in as well to get this fixed! @splnlss if you get someone on freelance.org, count my 50 bucks in! Can't be so hard to get this fixed... |
If someone finds someone they think is able to fix this bug, Mitro can probably find the funds to pay them. Feel free to send me some names etc! Finding someone on something like Odesk or Elance etc is probably easiest, since they handle all the international payment and tax implications. |
I'm keen to get this fixed (and I have a week of annual leave this week and nothing to work on...) Are there any leads thus far as to where the bug exists or what caused it? Otherwise I'm just going to poke around the code-base with a debugger or two and see what I can find. |
Just fixed the issue! Will send out a pull request shortly. |
It works on Firefox 31, but we get some sort of exception on Firefox 32 and 33.
The text was updated successfully, but these errors were encountered: