您使用什么复制保护技术?

发布于 2024-07-13 09:14:26 字数 766 浏览 7 评论 0原文

我正在考虑为我的一个工具添加某种复制保护。

  • 你有这方面的经验吗?
  • 您是否开发了自己的保护技术或购买了第 3 方软件?
  • 您认为这是增加销量的可行方法吗? (在私人和/或公司环境中)
  • 您如何防止打扰您的付费客户? 在大多数情况下,付费客户会遭受糟糕的版权保护,我不希望这种情况发生在我的客户身上。 (即使这意味着接受一些贪图便宜的人)

我对允许私人使用软件的试用版或免费软件版本但限制其在企业环境中的实用性的技术特别感兴趣。


相关问题您如何保护您的软件免遭非法分发
相关问题保护 .NET 代码免遭逆向工程。< /a>
相关问题
防止规避复制保护。

I'm thinking about adding some kind of copy protection to one of my tools.

  • Do you have any experience with that?
  • Have you developed your own protection techniques or did you buy 3rd party software?
  • Do you think it is a viable method to increase sales? (In a private and/or corporate environment)
  • What do you do to prevent hassling your paying customers? In most cases it's the paying customers who suffer from a bad copy protection, and I don't want this to happen to my customers. (Even if that means accepting some freeloaders)

I'm especially interested in techniques which allow a trial or freeware version of your software for private use but limit the usefulness in a corporate environment.


Related Question: How do you protect your software from illegal distribution
Related Question: Protect .NET code from reverse engineering.
Related Question: Prevent the circumvention of copy protection.

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

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

发布评论

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

