[osflash] Obfuscators
Infos E-Blokos
infos at e-blokos.com
Wed Jun 4 11:02:23 PDT 2008
Shaking, hiding and obfuscating is pretty enough to protect your code from
decompiler
look at www.flashuploaded.com
Franck Chionna
----- Original Message -----
From: "zwetan" <zwetan at gmail.com>
To: "Open Source Flash Mailing List" <osflash at osflash.org>
Sent: Wednesday, June 04, 2008 1:11 PM
Subject: Re: [osflash] Obfuscators
> >
>> I see. I don't think that would be a suitable alternative to obfuscation.
>>
>> For one thing, it requires a great deal more effort. Second, it puts the
>> burden on the client to run the decryption on their machine (every time
>> they access the swf). Finally, since you must provide the client with the
>> key, you haven't really protected anything, you've just added one extra
>> step.
>>
>
> effective solution require effort in general
>
> you can protect the key too
> simple example: if the SWF run within AIR you can use the encrypted
> storage
> to save the key but without exposing it in the source code that could
> be generated from decompilation
> but yes you're right is much more difficult to put in place,
> hence why you see very few people doing it right
>
> it's not just an extra step that is useless, with encryption done right
> you can have your encryption algorithm source code exposed on the wild
> and your crypted file still stays secure
>
> the only thing I was saying is that depending on your use case
> obfuscation is not the end-all be-all , encryption is there too,
> as steganography, etc.
>
> zwetan
>
> _______________________________________________
> osflash mailing list
> osflash at osflash.org
> http://osflash.org/mailman/listinfo/osflash_osflash.org
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
More information about the osflash
mailing list