.net-security

When running from a network share, my application throws the following exception: That assembly does not allow partially trusted callers. My application references two DLL files: BitFactory.Logging.dll FileHelpers.dll I'm not sure which one it is having problems with. AllowPartiallyTrustedCallersAttribute : Read up on it, but I do not have the source for either of the DLL files, so I'm not able to add the attribute to those DLL files. CASPOL.EXE : added my network share using a few variations, such as caspol -machine -addgroup 1. -url \\netserver\netshare\* LocalIntranet nothing seems to

Recently, our .Net client libaray is upgrading to compile against Net 4.0. After change the target framework to 4.0, the application has some compilation error. In AssemblyInfo.cs : [assembly: SecurityPermission(SecurityAction.RequestMinimum, Execution = true)] Error 7 Warning as Error: 'System.Security.Permissions.SecurityAction.RequestMinimum' is obsolete: '"Assembly level declarative security is obsolete and is no longer enforced by the CLR by default. See http://go.microsoft.com/fwlink/?LinkID=155570 for more information."' ` In .Net 4.0, it shows that: SecurityAction.RequestMinimum as

I use RSACryptoServiceProvider to encrypt some small blocks of data. For the solution I'm working on, it's important that if the same piece of source data is encrypted twice with the same public key, the result (the encrypted block of data) is not the same. I have checked this with an example and it worked like I hoped. My question is now, if this behaviour is by design and guaranteed or if I have to add some random part to the source data for guaranteeing that data blocks with the same data can not be matched anymore after encryption. Here is the example: byte[] data=new byte[]{1,7,8,3,4,5};