security.config files in .NET framework
Hi!
I have an MSI package (SAS Office Addin 1.3) that makes modifications in the following files:
--------------
c:\windows\Microsoft.NET\Framework\v1.1.4322\CONFIG\enterprisec.config.cch
c:\windows\Microsoft.NET\Framework\v1.1.4322\CONFIG\security.config.cch
c:\documents and settings\my profile\Appliaction data\Microsoft\CLR Security Config\v1.1.4322\security.config
c:\documents and settings\my profile\Appliaction data\Microsoft\CLR Security Config\v1.1.4322\security.config.cch
--------------
I guess these files are some kind of config files in XML format, but could anyone give me a good explanation about their functionality.
Just writing over the old files with new modified files doesn't seem smart, since I might lose old settings. Is the preferred way to edit the files with a .vbs script or what?
What will happen if the files are removed from the system?
Any ideas?
I have an MSI package (SAS Office Addin 1.3) that makes modifications in the following files:
--------------
c:\windows\Microsoft.NET\Framework\v1.1.4322\CONFIG\enterprisec.config.cch
c:\windows\Microsoft.NET\Framework\v1.1.4322\CONFIG\security.config.cch
c:\documents and settings\my profile\Appliaction data\Microsoft\CLR Security Config\v1.1.4322\security.config
c:\documents and settings\my profile\Appliaction data\Microsoft\CLR Security Config\v1.1.4322\security.config.cch
--------------
I guess these files are some kind of config files in XML format, but could anyone give me a good explanation about their functionality.
Just writing over the old files with new modified files doesn't seem smart, since I might lose old settings. Is the preferred way to edit the files with a .vbs script or what?
What will happen if the files are removed from the system?
Any ideas?
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
brenthunter2005
19 years ago
Posted by:
wicket
19 years ago
Sure, I'm using Wise. Thank you for the information, guess I have a bit to learn :-)
The thing is that this issue was found on a validation of existing packages in production. Is this such a major issue that the package should be replaced with an updated version?
(I have very little *read no* experience of the security settings in .NET)
The thing is that this issue was found on a validation of existing packages in production. Is this such a major issue that the package should be replaced with an updated version?
(I have very little *read no* experience of the security settings in .NET)
Posted by:
brenthunter2005
19 years ago
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.