The whole point about strong names is to ensure that the clients (UI, External
components etc) who is consuming the DLL knows that the DLL was published from a
valid source. This authenticity is verified by using strong names. The strong
name protection is good from external hackers but what if your own developers
think of doing something mischievous.
That’s where delay signing helps. The strong name key has two keys public key
and private key. You only share the public key with your developers so that they
can work seamlessly. The private key is stored in a secured location and when
the DLL is about to be deployed on production the key is injected for further
security.
Also view our video on Garbage Collector, Gen 0, 1 & 2 as follows: -
Get our more article on interview questions and answers for Dotnet
Regards,
See newly added more author’s article on Most asked Dotnet interview questions
components etc) who is consuming the DLL knows that the DLL was published from a
valid source. This authenticity is verified by using strong names. The strong
name protection is good from external hackers but what if your own developers
think of doing something mischievous.
That’s where delay signing helps. The strong name key has two keys public key
and private key. You only share the public key with your developers so that they
can work seamlessly. The private key is stored in a secured location and when
the DLL is about to be deployed on production the key is injected for further
security.
Also view our video on Garbage Collector, Gen 0, 1 & 2 as follows: -
Get our more article on interview questions and answers for Dotnet
Regards,
See newly added more author’s article on Most asked Dotnet interview questions
No comments:
Post a Comment