 |  |  |  |  |  |  |  |
delay signing
Please support our C# advertiser: Intel Parallel Studio Home
Thread Solved |
You're burning up the forum with general questions. Are you in college? 
Check this article out:
http://blogs.msdn.com/shawnfa/archiv.../17/91575.aspx
An excerpt from it that sums it up:
Delay Signing
Most people know about the delay signing feature of the CLR. (For those who don't check out MSDN's Delay Signing an Assembly for more details). Basically, delay signing allows a developer to add the public key token to an assembly, without having access to the private key token. Since the public key token is part of an assembly's strong name, it allows assemblies under development to carry the same identity as they will have when they are actually signed, however it does not require every developer to have access to the private keys.
For instance, at Microsoft, in order to get an assembly signed, we have to submit it to a special signing group, which are the only people that have access to the full Microsoft key pair. Obviously we don't want to go through this process for every daily build of the framework, let alone for each developer's private builds (imagine the debugging process if you had to wait for a central key group to sign each and every build you created). Instead of going through all of this overhead, we simply delay sign our assemblies until we get ready to make a release to the public, at which point we go through the formal signing process.
A delay signed assembly contains only the public key token of the signing key, not an actual signature. (Since, the person producing the delay signed assembly most likely doesn't have access to the private key necessary to create a signature). Inside the PE file produced, a delay signed assembly has space reserved for a signature to be placed in the future, but that signature is actually just a block of zeros until the real signature is computed. Because this block is not likely to be the actual signature value of the assembly, these assemblies will all fail to verify upon loading. (since their signatures are incorrect).
Check this article out:
http://blogs.msdn.com/shawnfa/archiv.../17/91575.aspx
An excerpt from it that sums it up:
Delay Signing
Most people know about the delay signing feature of the CLR. (For those who don't check out MSDN's Delay Signing an Assembly for more details). Basically, delay signing allows a developer to add the public key token to an assembly, without having access to the private key token. Since the public key token is part of an assembly's strong name, it allows assemblies under development to carry the same identity as they will have when they are actually signed, however it does not require every developer to have access to the private keys.
For instance, at Microsoft, in order to get an assembly signed, we have to submit it to a special signing group, which are the only people that have access to the full Microsoft key pair. Obviously we don't want to go through this process for every daily build of the framework, let alone for each developer's private builds (imagine the debugging process if you had to wait for a central key group to sign each and every build you created). Instead of going through all of this overhead, we simply delay sign our assemblies until we get ready to make a release to the public, at which point we go through the formal signing process.
A delay signed assembly contains only the public key token of the signing key, not an actual signature. (Since, the person producing the delay signed assembly most likely doesn't have access to the private key necessary to create a signature). Inside the PE file produced, a delay signed assembly has space reserved for a signature to be placed in the future, but that signature is actually just a block of zeros until the real signature is computed. Because this block is not likely to be the actual signature value of the assembly, these assemblies will all fail to verify upon loading. (since their signatures are incorrect).
 |
Similar Threads
- Using Delay or Pause, without the whole thing freezing? (Visual Basic 4 / 5 / 6)
- Perl- How to call an event after a time delay (Perl)
- Internet Explorer connect delay - Spyware? (Viruses, Spyware and other Nasties)
- I use windows 2000, and it keeps signing me off. (Windows NT / 2000 / XP)
- 1 do while with 2 delay (how u do that??) (C++)
- Server delay - with html, asp, aspx pages (ASP.NET)
- Stop Windows Messenger From Signing In (Windows tips 'n' tweaks)
- big trouble with signing in (Web Browsers)
Other Threads in the C# Forum
- Previous Thread: Proper component for table display
- Next Thread: WPF MediaElement displaying Images or Video with transitions
| Thread Tools | Search this Thread |
Latest C# Posts
- Today's Posts
- Unanswered Threads
Related Forum Features
Tag cloud for C#
.net access ado.net algorithm array barchart bitmap box broadcast buttons c# chat check checkbox client color combobox control conversion csharp custom database datagrid datagridview dataset datetime degrees development draganddrop drawing encryption enum event excel file files form format forms function gdi+ httpwebrequest image index input install java label list listbox listener login mandelbrot math mouseclick mysql networking object operator oracle path photoshop picturebox pixelinversion post prime programming radians regex remote remoting resource richtextbox saving serialization server sleep socket sql statistics stream string table tcp text textbox thread time timer treeview update usercontrol validation view visualstudio webbrowser windows winforms wpf xml
