在unix和windows中java可执行文件格式是什么

发布于 2024-08-16 11:06:32 字数 95 浏览 1 评论 0原文

我知道 class/jar 可执行格式。但是jar/class不能保证源码安全,因为java源代码(.java)可以从中检索。我正在寻找这样一种格式,其中源是安全/不可检索的。

I know about class/jar executable format. But jar/class can not ensure source security, because java source code(.java) can retrieve from it. I am looking for such a format where source are secure/un-retrievable.

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(2

仄言 2024-08-23 11:06:32

您无法确保代码免受逆向工程的影响。如果有权执行它,则可以在可以反汇编、反向编译或与已知程序集进行匹配的位置对其进行检查。

You can't make code secure from reverse engineering. If one has permission to execute it, then it can be examined where it can be disassembled, reverse compiled, or matched against known assemblies.

披肩女神 2024-08-23 11:06:32

如果您的计算机可以运行它,那么您就可以对其进行逆向工程。没有办法避免这种情况。您所能期望的最好的结果就是通过(例如)在编译之前将源代码通过混淆器来阻止随意破解。

IBM 通过他们的 type-4 JDBC 驱动程序做到了这一点,这使得理解正在发生的事情变得非常困难(直到你编写一个可以反混淆它的程序,尽管你仍然需要在函数和变量中添加信息)名字,这不是一件容易的事)。

默默无闻的安全永远无法对抗坚定的敌人。这与物理安全相同。你可以在你的房子里设置尽可能多的安全措施,这可以防止偶然的闯入,但它不会阻止顽固的窃贼。

我宁愿专注于做我最擅长的事情,提供一流质量的软件。大多数保护代码安全的尝试(除了简单的混淆)几乎总是对真正的客户造成比攻击者更大的不利。您的代码真的如此珍贵以至于您愿意冒这个险吗?

If your computer can run it, then you can reverse-engineer it. There is no way to avoid this. The best you can hope for is to stop casual cracking by (for example) passing your source through an obfuscater before compiling.

IBM did this with their type-4 JDBC drivers and it makes it hellishly difficult to understand what's going on (right up until the point you write a program that can de-obfuscate it although you still need to add information back in like function and variable names, no easy task).

Security through obscurity never works against a determined foe. This is the same as with physical security. You can put as much security in your house as you like, and that will prevent casual break-ins, but it will not stop a determined burglar.

I would rather concentrate on doing what I do best, providing top-notch quality software. Most attempts to secure code (beyond simple obfuscation) almost always disadvantages your real customers more than your attackers. Is your code really so precious that you want to risk that?

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文