Re: Trust An Assembly (With Updates)

From: Jason Garland \(Secure Access Pty Ltd\) (Jase_at_SecureAccess.Com.Au)
Date: 10/24/03

  • Next message: casey chesnut: "Re: Verify signature unsing X509Certificate" 
    Date: Fri, 24 Oct 2003 08:42:20 +1000

    Thats Great

    2 Quick Questions.

    a) Do you know of away of doing this via CASPOL or some other scripting ?

    b) Do you know if this can be pushed out in Dot Net Security (from Server to
    Clients)

    With THanks

    Jase

    "Dave Jefferson" <david.jeffersd@REMOVETHISkbcfp.com> wrote in message
    news:oprxh5hvhahnd987@news.microsoft.com...
    > The simplest thing to do is:
    > 1. Generate a strong name key pair using "sn -k myKey.snk"
    > 2. Get your application to use this (in the AssemblyInfo.cs file)
    > 3. Run C:\WINNT\Microsoft.NET\Framework\v1.1.4322\mscorcfg.msc (assuming
    > you are using v1.1 of the framework)
    > 4. Runtime Security Policy -> Increase Assembly Trust. Choose your
    > assembly and in the next dialog pick the option "All assemblies with the
    > same assembly public key"
    > 5. Choose the security level
    >
    > Now any version of any application which is signed with myKey.snk can run
    > on this PC.
    > If you want to deploy your application to other PCs then choose Runtime
    > Security Policy -> Create Deployment Package and thne deploy the resulting
    > msi package to all PCs in your company.
    >
    > What we do is my development group has it's own key and we sign all our
    > assemblies with that key and all the PCs in my company have their security
    > policy adjusted so trust that key.
    >
    > Hope this helps,
    >
    > Dave
    >
    >
    >
    > On Thu, 23 Oct 2003 18:07:05 +1000, Jason Garland (Secure Access Pty Ltd)
    > <Jase@SecureAccess.Com.Au> wrote:
    >
    > > Does anyone know of a method to allow an Application (not a specific
    > > version
    > > or build) to be allowed to be trusted with full rights ?
    > >
    > > Sort of a Registration of a Certificate, and any app that is signed with
    > > that certificate (regarless of name or build) is right to run ?
    > >
    > > Any thoughts would be great.
    > >
    > >
    >
    >
    >
    > --
    > Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/

  • Next message: casey chesnut: "Re: Verify signature unsing X509Certificate"

    Relevant Pages

    • Re: Code Access Security Enforcement anamoly - - Thx in advance.
      ... If we look at the documentation and security changes since v1.0 of .NET, ... so that any assemblies under that website would be considered as fully ... > Hi Shawn, ... >> You are probably running into a situation with dynamic compilation. ...
      (microsoft.public.dotnet.security)
    • Re: Am I the only one with doubts about .NET for commercial apps?
      ... > So far, I have found only these two weaknesses, but these are BIG ... harder to do in unmanaged code, no licensing restrictions you add there are ... sense of security by making it clearer how easy it is to do. ... You can make reusing your assemblies a bit harder by using identity demands, ...
      (microsoft.public.dotnet.general)
    • RE: Decleration Excel.Application or what
      ... security error when you call into the NanoSort class. ... When you create and build your VSTO project a .NET security policy is ... assemblies reside rather than just the VSTO assembly and this should correct ...
      (microsoft.public.vsnet.vstools.office)
    • Re: access to Server 2K3
      ... I suggest you enable and apply security ... Jason Tan ... Microsoft Online Partner Support ... |> | All works fine with PCs that are in my domain and also for PCs the ...
      (microsoft.public.windows.server.migration)
    • RE: Windows Service cannot create text files?
      ... should know that running your service as the Local System account is Very ... If your service has a single security flaw that is exploited, ... The steps for changing the policy for the user ... This will import the strong name and only assemblies ...
      (microsoft.public.dotnet.languages.vb)