|
|||
|
|||
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
||||||||||||||||
| Discussion on UPX - Usage - Three simple steps to localize - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support | |||||||||||||||||
| Author | Post | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
pipoman Member
|
I allow myself to start a new topic on UPX, since this could benefit many of us and possibly clarify a few things. The starting point was a wish that Sisulizer could someday handle UPX-compressed exe files transparently. Markus posted then an interesting comment: we have to be careful with this. According wikipedia (http://en.wikipedia.org/wiki/UPX) some authors use UPX to prevent reverse engineering. The part of the application Sisulizer reads for localization is meant to be read by third party. If a software author uses obfuscation to not allow that we have to respect that. While the software localizator in general is partnering with the software maker he should be able to get a program version open to be read by some localization tool. Perhaps the other software developers joining the forum have some opinion on this. Do you think we should respect obfuscation or should we go for the technically possible? Please share your thoughts with us. My personal use of UPX is file compression and that's basically it. I have absolutely no problem with someone unpacking my exe file, otherwise I would have used something which compresses and encrypt (http://www.aspack.com to name one), where reverse engineering is much, much more difficult.
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator 
|
Hi, my personal opinion is, if there is a (virtual) sign of some software developer saying "no trespasing" Sisulizer should respect that. What do the other developers here think about that? Best Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Jaakko.Salmenius Administrator 
|
The situation of UPX is a bit different because it is an open tool. The source code is public and they even hav API (although it is not very convinient). My opinion is that it is 99% compression only. Its purpose is to make EXE smaller not to protect them. It is just too easy to "break" it so it won't give any real protection agains reverse engineer. As I told in my provious email I added that to possible new features. However because there is a godo workaround (= applying SL for uncompressesed files) this is not currently high priority. Best regards, Jaakko Last edited on Tue May 15th, 2007 02:42 pm by Jaakko.Salmenius ____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Jaakko.Salmenius Administrator
|
I was playing around UPX a while I came up to an idea: We can use UPX command line tool to decompress file before localizing it. Then SL will localize the file and finally use the UPX command line tool to compress the localized files. We would not include UPX command line to SL setup but make SL to use if the user has the tool. Also the user has to tell SL that EXE has been compressed. There is not easy way for SL to detect that an EXE is UPX-compressed. SL finds that EXE is compressed or encypted if it fails to read the resource but it can not find out what is tool used. So what would you like about feature that SL could use UPX command line tool (if installed). Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
pipoman Member
|
Using SlMake is a good idea and a viable solution ... but I see 2 problems in that:
But well, let's not make this issue bigger than it is. Uncompressing the exe file before "importing" it in Sisulizer and compressing if afterwards in not that hard. It is nice to hear that Jaako has placed this item in a "possible new features" list though. Best regards
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator
|
For us it is important to show that we care for the concerns of all of our customers. Best Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Janusz Grzybek Super Moderator 
|
Any time ago I thought also about new add-on for decompress/compress files with UPX in the Sisulizer, but I didn’t posted this proposal on forum, because I think the Sisulizer users should to respect copyright law, and adding UPX feature could to provoke using the Sisulizer to make actions with copyright violation. Best, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| Current time is 07:18 am | |
| .NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > Discussion on UPX | |
Sisulizer software localization tool - Three simple steps to localize
