Ok, I misunderstood that then. Another option: - download the language pairs using the app (the way it's done now) - compute a hash value (e.g. SHA) and store it in app memory, where it cannot be changed by other apps, but store the actual data on SD card - refuse to use the data if the hash value does not match
This option should allow for practically the same level of security that the app has now. Am 27.10.2014 um 18:53 schrieb Mikel Artetxe: > > We are talking about lttoolbox-java, and not C++ lttoolbox/apertium. In > the Java version transfer rules are not interpreted but compiled into > Java/Dalvik bytecode, which is then invoked dynamically. See > http://wiki.apertium.org/wiki/Bytecode_for_transfer for more details. > > The mobile app uses precompiled bytecode, so if we store it in the > external storage and some kind of malware modifies it, the app would > invoke that modified and potentially malicious bytecode. As far as I > know there is no way to solve this problem other than using cryptography. ------------------------------------------------------------------------------ _______________________________________________ Apertium-stuff mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/apertium-stuff
