It would help to be careful with verbs here. Encryption is very different from a cryptographic hash both algorithmically and in commerce (export regs).
I presume you are not using decryption to "decipher" the documentation. I hope you are reading it. The SHA-1 algorithm does not "encrypt". It hashes. wunder On Aug 4, 2010, at 4:46 AM, Karl Erisman wrote: > Steve and Sam, > > Since asking the question I've found a second reason for needing > SHA-1: a particular specification I'm in the process of deciphering > (the IHE "Cross-Enterprise Document Sharing" profile) directly > requires its use (for detecting changes). > > My first goal was to encrypt individual data elements within a > document. For this, a cryptographic hash function would be necessary > (though, I realize, not sufficient). I've only cursorily considered > doing this encryption (we're still evaluating whether it is needed), > but I was thinking SHA-1 would be my preference here as well. > > So, I know I need SHA-1 (at least for the second reason). > > Thanks! > Karl > _______________________________________________ > General mailing list > [email protected] > http://developer.marklogic.com/mailman/listinfo/general _______________________________________________ General mailing list [email protected] http://developer.marklogic.com/mailman/listinfo/general
