asp.net - Login Page security? -


i have designed login page 1 of our website have used following resources

  1. login name , passowrd lable , textboxes
  2. combo box multilingual support
  3. submit button.

now make page more secure planning use following points.

  1. captcha/ re-captcha
  2. number of retry: block after 3 unsuccessfull login attempt.

i have seen these things visiting other sites. know

  1. whether these extar point makes somediffrence security?
  2. how should implement number of retry? when should again unblock user account.

what right approach?

  1. general - require strong password , limit login tries/user (not ip/cookie). if add 5 minute lock-down user name after 3 fails bruit force attack take more years site live (dictionary attacks not possible since require strong passwords)*.

  2. protect users - in form, don't post password in clear text, post hashed version eg. md5([your domain] + [password]) reason add domain protect hash of password server owner (you), if user db hacked hashed passwords stored useless if users use same password on multiple sites. if stronger hash sha version. make js script replaces password hashed 1 before sending. remember have hash calculated on registration page, never let password sent browser in clear text. don't want know it!

  3. http://en.wikipedia.org/wiki/cross-site_request_forgery, have server sign cookie values make cookie forgery harder.

  4. encryption - either use tsl/ssl or rsa script , encrypt form data severs public_key.

  5. man-in-the-middle - hardest threat guard against, guess https easiest way trusted certificate costs money. if self sign users today don't bather if it's right cert or not, requires form users. buy cert or hope don't have man-in-the-middle.

i never use re-captcha login since lock-down of user name more effective , less disturbing user. though re-captcha account registration don't end having lot of scripted accounts.

  • limiting login tries/username used block user log in. bruit force attacks still available since can attack lot of usernames , not one, keeping attack under limit/username block. site few (less 10.000?) user accounts should quite safe.

Comments

Popular posts from this blog

c++ - Convert big endian to little endian when reading from a binary file -

C#: Application without a window or taskbar item (background app) that can still use Console.WriteLine() -

unicode - Are email addresses allowed to contain non-alphanumeric characters? -