This thread title asks: "What are the chances this will be addressed in LC?"

The answer turns out to be: "Quite good - pull request submitted, status changed to 'Awaiting Build'" - i.e. "done!"

http://quality.livecode.com/show_bug.cgi?id=14223

Many thanks to Peter Brett for addressing this, and implementing it in such a nice way.

From the pull request linked to in the bug report it seems we now have a new messageDigest function:

get messageDigest( <message>, <type> )

(Note: there's discussion in the pull request about the param order, and I'm inferring here; the actual implementation may be the other way around, with type first and then message - Peter, Monte, where did that land?)

...where (if I read the notes correctly; Peter please correct me if I'm wrong) <type> can be any of the following:

  md5
  sha1
  sha2
  sha3

Awesome!

With those we should be set for several years.

This will mean that from v9.0 dp6 forward you'll probably want to avoid using the older md5Digest and sha1Digest functions in favor of this new syntax.

If you need the older hash algos the new function apparently supports them, but of course if you need a cryptographic-quality hash use sha2 or sha3.

--
 Richard Gaskin
 Fourth World Systems
 Software Design and Development for the Desktop, Mobile, and the Web
 ____________________________________________________________________
 ambassa...@fourthworld.com                http://www.FourthWorld.com

_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Reply via email to