on Mon, 2 Jan 2006 Eric Chatonet wrote: > You can compress the images, decompress them on-the-fly, > clear files extensions and put them with non meaningful > names in a folder named data :-) > Most users won't be able to open them...
and if you really want to hide, obfuscate and deceive your files, you could switch the position of two or more bytes in the binary data of your files, for example: If your file named "DoNotOpen.zxc" had the character 50 and 51 like these: %* you could write a function that revert the position of these character like these: *% and later for opening the file you restore them to their original position: %* Notice that you could do the same with many bytes (characters), not only using 2 characters. You had to test how many char swaps works better to lock your files. i had wrapped binary files (like sounds, images and stacks) with two encrypted md5digests, one for the file uncompressed and other for the compressed file. Of course, it's necessary to use a script in RR to unwrap, verify, decompress and open these files. al Visit my site: http://www.geocities.com/capellan2000/ __________________________________________ Yahoo! DSL Something to write home about. Just $16.99/mo. or less. dsl.yahoo.com _______________________________________________ use-revolution mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
