On the other hand, the first (original) point (the GitHub issue) still stands to this day - it would make sense to either improve the default implementation of Auth to be usable (as per most every sane framework out there) or to provide a warning somewhere (at least on the Padrino guide for admin & auth?) would it not?
you are right, current auth is the most simple thing we have in mind. For sure can be better and so we planned to follow more an API standard so to be interchangeable with others auth systems.
That helper is 'dead'. Will be removed before 1.0.
If you have some others suggestions or you think there is something insecure, please share your thoughts. In this release we did a lot of stuff to improve that area, so you are welcome!
I can't tell at a glance whether this change was made after the issue and if the problem is now overcome, but I'm glad to hear that security is at least on your minds! Just switching to BCrypt from the old DES'd passwords is a wonderful step!
Best of luck and thanks for the great project!
Thanks for all!
1) We use bcrypt: https://github.com/padrino/padrino-framework/blob/master/pad...
2) Auth is an API we generate that for YOU, but you can change the code generated to fit your needs.