How to prevent the user to replace global cache assembly or show error if changed?

Question

1.00/5 (2 votes)

See more:

Dear All,
I have created one strongly named assembly and I installed in global assembly cache.
Then I added as a reference in my application. That results successful. After that I have created one assembly with same name and without strong name and manually deleted existing assembly from global cache and replaced with newly created assembly(without strong name). After I replaced application working fine.

My Question:
Application won't allow other assembly. if some one replaced with other assembly application should not run, how can I achieve that?

Posted 22-Oct-14 7:34am

Member 8310151

Add a Solution

Comments

PIEBALDconsult 22-Oct-14 13:40pm

That seems like an unreasonable level of paranoia.

Member 8310151 22-Oct-14 13:49pm

if you don't know then please keep quit. Anything is possible.

Sergey Alexandrovich Kryukov 22-Oct-14 14:47pm

"Anything is possible" is the most illiterate statement. Aha, and energy conservation law can be violated. Everything.

Now, please stop shutting up anyone. All people a free, no less free than you are, who allows yourself such rudeness. If you want to be rude, you can be reported and eventually loose your account. Please remember that.

As to your question, I can only repeat: this seems to be an unreasonable level of paranoia. (It means, some levels of paranoia can be considered reasonable, but this is well too much.)

Please take this reasonable advice and don't care about such thing. This advice will greatly help you in your work.

Good luck.
—SA

BillWoodruff 22-Oct-14 14:02pm

Can't you test somehow when your app starts if the assembly has a strong name ?

Member 8310151 22-Oct-14 14:07pm

is there any other way?

Sergey Alexandrovich Kryukov 22-Oct-14 14:50pm

This "someone" will also use strongly-named assembly; and it's not possible to put not strongly names assembly in GAC. So, this is not a right criterion. However, a private key would be different, which will be detected, but this problem is easily solved by reverse engineering followed by recompilation (with .NET, really, really easily).

Anyway, I think this question simply does not deserve a solution. I think, PIEBALDconsult and I already gave quite a reasonable advice, please see the comments above. Don't you think so?

—SA

BillWoodruff 22-Oct-14 16:17pm

I just can't keep quit when I don't know :)

Sergey Alexandrovich Kryukov 22-Oct-14 16:22pm

:-)

Member 8310151 23-Oct-14 0:09am

Then everyone know about you don't know anything :)..

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

johannesnestler · Answer 1 · 2014-10-22T23:31:00

In addition to the valueable comments you got - but ignored - it maybe interests you what's the problem in your conception of this "strong name thing" is.
The strong name stops you from having name collisions in the GAC - nothing more.
If you deleted it manually you must have seen what happens in this special "folder" - a directory with the strong name is created and your dll is put into it.
So a strong name is not a "security mechanism" in any way regarding the GAC.
(you can even replace .NET dll's - much fun if you replace mscorlib.dll on your coworkers computer).

Conclusion: Protect your Windows-System - if someone can replace dll's in your GAC you are allready vulnerable to all kind of "bad things"...

just my 2cents...

Sidtrey · Answer 2 · 2014-10-23T05:04:00

Solution 2

Easy, monitor the GAC directory(yes there is one), if any files change, throw an error.

That being said, this is a waste of programming, use domain policy instead.

Posted 23-Oct-14 5:04am

Sidtrey