モヤチヤリナ <PGEPJIFLPEPOHCKEEEIKOEMDDCAA.james / rubyxml.com> james / rubyxml.com ホチミノモチフ(チ):

>> If the computer is able to "decrypt" the code to the point of
>> executing it, it's more than likely that there's enough "stuff" there
>> to get a somewhat meaningful disassembly.  That is what seems to have
>> happened with Java; people distribute "jars," and the disassemblers
>> produce not incredibly horrid Java code.
>>
>> And keep in mind: The dishonest customers that would use the code
>> illicitly and not pay for it aren't people you want to do business
>> with, anyways.
> 
> One possible reason to encrypt the source is to guard against
> well-intentioned but unskilled employees.  If a company is internally
> deploying an application, they may prefer that users not "improve" the
> code.  It reduces support calls.  This may apply to external customers as
> well.  Support may be easier if you can be assured up front that the source
> code hasn't been altered.  (I know you can check this anyway, but if the
> source is encrypted it may be one less thing to spend time on.)

	'tar', 'md5' and 'diff' should help here.