12

We believe that the password scheme is too vulnerable.

IE: http://www.theatlantic.com/magazine/archive/2011/11/hacked/8673/

We would like to be able to use phonefactor or other 2-factor mechanism to make fogbugz secure. Ideally, we would be able to say that access from our internal net is OK via single factor (pw), and from public net via two factor.

Alternately, a gmail kind of approach where I can do two-factor and authorize the computer to use one factor (pw only) for 30 days after a successful two factor auth.

http://www.phonefactor.com

Thanks!

(this is for real, I have no financial interest in phonefactor)

I should note: This is for self-hosted FB (on my own server)

flag

3 Answers

1

If FogBugz is running on a Windows Server using IIS or if it is configured to use LDAP authentication, PhoneFactor could be used for 2FA without any changes to the FogBugz application.

link|flag
1

The current version allows the admin to select the Strict Password policy:

The Strict Password Policy will enforce the following rules whenever a password is set:

Passwords must be at least 8 characters long

Passwords must contain:

  • At least 1 uppercase letter
  • At least 1 lowercase letter
  • At least 1 number
  • At least 1 special character (@,#,$,etc.)

We also have mechanisms in place to prevent brute force attacks against FogBugz via password-guessing. After a certain number of incorrect attempts, even a correct guess will not let you in until a period of time has elapsed. You can get the details from the code if you own FogBugz.

We don't pretend that these are enough for everyone ever in the history of the world. Security and authentication are always a moving target and needs are different depending on the data being secured. We find that our current authentication mechanism strikes a workable balance.

If these policies are insufficient for your organization, the next step is to restrict access to the FogBugz web site itself so that a user never even reaches the FogBugz web site/application, without having been authenticated to your satisfaction. Of course, this would require you to host FogBugz on your servers. Fortunately, those users who require stronger security than is built into FogBugz have mostly self-selected into FogBugz for Your Server anyway.

link|flag
How about exposing an interface via the plugin api that would allow a plugin to implement 2-factor authentication? Basically something that gets called after a user has already authenticated and can allow/deny further access depending on further authentication methods. I would very much like to see something like this. – Roman Oct 27 at 18:23
Rick, "Doing that is outside the purview of FogBugz development" does not sound very customer centric. Making FB secure, or secure-able (via a plugin) is, I believe, the job of FB. Two factor is all over the place (even gmail has it!). Why wouldn't a customer want FB to be as secure as gmail? – sam jones Jan 3 at 15:33
@sam: Gmail has it yes, but that's the main site using it, as access to your email is central to security nowadays. Apart from banks and the like, which inherently use top-level security. – Michel de Ruiter Jan 3 at 21:03
0

Why not just look into TeleSign? They just use a simple SOAP-API.

link|flag
Yes, there's actually many of these type of solutions out there. However the application still needs a way to send and receive these soap request/replies and to make a decision to allow/deny access based on the reply. Unless the solution is something that integrates directly with IIS, however in this case I imagine that you end up authenticating first to IIS with 2-factor and then again to Fogbugz. – Roman Oct 28 at 10:53

Your Answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.