Ask HN: 如何在“后神话”时代处理桌面应用程序的安全性？
1 分•作者: Archit3ch•4 个月前
最近，有人声称安全问题最终变成了比对方投入更多资源的较量：https://news.ycombinator.com/item?id=47769089
无论这种说法是否成立，您将如何处理现代桌面应用程序的复制保护问题？我特别担心攻击者能够利用前沿的 LLM（大型语言模型）来分析闭源二进制文件并发出“破解它”的指令，而这在过去可能需要数月的时间。以下是假设条件：
1. 出于延迟方面的考虑，该应用程序必须是原生应用程序，不能是 SaaS（软件即服务）。
2. 攻击者只需成功一次即可。
3. 目标是机器锁定的许可证，未经明确停用，无法转移。
4. 激活（例如，在安装期间）可以联网进行，但应用程序需要完全离线可用。这意味着在运行时不能通过回拨服务器进行检查。
查看原文
Recently, there are claims that security is a matter of spending more tokens than the other side: https://news.ycombinator.com/item?id=47769089<p>Regardless of validity, how would you handle copy protection for a modern desktop app? I'm especially concerned about the attacker being able to point a frontier LLM at a closed source binary and saying "crack it", when it used to be a months-long effort. Assumptions:<p>1) The app has to be native for latency reasons and cannot be a SaaS.<p>2) The attacker only has to win once.<p>3) The goal is machine-locked licenses that cannot be transferred without explicit deactivation.<p>4) Activation (e.g. during installation) can be online, but the app needs it's entire functionality available offline. This means no checks by phoning back to a server during runtime.