469,134 Members | 1,315 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,134 developers. It's quick & easy.

Strong Name Security Policy Addgroup Error

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
Jul 21 '05 #1
1 1876
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
"Rob Barnes" wrote:
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

Jul 21 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

6 posts views Thread by NormD | last post: by
7 posts views Thread by Tim Bücker | last post: by
reply views Thread by virgo81 | last post: by
1 post views Thread by Rob Barnes | last post: by
8 posts views Thread by per9000 | last post: by
1 post views Thread by CARIGAR | last post: by
1 post views Thread by Mortomer39 | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.