On Fri, 8 Mar 2002, Nick wrote: > ok.. I got this proxy machine in our dorm, which has several > accounts.. and THREE users who got root access.. we manage to buy this > kewl PC with all these SCSI, DVD and MPEG / Radio card in it. > > It's just for use in our dorm... > > what makes me pissed off is.... I created this firewall script, which > I wrote by myself line by line.. but then one of the roots just copied > it for his works related stuffs without noticing me first.. he just > copy it , rename the script and make it like his work... Obviously he > knows none of " This is free but respect the original script writer "
Did the script have a license statement in it? If so, did it contain language which doesn't permit such utilization? If not, you've leared an important lesson on why licenses exist. > Is there any way I can make the scripts " a bit " unchangeable ? or > maybe it is not there when the system up, and then create the script > on the fly when the machine boot up ? ( we turn the proxy off during > classes, when no one is in the dorm ) Root access ensures being able to do anything. Scripts are text files, and therefore easily changable. You need to either not share administrator access or move to a compiled language (not that it would stop it, but it makes things much more challenging.) You could do things like shar archives to obfuscate the script, but it would likely make maintenance a pain and it's easy for anyone who's got half a clue to get around. > > I need input.... (assuming you're in the US[0]) Explain to the person that you automatically get copyright when you write a script, and they've violated your copyright. Ask them to credit you or stop using your script. You can do the same with their boss if they're not directly cooperative. Do it in writing, and keep copies of the documents. In most university settings, plagerism is strongly discouraged, and you may also have an ethics complaint to take to the university or other appropriate body. This is one of the inherrant risks in giving away source code. You can take one of several tacks- go after violators, not give away source code, realize that people will plagerize your work but it doesn't detract from your having done it, or act like it doesn't happen. Multi-level systems can stop the "multiple root" problem, but they're complex to set up and maintain. Virtual machines can do the same, but they don't offer the same level of "access." Not trusting untrustworthy people wins every time. Frankly, for most scripts, it's not worth the hassle of getting upset about. If you're mad though, make them stop using your script until it's restored to its original form- copyright should cover that much. Also, think about the fact that this person still has root access should they wish to be malicious. Paul [0] I am not a lawyer and don't play one on the Net, check with one to back up my limited understanding of the law. ----------------------------------------------------------------------------- Paul D. Robertson "My statements in this message are personal opinions [EMAIL PROTECTED] which may have no basis whatsoever in fact." _______________________________________________ Firewalls mailing list [EMAIL PROTECTED] http://lists.gnac.net/mailman/listinfo/firewalls
