Frequently Asked Questions for RTEncoder 2.x

1. What is RTEncoder?

RTEncoder is a software utility used to protect computer files. The purpose of this application is to allow a user to protect a computer file by encoding it into an RTE file. Then the RTE file would be sent to another user who would use RTEncoder to decode the RTE file back into the original computer file. The goal is that while protected in the RTE file, the original computer file can not be decoded by a user who is not authorized to view that file.

Several methods are available in RTEncoder to protect your source computer files. One such method is to use Key files to encode the original file, such that the identical Key files are needed to decode the RTE file. This process works by the encryption algorithm called a One-Time Pad. A similar approach is available in RTEncoder called a Key Phrase. In this case, a short phrase is used to generate a random stream of data which is used in a similar manner to a Key File.

Another protection method available in RTEncoder is the Blowfish encryption algorithm. When Encoding an RTE file, entering an Encryption Phrase will make use of a 64-bit symmetric encryption algorithm using the Blowfish standard. When Decoding, the user will need to know the Encryption Phrase to successfully decode the RTE file.

A final feature available in RTEncoder is the ability to use Compression on the source file, before the Encoding begins. This extra step will not only help make the output RTE file smaller, but it can add a measure of security by obfuscating the contents of the original file, making brute force attacks on an encoded RTE file more difficult. The compression is done using the standard GZip compression algorithm.

2. What platforms does RTEncoder 2.0 support?

RTEncoder 2.0 runs on Microsoft Windows XP and Vista.

3. Where can I download the Microsoft .Net Framework Version 2.0 Redistributable Package?

RTEncoder requires your Windows machine to have .Net 2.0 installed. You can download this package from Microsoft at: http://www.microsoft.com/downloads/details.aspx?FamilyID=0856EACB-4362-4B0D-8EDD-AAB15C5E04F5&displaylang=en

4. Can I decode RTEncoder 1.x RTE files with RTEncoder 2.0?

Yes. RTEncoder 2.0 can decode RTE files encoded with RTEncoder 1.x.

5. Why is encoding disabled in the version of RTEncoder I downloaded?

RTEncoder 2.0 requires the purchase of a license to enable the encoding feature. You may purchase a license at: http://www.rtencoder.com/purchase.

6. Why should I purchase a license for RTEncoder?

The unlicensed version of RTEncoder is only able to decode RTE files. If you need to encode an RTE file, you will need to purchase a license. If you only need to decode RTE files, then you do not need to purchase a license.

7. What happens after I purchase a license?

After your purchase, you should be emailed a small license file that you need to save to your hard drive. Then, inside RTEncoder, select the Help, Register License menu item. A standard File Open dialog will be launched for you to select the license file you saved to your hard drive. If the license file is validated by the software, you should notice the title of the RTEncoder window change to reflect your newly license software. You will also see the license details in the Help, About dialog box.

8. Who uses RTEncoder?

RTEncoder was originally developed for use in the Poser third party developer community as a way of protecting the copyright of 3d content creators while still allowing other developers to create new content based on copyrighted work. By encoding the derivative content into an RTE file that requires the original copyrighted content to decode the RTE file, the original copyright holder’s rights are protected against improper distribution of their original content.

Frequently Asked Questions for RTEncoder 1.x

1. Is there a Macintosh version of RTEncoder available?

No. There is no Macintosh version available for RTEncoder version 1.01.

2. Can I encode against multiple key files?

No. Version 1.01 of RTEncoder can only encode against a single key file. The current solution is to use multiple rounds of encoding. Basically, encoder your source file against file “key1″. Then, encode the resulting RTE file against “key2″. You can distribute your second RTE file. Remember, they must be decoded in the proper order.