Who are you?
We are Barebit, a registered company based in EU, Czech Republic.
I doubt if it is safe to upload my APK.
First of all, we are not interested in your APK. It is removed from our servers shortly after you downloaded your protected APK.
To make sure we won't publish your APK on your behalf we strongly recommend you to remove the <apk>/META-INF
directory before it is uploaded. The APK file is actually a ZIP file. Just unpack it, remove the directory and pack it again.
Where can I download Bytor?
The protector can't be released as a client application because it would be soon exploited by malware to hide
itself from anti-virus scanners. You can use Bytor only through its web interface.
I doubt if the Bytor protection is stable enough.
Bytor has been well tested in the wild because it already has hunders of thousands instalations. For obvious reasons,
we can't disclose what games are protected with Bytor.
How much FPS will my game loose because of the protection?
The protection doesn't slow down your code at all. You won't loose any FPS.
Is Bytor just another .NET obfuscator?
It is much more than an obfuscator. It uses previously unseen approach to protect code running on Mono.
Get the trial license
and try it yourself.
Is the protection unbreakable?
Nothing is unbreakable. However, Bytor provides real protection that takes huge effort to be circumvented.
I don't need protection, IL2CPP is coming to protect my code.
Sad to say, IL2CPP doesn't work like a code protection. Your compiled .NET bytecode can be decompiled easily
because of .NET metadata. These metadata are generated by IL2CPP as well. This means IL2CPP adds only a small
barrier. Your code can be decompiled to C-language code that is not hard to read. The game modding community
is strong and always find ways to break your code, unfortunately.
Does Bytor work with IL2CPP?
Bytor works only with Mono runtime. We don't recommend IL2CPP without protecting the generated code that can
be easily cracked as well.
Do you support my Unity3D version?
Bytor supports versions 4.6, 5.0, 5.1, 5.2 and 5.3.
How do I sign the protected APK?
You need to sign the protected APK again because Bytor (or you) had to remove your certificates (the META-INF
directory) from the APK. The signing provides jarsigner
from Java Development Kit (JDK). If you are
not sure about your JDK location, check the JAVA_HOME
environment variable that is usually set to the
JDK installation path.
Use the following command:
jarsigner -storepass <your password> -sigalg SHA1withRSA -digestalg SHA1 -keystore <your keystore file> <apk file> <alias name>
- storepass: password that protects your keystore
- sigalg and digestalg: these values are recommended by Google
- keystore: the file with your keys; by convention, Android Java keystore has "keystore" extension
- alias: name of the key stored in the keystore
Check if the APK is signed:
jarsigner -verify -verbose -certs -keystore <your keystore file> <apk file>
Detailed help is available in Oracle Documentation
. Learn more in Android documentation
The last step is alignign your APK with zipalign. It is a part of Android SDK, located in <sdk>/build-tools
directory. Use the following command:
zipalign -v 4 <signed apk file> <output apk file>
- v: verbose output
- 4: alignment in bytes; this value is recommend by Google
Check if the APK is aligned:
zipalign -c -v 4 <aligned apk file>
Learn more about zipalign in Android documentation