sha

I'm not talking about server-side node.js. I want to use a slow hashing algorithm for a key on the client-side of my site. I have found implementations of SHA-256 which seem to be reliable . I also found this question which lead to the OP creating his own library . However, I'm not sure if I should just do multiple rounds of SHA hashing or trust some of that code since I'm not a security expert and it doesn't seem to have a large following only being "stared" by 36 people. What is the best choice in this case? I (basically) cannot change methods once I choose something. I want a slow hashing

I'm using SHA-1 to detect duplicates in a program handling files. It is not required to be cryptographic strong and may be reversible. I found this list of fast hash functions https://code.google.com/p/xxhash/ What do I choose if I want a faster function and collision on random data near to SHA-1? Maybe a 128 bit hash is good enough for file deduplication? (vs 160 bit sha-1) In my program the hash is calculated on chuncks from 0 - 512 KB. A. Binzxxxxxx Maybe this will help you: https://softwareengineering.stackexchange.com/questions/49550/which-hashing-algorithm-is-best-for-uniqueness-and

I have an application that creates a serial key as follows: Take customername Sign customername using privatekey and sha/dsa algorithm Then license can be checked by decoding with public key, and checking cuastomername matches This works okay except that the generated serial is rather long. So it is not really practical for customer to type in the serial key instead they have to provide a serial with in a file, which is rather different to how mist applications and work and is confusing. Many other applications just provide the user with a Guid when they make a purchase i.e 5bd1060b-8608-4817

I'm seeing an issue with some code I maintain. The code below has a private static SHA1 member (which is an IDisposable but since it's static , it should never get finalized). However, under stress this code throws an exception that suggests it has been closed: Caught exception. Safe handle has been closed" Stack trace: Call stack where exception was thrown at System.Runtime.InteropServices.SafeHandle.DangerousAddRef(Boolean& success) at System.Security.Cryptography.Utils.HashData(SafeHashHandle hHash, Byte[] data, Int32 cbData, Int32 ibStart, Int32 cbSize) at System.Security.Cryptography

The definition of SHA-256 appears to be such that the input consisting of a single "1" bit has a well-defined hash value, distinct from that of the "01" byte (since the padding is done based on input's length in bits). However, due to endianness issues and the fact that no implementations that I can find support feeding in single bits, I can't quite figure out what this correct value is. So, what is the correct hash of the 1-bit long input consisting of the bit "1"? (not the 8-bit long byte[] { 1 } input). OK, according to my own implementation: 1-bit string "1" : B9DEBF7D 52F36E64 68A54817