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 »

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 »

Code Access Security in .Net

Namespace: System.Security What is Code Access Security? Code Access Security is a mechanism through which Developers and administrators can restrict code from accessing different resources , without caring about the users’ access level. You can also control resource that can’t be controlled through traditional RBS (Role Based Security), e.g. Web Requests and DNS requests etc. It can be only applied to Managed Applications. These restriction are applied not to the user instead to the Application, thus it does not require username or password. Evidence: It is the information that runtime gather about the assembly to determine which Code Groups the assembly belongs to. The following table shows the common types of evidence that a host can present to the runtime. Evidence Description Application directory The application's installation directory. Hash Cryptographic hash such as SHA1. Publisher Soft...
Post a Comment
Continue Reading »