Looks good to me, just to make sure, your re-write doesn't change the the output, right?
Diego
Sent from my android cell
--
--
Lift, the simply functional web framework: http://liftweb.net
Code: http://github.com/lift
Discussion: http://groups.google.com/group/liftweb
Stuck? Help us help you: https://www.assembla.com/wiki/show/liftweb/Posting_example_code
Awesome then!
Diego
Sent from my android cell
So, I realized this morning when I was in the shower that something didn't make sense. We're base 64 encoding md5 and sha hashes to turn them into a string... don't most people use hex encoding for those?
On Saturday, January 19, 2013 12:39:31 AM UTC-5, Matt Farmer wrote:So, the contribution guidelines indicate that Pull Requests need to be discussed here before being opened. Seeing as this was a cleanup, I decided to just implement the changes in a clone and then paste in a link to the diff to facilitate a discussion. If I should do something different for changes like this in the future, let me know. :)Anyway, I did some cleanups to SecurityHelpers. Specifically, the code for generating a base64 string was duplicated in a few places in the file, so I converted those to calls to base64Encode. I also removed some unneeded parens that I found. Here's the diff: https://github.com/farmdawgnation/framework/compare/master...cleanup_security_helpersLet me know if you guys want to changes, and if so I'll open a Pull Request.Cheers!
--
--
Lift, the simply functional web framework: http://liftweb.net
Code: http://github.com/lift
Discussion: http://groups.google.com/group/liftweb
Stuck? Help us help you: https://www.assembla.com/wiki/show/liftweb/Posting_example_code
o.O Er.... I didn't silently change the results. I left the results as-is (unless I botched something in my branch). I was just trying to start a discussion about it.
Completely, 100% valid. :)But while we're on the topic, do you mind if I pick your brain as to why base64 was chosen over a hex-string representation?