Databases
StackOverflow2013
Postsdbo
POSHA256 hash calculation
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POSHA256 hash calculation
    primarykey
    data
    text
    <p>for my employer I have to present customers of a web-app with checksums for certain files they download.</p> <p>I'd like to present the user with the hash their client tools are also likely to generate, hence I have been comparing online hashing tools. My question is regarding their form of hashing, since they differ, strangely enough.</p> <p>After a quick search I tested with 5:</p> <ol> <li><a href="http://www.convertstring.com/Hash/SHA256" rel="nofollow">http://www.convertstring.com/Hash/SHA256</a></li> <li><a href="http://www.freeformatter.com/sha256-generator.html#ad-output" rel="nofollow">http://www.freeformatter.com/sha256-generator.html#ad-output</a></li> <li><a href="http://online-encoder.com/sha256-encoder-decoder.html" rel="nofollow">http://online-encoder.com/sha256-encoder-decoder.html</a></li> <li><a href="http://www.xorbin.com/tools/sha256-hash-calculator" rel="nofollow">http://www.xorbin.com/tools/sha256-hash-calculator</a></li> <li><a href="http://www.everpassword.com/sha-256-generator" rel="nofollow">http://www.everpassword.com/sha-256-generator</a></li> </ol> <p>Entering the value 'test' (without 'enter' after it) all 5 give me the same SHA256 result. However, and here begins the peculiar thing, when I enter the value 'test[enter]test' (so two lines) online tool 1, 2 and 3 give me the same SHA256 hash, and site 4 and 5 give me a different one (so 1, 2 and 3 are equal, and 4 and 5 are equal). This most likely has to do with the way the tool, or underlying code handles \r\n, or at least I think so.</p> <p>Coincidentally, site 1, 2 and 3 present me with the same hash as my C# code does:</p> <pre><code> var sha256Now = ComputeHash(Encoding.UTF8.GetBytes("test\r\ntest"), new SHA256CryptoServiceProvider()); private static string ComputeHash(byte[] inputBytes, HashAlgorithm algorithm) { var hashedBytes = algorithm.ComputeHash(inputBytes); return BitConverter.ToString(hashedBytes); } </code></pre> <p>The question is: which sites are 'right'? </p> <p>Is there any way to know if a hash is compliant with the standard?</p> <p>UPDATE1: Changed the encoding to UTF8. This has no influence on the output hash being created though. Thx @Hans. (because my Encoding.Default is probably Encoding.UTF8)</p> <p>UPDATE2: Maybe I should expand the question a bit, since it may have been under-explained, sorry. I guess what I am asking is more of a usability question than a technical one; Should I offer all the hashes with different line endings? Or should I stick to one? The client will probably call my company afraid that their file was changed somehow if they have a different way of calculating the hash. How is this usually solved?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USGerben Rampaart
    1. USGerben Rampaart
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COWhich line ending do you consider to be right? Choose from \r, \n or \r\n. Fret about text encoding while you are at it.
      singulars
      1. POSHA256 hash calculation
      1. USHans Passant
    2. CO@Hans, I have no idea what you are trying to tell me.
      singulars
      1. POSHA256 hash calculation
      1. USGerben Rampaart
    3. COA hash algorithm works on *bytes*. There are lots of different ways to convert strings to bytes, all of them are 'right'. You like Encoding.Default for some reason, you'll regret that some day when your code runs on another machine with a different default. There are a hundred more to choose from. As long as you *have* to pick one that doesn't depend on a machine setting then you can't really go wrong with Encoding.UTF8.
      singulars
      1. POSHA256 hash calculation
      1. USHans Passant
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload