Dot Net Framework: Introduction to CLR and Encryption in Dot Net

This article provides an introduction to the Dot Net Framework, including the Common Language Runtime and encryption in Dot Net. It explains hashing, symmetric encryption, and asymmetric encryption. The article also discusses the characteristics and weaknesses of these encryption methods and how they are used together for modern cryptography.

Dot Net format
All things considered, it is a product structure in which we plan and make superb applications.
This system is presented by Microsoft which implies it has incredible future with head bolster.
Prologue To CLR
The Common Language Runtime, the primary machine or key part of Microsoft Dot Net
Framework and it deals with the aggregate execution of DOT NET projects.
Under .NET Framework, there are classifications the code into two kind initially oversee code
which runs and executed under CLR condition and unmanaged code which not run and execute
under CLR condition [1].
Code is Managed
The Overseen code [1, 2] is the resultant yield of source code done by the compiler and that code
is composed in one of more than 10 abnormal state programming dialects that are utilized with
the Microsoft .NET Framework, that includes C sharp, J sharp, VB Dot NET, JavaScript while
unmanaged code alludes to programs written in C, C++, and different dialects that needn't bother
with a runtime to execute.

Encryption in Dot Net.
Dot NET structure has healthy encryption policy which is according to Microsoft security policy
for encryption. It's basic that every architect appreciates these thoughts beforehand proceeding
with any further [3.4]:
1. Hashing
Hashes not really are the encryption, basically, in any case they are primary to all other
encryption errands. A hash is a data one of a kind finger impression - a little game plan of bytes
that addresses the uniqueness of an extensively greater square of bytes. Like fingerprints, no two
should ever be indistinct, and an organizing special check is conclusive confirmation of identity.
2. Symmetric Encryption

In symmetric encryption, a singular key is used for scrambling and unscrambling the data. This
sort of encryption is brisk, yet has an outrageous issue: remembering the ultimate objective to
bestow a secret to some person, they have to know your key. This surmises an irregular condition
of trust between people sharing insider certainties; if a degenerate individual has your key- - or if
your key is gotten by an undercover agent, it can unscramble each one of the messages you send
using that key!
3. Asymmetric Encryption
Upside down encryption handles the trust issue natural in symmetric encryption by using two
assorted keys: an open key for encoding messages, and a private key for disentangling messages.
This makes it possible to pass on in riddle with people you don't totally trust. In case a
degenerate individual has your open key, general society key is helpful for encryption; it's futile
for interpreting. They cannot unscramble any of your messages! In any case, uneven encryption
is direct. It's not endorsed for use on more than around 1 kilobyte of data.
These three thoughts are enthusiastically intertwined and reliably watched together in exhibit day
cryptography. They have assorted characteristics and weaknesses; combining them offers a
significantly bigger measure of security than can be proficient using a single system alone. For
example, when precisely transmitting a check to your bank, each one of the three of these
systems are used:

References
1. Boehm Anne: Murachs ASP.NET 3.5 Web Programming with VB, Mike Murach and
Associates, 2008, ISBN 978-1-890774-47-9
2. Samtani Gunja, “Application Frameworks”, [online], 2017. Available
http://www.nws.noaa.gov/oh/hrl/hseb/docs/ApplicationFrameworks.pdf.
3. Walther Stephen, ASP.NET 3.5 Unleashed, Sams Publishing, ISBN 0-672-33011-3,
2007.
4. Walther Stephen, Data Access in the ASP.NET 2.0 Framework, Sams Publishing, ISBN
0-672-32952-2, 2007