Detecting BAD code

Posted By: Minh | Nov 2nd @ 5:59 PM
page 2 of 2
Comments: 30 | Views: 442
#Nov 3rd @ 10:42 AM
PerfectPhase
PerfectPhase
"This is not war, this is pest control!" - Dalek to Cyberman

As I remember it was done with the debugger/tracing API on mono, which is very different from the windows version and easier to extend.

#Nov 3rd @ 10:53 AM
blowdart
blowdart
Peek-a-boo

Which is where CAS comes in - you're talking "minimal trust"

#Nov 3rd @ 11:02 AM
Minh
Minh
WOOH! WOOH!

I never fully understood CAS... I'm thinking I'd just use reflection and disallow code that makes references to certain assemblies... hammer/fly

#Nov 3rd @ 11:12 AM
blowdart
blowdart
Peek-a-boo

Even that's a bad move, you want to work from a white list, rather than a black list. If an assembly is referenced which is not on the list then you don't run the code.

 

The simple sandbox stuff is .NET 2.0. Code.

#Nov 4th @ 6:46 AM
Minh
Minh
WOOH! WOOH!

Thanks for the link... I'll be sure to check it out tonight

page 2 of 2
Comments: 30 | Views: 442
Microsoft Communities