Skip to main content

Validating Data Integrity with Hashes using .Net

Validating Data Integrity with Hashes:
            Hashes can be used to generate code that cross pond to specific data or file. But you can’t reproduce data from the hash. All hash algorithms inherit from System.Security.Cryptography.HashAlgorithms. These algorithms include:

MD5
Represents the abstract class from which all implementations of the MD5 hash algorithm inherit.
HashSize =128
 RIPEMD160
Represents the abstract class from which all implementations of the MD160 hash algorithm inherit.
HashSize=128
SHA1
HashSize = 160 bits
SHA256
HashSize = 256 bits
SHA384
HashSize = 384 bits
SHA512
HashSize = 512 bits

Keyed Hash Algorithms:
                All Keyed Hash Algorithms inherit from System.Security.Cryptography.KeyedHashAlgorithm which in turn inherits from HashAlgorithm. These Algorithms include:

HMACSHA1: Both sender and receiver share the same secret key. It uses SHA1 to produce hash of length 20 bytes. It accepts key of all sizes.

MACTripleDES: Uses TripleDES to produce a hash of 8 bytes. It accepts key of size 8, 16, or 24 bytes.

Computing a Non-Keyed hash:

byte[] data = new byte[DATA_SIZE];
MD5 md5 = new MD5CryptoServiceProvider();
byte[] result = md5.ComputeHash(data);


Computing a Keyed Hash:

HMACSHA1 myhmacsha1 = new HMACSHA1( key );
FileStream inStream = new FileStream(sourceFile, FileMode.Open);

byte[] hashValue = myhmacsha1.ComputeHash(inStream);

myhmacsha1.Clear();

inStream.Close();

Digitally Signing Files:
Digital signature is a value that is appended to a file to secure its contents. For this purpose public key is used that is the part of the signature. The recipient receives and verifies the signature, before trusting on it. RSACryptoServiceProvider and DSACryptoServiceProvider are the two implementations for digitally signing documents. Properties involved in signing are:

SignData
Overloaded. Computes the hash value of the specified data and signs it.
SignHash
Computes the signature for the specified hash value by encrypting it with the private key.
ToXmlString 
Creates and returns an XML string containing the key of the current RSA object. (Inherited from RSA.)
VerifyData
Verifies the specified signature data by comparing it to the signature computed for the specified data.
VerifyHash
Verifies the specified signature data by comparing it to the signature computed for the specified hash value.
Labels:

Comments

Post a Comment

Popular posts from this blog

Culture Information and Localization in .NET

Namespace: System.Globalization CultureInfo Class:                 It provides information like the Format of numbers and dates, Culture’s Calendar, Culture’s language and sublanguage (if applicable), Country and region of the culture. The Basic use of CultureInfo class is shown here: • How string Comparisons are performed • How Number Comparison & Formats are performed • Date Comparison and Formats. • How resources are retrieved and used. Cultures are grouped into three categories: Invariant Culture : It’s Culture Insensitive. It can be used to build some trial application. It can be also used to build an application with hard-coded expiry date that ignores cultures. But using it for every comparison will be incorrect and inappropriate. Neutral Culture : English(en), Frensh(fr), and Spanish(sp). A neutral culture is related to language but it’s not related to specific regi...
Post a Comment
Continue Reading »

Text Encoding and Decoding using .Net

Namespace: System.Text To read a file, an application must write information about the encoding in which the file was written. So, the application that creates a file must write encoding information, otherwise viewer will see block and question marks in file. Unicode UTF-32 encoding : Represents a character as sequence of four bytes (32 bits). UTF32Encoding class can be used in that perspective. Unicode UTF-16 encoding : Represents a character in 16 bits. UnicodeEncoding class can be used to convert to and from UTF-16 encoding. Unicode UTF-8 encoding : Unicode UTF-8 uses 8-bit, 16-bit, 24-bit, and up to 48-bit encoding. Values 0 through 127 use 8-bit encoding and exactly match ASCII values, 128 through 2047 use 16-bit encoding, and values from 2048 and 65535 uses 24-bit encoding. UTF8Encoding class can be used to convert to and from UTF-8 encoding. ASCII encoding : ASCII encoding encodes Latin alphabets as single 7-Bit ASCII character. It is not well su...
Post a Comment
Continue Reading »

Using ADO.NET Transaction Object, Saving CLR Objects and SqlNotificationRequest

Serializable allows one transaction to complete before the other start. SqlConnectoin support named savpoint to roll back to; that’s an equaliant to save transaction command in MS SQL Server. Using TransactionScope Object : A transaction can’t span multiple connections.   Local and distributed transaction ares supported in 1.x you have to Enterpeise seveices library to regiser multiple connections and then call EnlistDistributedTransaction. Distributed Transaction Coordinator is required for Distributed transaction that’s available on windows 2000 & +. In 2.X and later use TransactionScope object. Serializable allows one transaction to complete before the other start. SqlConnectoin support named savpoint to roll back to; that’s an equaliant to save transaction command in MS SQL Server. Using TransactionScope Object : Dispoase of the transaction must be called to complete the transaction. Distributed Transaction : ...
Continue Reading »