Strong Name Security Policy Addgroup Error

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

When I try to create a machine-level security policy based on an assembly's
strong name, I get the following error:

"ERROR: Invalid label or name"

The caspol command is:

"caspol -machine -addgroup All_Code -strong -file \\<network_share>\app.exe
-noversion"

I've tried several variations of the command, all with similar results,
including using "1." as the parent_label and using a local assembly.

I'm using .NET Framework version 1.1.4322.573.

Thoughts?

Thanks,
Rob
 
User error. My "All_Code" group had at some point been renamed to "All
code". Now this brings me to my next question. I'd like to be able to
create a security policy based on an assembly's strong name. The challenge
is that the file may not be present at the time the policy is created. Is it
possible to create this policy using the assembly's public key (which is
known at policy creation time)?

Thanks,
Rob
 
Back
Top