• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Jeanne Boyarsky
  • Liutauras Vilda
  • Campbell Ritchie
  • Tim Cooke
  • Bear Bibeault
Sheriffs:
  • Paul Clapham
  • Junilu Lacar
  • Knute Snortum
Saloon Keepers:
  • Ron McLeod
  • Ganesh Patekar
  • Tim Moores
  • Pete Letkeman
  • Stephan van Hulst
Bartenders:
  • Carey Brown
  • Tim Holloway
  • Joe Ess

Struts 1.3.9 Password Reminder Action class  RSS feed

 
Ranch Hand
Posts: 49
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Is this as it says "encryption" or just hashing with MessageDigest? Is this good enough? Should I use SHA? Are code conventions completely followed?
 
Ranch Hand
Posts: 471
Hibernate Mac OS X Spring
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I prefer that passwords are hashed, since this is non reversible. Of course there are hash tables to be able to be used as lookup tables, but this can be overcome using a salt source, like always adding something like *&username{^ to the password before hashing, or better off, you can add it to the hashed password, then rehash again. This makes it nearly impossible to lookup password.

Reversible encryption methods can be used if you have a strong encrypting method, and more importantly a strong key. As I said, hashing using MD5 with a salt source is really strong security, and I recommend that.
 
It is sorta covered in the JavaRanch Style Guide.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!