评论(9

清风夜微凉 2024-07-20 09:14:27

无论您使用什么技术,您的软件都会被复制。 版权保护的实际目的是防止诚实的客户受到不公平的诱惑。

最低限度的复制保护技术就足够了。 最多不值得花费时间。

此外,我听说一些开发人员会向任何提出请求的用户(无论是否是客户)提供用户支持。 这个想法是快乐的用户可能成为忠实的客户。

Whatever technique you use, your software will be copied. The actual aim of copy protection is to prevent honest customers from being tempted to be unfair.

The minimum copy protection technique is enough. The maximum is not worth the time spent.

Moreover, I've heard that some developers provide user support to any user who asks, customer or not. The idea is that happy users may become faithful customers.

为你鎻心 2024-07-20 09:14:27

在桌面应用程序上,我一直在使用 Clarion 模板(3rdParty,http://www.capesoft.com /accessories/secwinsp.htm)。

对于网络应用程序,几乎只是使用用户必须登录的简单事实并跟踪活动。 如果他们有账户,就意味着他们已经付款。

桌面版更难追踪。 正如已经说过的,很容易破解。 非常典型的情况是:

让黑客感到烦恼,但对用户来说尽可能不引人注目

On desktop apps I've been using a Clarion Template (3rdParty, http://www.capesoft.com/accessories/secwinsp.htm).

With web apps, pretty much just been using the simple fact that the User has to log in, and tracking the activity. If they have an account, it means they've paid.

Desktop is a lot harder to track. As has been said, very easy to crack. Very much a case of:

Make it annoying for the Hackers, but as unobtrusive as possible for the Users

狂之美人 2024-07-20 09:14:27

“硬件就是加密狗”

这是我们在以前的工作中经常说的一句话,在某种程度上,这在我现在的工作中也是如此。 基本上,我们出售物理硬件来运行我们的软件,并免费赠送这些软件。 这可能不适用于所有企业,但知道您不必担心盗版是一种很好的感觉,因为人们投资于硬件,而不是软件。

"The hardware is the dongle"

That was what we always said at my old job, and to some extent, it's also true at my present one. Basically, we sold physical hardware to run our software, which we gave away for free. This probably isn't feasible for all businesses, but it's a nice feeling to know you don't have to worry about piracy, because people are invested in the hardware, not the software.

梦里泪两行 2024-07-20 09:14:27

正如莫维希尔所说,没有什么是完美的。 旨在温和地鼓励可能购买您产品的用户购买它,而忘记那些永远不会购买的人。

一些一般性提示:

  1. 不要费心实施自己的保护,除非您有这样做的经验。 在这个领域,向专门提供某种类型的许可/保护的人付费可能是值得的(请记住,它不会是完美的)。
  2. 选择难以注册的许可证密钥系统。 同样,选择预构建的许可系统可能就足够了。 从头开始创建自己的产品可能不会。
  3. 花时间正确集成您选择的任何许可系统。 如果您只是“保护/包装”您的可执行文件,保护将很快被删除。 大多数许可/保护产品都提供简单的集成工具/宏,这使得自动破解变得更加困难。

对于企业软件,您能做的最好的事情就是让管理员轻松确保它们在许可证范围内(实例/安装数量等)。 为他们提供一个中心位置来验证这一点,并在他们采取任何更激烈的行动之前温和地提醒他们,如果他们稍微有些过分的话。 在大型网络环境中,软件许可对于 IT 部门来说可能会变得非常复杂。 让他们的工作变得更轻松,他们会感谢你。

As mouviciel mentioned, nothing is perfect. Aim to gently encourage users who might buy your product to buy it, and forget about the people who never will.

Some general tips:

  1. Don't bother implementing your own protection, unless you have experience doing so. This is an area where paying someone who's specialty is providing some type of licensing/protection is probably worthwhile (just keep in mind it won't be perfect).
  2. Choose a license key system that is difficult to keygen. Again, picking a pre-built licensing system will likely suffice. Creating your own from scratch will likely not.
  3. Take the time to properly integrate whatever licensing system you choose. If you just "protect/wrap" your executable(s), the protection will quickly be removed. Most licensing/protection products offer easy integration tools/macros that make automated cracking much more difficult.

For corporate software, the best thing you can do is make it easy for administrators to ensure they are within the license boundaries (# of instances/installs, etc.). Provide a central place for them to verify this, and gently remind them if they go slightly over, before you take any more drastic actions. In a large network environment, software licensing can get very complex for the IT dept. Make their job easier and they'll thank you.

海未深 2024-07-20 09:14:27

“技术支持就是加密狗”

这并不适用于所有应用程序,但对于价格较高且销量较低的复杂应用程序,为您的客户提供出色的支持是确保所有用户付费的最佳方式。

"The technical support is the dongle"

This doesn't apply to all applications, but for complex applications with higher price and lower sell volume, providing excellent support to your customers is the best way to be sure all your users are paying.

风尘浪孓 2024-07-20 09:14:27

我知道这篇文章是很久以前提交的,但当讨论这个话题时,每个人总是显得那么消极。 出于显而易见的原因,我不想透露我在哪里工作,但我们使用 Wibu-Systems US 的 CodeMeter< /a>. 我们选择这个是因为黑客在黑客竞赛中未能成功破解它。

对于您提出的所有问题,它非常灵活,并且他们提供免费的SDK,这就是我们在购买之前进行测试的方式。

I know this post was submitted quite some time ago, but everyone always seems so negative when this subject is discussed. For obvious reasons I prefer not to say where I work but we use CodeMeter by Wibu-Systems US. We chose this as hackers didn't manage to hack this during a hacker competition.

Regarding all the questions you ask, it is really flexible and they offer a free SDK, which is how we tested before we purchased.

冰火雁神 2024-07-20 09:14:27

对于某些产品,我们(必须)使用硬件加密狗。 尽管它们提供了相当好的复制保护,但对我们的客户来说却是一个真正的麻烦。

所有其他软件均受软件密钥保护。 是的,你可以复制这些。 但我们有很好的经验,客户不会这样做。
如果没有按键,程序可以正常工作,只是无法计算模型并且某些打印功能被禁用。

For some products we (have to) use hardware dongles. Although they give a prety good copy protection, they are a real hassle for our customers.

All other software is protected by a software key. And yes you can copy those. But we have very good experience that customers don't do that.
Without a key a program works normal, only you can't calculate the model and some print functions are disabled.

清醇 2024-07-20 09:14:27

您确实需要对您的软件采用复制保护,但正如其他人所说,请尽可能让您的客户无忧无虑。 您的目标应该是让诚实的客户保持诚实,而不是让他们在最终使用您的软件之前经历困难。

我还建议不要将时间花在制定自己的许可方案上,而是将时间花在实际产品上。

考虑使用 CryptoLicensing - 它提供许可、复制保护、激活、机器锁定、试用和其他功能。

免责声明:我在 LogicNP Software 工作,该公司是 CryptoLicensing 的开发商。

You do need to employ copy-protection for your software, but as others have said, make it as hassle-free as possible for your customers. Your aim should be to keep honest customers honest, and not make them go through hoops before they can finally use your software.

I would also advice against spending your time on coming up with your own licensing scheme, instead spend that time focusing on your actual product.

Consider using CryptoLicensing - it provides licensing, copy-protection, activations, machine-locking, trials, and other features.

DISCLAIMER: I work for LogicNP Software, the developer of CryptoLicensing.

请止步禁区 2024-07-20 09:14:27

好的软件不需要保护。 无论您选择何种保护,您的软件都将被复制。

因此,避免非法复制的最佳方法是使您的软件易于使用,以便您的客户对您的产品感到高兴和满意。

Good software doesn't need a protection. Your software will ever be copied, no mather what protection you choose.

So the best way to avoid illegal copies would be to make your software user-friendly, so that your customers are happy and satisfied with your product.

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