• 0

dumb question, how to i close source?


Question

11 answers to this question

Recommended Posts

  • 0

Well, Java is rather easy to decompile, so if you rely that much on lack of easy code extraction... You're basically screwed with Java.

Afaik at least.

I could be wrong.

Glassed Silver:mac

  • 0

Java compiles to bytecode which can be rather easily converted back into readable source code with a free tool like this. Java isn't meant for keeping your source code secure and even if you use C++ someone sufficiently dedicated will manage to reverse-engineer your code if they want to. I'm not trying to be offensive, but if you have to ask this question you probably aren't writing anything that would be worth someone's time to try to steal anyway at the moment. Just write your program, practice and don't worry about people decompiling your code because anything you do can only make it slightly harder for them, not stop them.

  • 0

Java compiles to bytecode which can be rather easily converted back into readable source code with a free tool like this. Java isn't meant for keeping your source code secure and even if you use C++ someone sufficiently dedicated will manage to reverse-engineer your code if they want to. I'm not trying to be offensive, but if you have to ask this question you probably aren't writing anything that would be worth someone's time to try to steal anyway at the moment. Just write your program, practice and don't worry about people decompiling your code because anything you do can only make it slightly harder for them, not stop them.

I do not take you comment offensively but I am making encryption programs and I am simply exploring methods to ensure no reverse engineering of the encrypted data can happen (or happen with extreme ease)

  • 0

Could look into an obfuscator. Not 100% foolproof(if somebody wants to decompile your code they will, there are no magic bullets for software protection) but certainly makes it a bit tougher.

  • Like 1
  • 0

I do not take you comment offensively but I am making encryption programs and I am simply exploring methods to ensure no reverse engineering of the encrypted data can happen (or happen with extreme ease)

Pure Java doesn't seem like a too great idea for me here.

Glassed Silver:mac

  • 0

I do not take you comment offensively but I am making encryption programs and I am simply exploring methods to ensure no reverse engineering of the encrypted data can happen (or happen with extreme ease)

A good encryption method is hard to break even if the attacker knows exactly how it works. Obfuscating your source code will NOT improve the strength of the encryption it performs. Everyone knows how AES works, for instance, yet no one can break it. The program TrueCrypt is open-source yet it is widely used to secure sensitive data and is considered secure.

Security comes not from obfuscation of algorithms but from the time it would take an attacker to break the encryption.

  • Like 3
  • 0

A good encryption method is hard to break even if the attacker knows exactly how it works. Obfuscating your source code will NOT improve the strength of the encryption it performs. Everyone knows how AES works, for instance, yet no one can break it. The program TrueCrypt is open-source yet it is widely used to secure sensitive data and is considered secure.

Exactly, encryption should be provably difficult to calculate the reverse of some function. Don't rely on security through obscurity, use logic and proofs!

  • 0

There is no such thing.

You can make it harder yes, if you want to completely stop people from knowing how your program works well then the best and only way I can see to do that is release your program in a non-working state.

If a computer can read and execute it, so can a human (with some effort/tools/hassle)

  • 0

I do not take you comment offensively but I am making encryption programs and I am simply exploring methods to ensure no reverse engineering of the encrypted data can happen (or happen with extreme ease)

A good encryption method is hard to break even if the attacker knows exactly how it works. Obfuscating your source code will NOT improve the strength of the encryption it performs. Everyone knows how AES works, for instance, yet no one can break it. The program TrueCrypt is open-source yet it is widely used to secure sensitive data and is considered secure.

Security comes not from obfuscation of algorithms but from the time it would take an attacker to break the encryption.

This!

OP, forget it, code obfuscation is not about protecting data, it's about making it harder for other programmers to copy your code. As Asik said above, just simply encrypt your data, and for f-sake don't create your own encryption algorithm, use something standard.

This thread is pointless, lets return conversation to your other thread or make a new one on the lines of 'help me design a secure chat client'.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Payday TWO!! Is 13 years old man I feel old - I remember trying it out and if I did not know I would say 5-6 years ago or something
    • Payday 2 engine upgrade adds 64-bit and DX11 support, drastically shrinks install size by Pulasthi Ariyasinghe Payday 2, the most popular entry in the heisting game franchise, is getting a surprising update after all these years. This is slated to be a complete engine upgrade that will enhance almost every aspect of the 13-year-old title, targeting performance, loading times, file size, rendering backend, and more. Developer Sidetrack Games is planning a beta to test out the new version ahead of the full public launch. The development team today revealed that the long-awaited upgrade to the 64-bit architecture is happening with this Diesel 3.0 engine update. By letting the game use more ram than 4GB, it is said to improve stability and compatibility on most hardware. It should also help modders in the long term with implementing larger changes too. "While many of the changes are made on the backend and not everything will be visible to you guys because it is a massive rewrite of the entire codebase, there will be a lot of things that you can look forward to," Sidetrack explained. Payday 2 will also hop over from DirectX 9 to 11. Instead of visual improvements, this is slated to reduce the amount of VRAM used by the title, letting more lower-end hardware access the title and run it better. Since these changes would require a complete redownload of the game anyway, Sidetrack says it has revamped "the game's packaging and bundling system." This should reduce the installation size from 86GB to 32GB. "So, now it's time to finally move the game to your SSDs," added the studio. The Payday 2 Diesel Engine 3.0 update is entering open beta on June 30 for Steam users. No console release plans were announced today. Sidetrack Games says it has been working on this complete rewrite of the codebase for the last nine months. While these changes should break most mods, the studio encouraged modders to use the beta period to repair their creations with support from the development team.
  • Recent Achievements

    • Week One Done
      Scoobystu earned a badge
      Week One Done
    • Week One Done
      tuben earned a badge
      Week One Done
    • First Post
      OffsetAbs earned a badge
      First Post
    • Reacting Well
      OffsetAbs earned a badge
      Reacting Well
    • First Post
      Kolakid60 earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      439
    2. 2
      +Edouard
      196
    3. 3
      PsYcHoKiLLa
      156
    4. 4
      FloatingFatMan
      71
    5. 5
      Steven P.
      68
  • Tell a friend

    Love Neowin? Tell a friend!