Deploying patches that work with digitally signed .NET assemblies
From: anelson327 (anelson327_at_yahoo.com)
Date: 11/30/05
- Previous message: Marlon Brown: "Perimeter domain:using corporate Anti-virus repository or let servers go to Internet"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: 29 Nov 2005 15:27:18 -0800
Does anyone have some best practices for how to deploy patches
(selected subsets of assemblies) that will work with other previously
deployed .NET assemblies that are all digitally signed with an
Authenticode (digital code signing) certificate and enforce link
demands? We're using LinkDemand to ensure that callers have been
signed with the same digital certificate as the assemblies being called
(to ensure their authenticity), but once a certificate expires, it
appears that a "patch" of any of these assemblies is not possible --
all assemblies have to be resigned with a valid certificate and
redeployed. Is our understanding correct about this, and are there
suggestions/best practices for dealing with this situation?
- Previous message: Marlon Brown: "Perimeter domain:using corporate Anti-virus repository or let servers go to Internet"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
