With a Catch-22, of course, there's no way out. You're stuck. A Catch-21, on\nthe other hand, is one level down in severity and therefore may be exited by\nthe clever and crafty. I believe this to be one such situation.\n\nSo here's the problem...\n\nI'm putting the finishing touches on the licensing for a custom server\ncontrol I've built for sale to whomever might be interested and feel that\nit's good value for the money. Naturally folks are going to be running it in\nshared hosting environments, which traditionally run under partial trust\n(and wisely so).\n\nI want to prevent piracy, and so I was thinking about tying each license to\na specific machine, via CPU serial number or something like that. Trouble\nis, that sort of info is retrieved via WMI, which of course requires full\ntrust. So that's not an option.\n\nAm I stuck with leaving myself open to people copying the assembly and\nlicense file to any machine at will? I sure hope not...\n\nThanks ahead for any ideas.