Perl just doesn't lend itself to this sort of protection. Given the headaches of maintaining compiled and/or obfuscated perl code, I suggest you at least consider a non-technological solution: you can write whatever restriction you want into the contract with your client, and contract law is much easier to enforce than copyright and intellectual property law. Alternatively consider offering the site as a service (you host it),
On Dec 16, 2007, at 10:41 AM, namotco wrote: > No, this isn't what I mean at all. > > I have a Mason site. I want to give it to someone else to put on > their own server, but I don't want them to see the perl code. > Instead I want to compile perl (or do something to it) so that they > can not change the site and any changes would have to be made by me > since I retain the original perl source (which would require > recompiling after I made the changes...). > > Sorry if there was some confusion about what I meant. > > > Ryan > > > On Dec 15, 2007, at 10:21 PM, Raymond Wan wrote: > >> >> Hi, >> >> namotco wrote: >>> Of course. I'm trying to prevent people from accessing my code >>> that I give the Mason site to. >>> >>> Can anyone provide some more insight? >>> >> >> I'm not sure if this works and in fact, I have a question myself >> about this :-), so if anyone has any suggestions, I'd like to hear, >> too. At the moment, I added this into my Apache2 httpd.conf: >> >> <FilesMatch "(\.mhtml|\.mtxt|\.mpl|dhandler|autohandler|syshandler) >> $"> >> SetHandler perl-script >> PerlHandler Apache2::Const::NOT_FOUND >> </FilesMatch> >> >> So, any direct requests for these file extensions will return a 404 >> error. I also made html files such as index.html which are a few >> lines long and simply call another component. That is, index.html >> can call form.mhtml, but a direct request for form.mhtml won't >> work. And if Mason is set up correctly to compile the html file, a >> request for this html file will result in html code and no Mason >> code. >> >> Is this what you mean? >> >> I only have one problem and if anyone else can tell me what is >> wrong, please let me know... In my forms, I send a post request to >> say "process.html". I'd like to give it a mhtml extension, etc. to >> prevent someone from accessing it directly, but then the post >> request doesn't work. i.e., my desire to prevent access to .mhtml >> files has bitten me when it comes to forms...thus, the form has to >> have an html extension. Since HTTP is stateless and a request to >> index.html is no different to process.html with POST data, I see no >> way around this one other than the fact that process.html will have >> its Mason code compiled. >> >> Sorry...a bit off topic from your original problem! >> >> Ray >> >> > > > ---------------------------------------------------------------------- > --- > SF.Net email is sponsored by: > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services > for just about anything Open Source. > http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/ > marketplace > _______________________________________________ > Mason-users mailing list > Mason-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/mason-users > ------------------------------------------------------------------------- SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ Mason-users mailing list Mason-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mason-users
