软件安全 [英] Security of software

查看:60
本文介绍了软件安全的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我在Asp.net C#制作了一个软件。

我想放置安全性,以便没有人可以复制这个软件并使用它。我怎么能避免有人复制这个软件。

我必须为此做些什么?

请帮助我...

i have make one software in Asp.net C#.
I want to put security so that no one can copy this sofware and use it. How i can avoid someone form copy this software.
What i have to do for this ?
Please Help me ...

推荐答案

从根本上说,你不能。如果付出足够的努力,可以打破安全形式:看看新版本的PhotoShop在Adobe发布之后在盗版网站上以破解的形式出现的速度有多快 - 在某些情况下是同一天。而你可以打赌它花费了更多的时间和金钱来实现复制保护......



有些事你可以做,但你需要先做决定您想要支持的利益/投资比例。如果您以几美元的价格出售该应用程序,并希望以相同数量的盗版销售一百份副本,那么在您花费超过自己节省的成本之前,您就无法投入大量资金。请记住,使用中的复制版本数量并不重要,而是将要支付的复制版本数量:因此,如果您防止100个副本,但只有10个转换为销售,那么(仅10 - 1)倍的利润本应投入到保护中,或者您已经亏损获得这些销售。如果你的版权保护让一个客户厌倦了要求退款 - 而且它可以,如果你没有完全正确的话 - 那么这也是转换后的副本的数量。没过多久,实施复制保护就要花费你很多,而不是从它回来...



话虽如此,谷歌可以帮助你: Googlecopy protect my application [ ^ ] - 我留给你找出适合你特定情况的最佳方法。
Fundamentally, you can't. And form of security can be broken if enough effort is put into it: look at how quickly a new version of PhotoShop appears in "cracked" form on the pirate sites after it is released by Adobe - the same day in some cases. And you can bet it cost Adobe a lot more time and money than that to implement copy protection...

There are some things you can do, but you need first to decide what benefit / investment ration you want to support. If you are selling the application for a couple of dollars, and expect to sell a hundred copies with the same number pirated, then you can't put much into it before you have cost yourself more than you will save. And bear in mind that it's not the number of copied versions in use that matters, it's the number of copied versions that will be paid for instead: so if you prevent 100 copies, but only 10 of them are converted to sales, then only (10 - 1) times the profit should have been invested in the protection, or you have lost money getting those sales. And if your copy protection annoys one customer into demanding his money back - and it can, and does if you don't get it exactly right - then that counts against the number of converted copies as well. It doesn't take long before it costs you a lot more to implement copy protection than you get back from it...

Having said that, google can help you: Google "copy protect my application"[^] - I leave it to you to work out the best method for your particular circumstances.


对于ASP.NET应用程序,问题实际上非常简单:



无论您在服务器端拥有什么,用户都无法看到。如果托管本身足够安全,那么这根本不是你关注的问题。一旦内容(使用所有客户端脚本)发送到客户端,用户端无论您在客户端执行的操作都可以完全访问,因此无论您做什么,都无法阻止复制它。



所以,从这个意义上说,你的问题根本不存在。你可以放松一下。



-SA
For an ASP.NET application, the problem is in fact very simple:

Whatever you have on the server side, the user cannot see anyway. If the hosting itself is secure enough, this is not your concern at all. And whatever you do on the client side becomes fully accessible by the users as soon as content (with all your client-side scripts) is sent to the client side, so there cannot be a way to prevent copying it, no matter what you do.

So, in this sense, your problem simply does not exist. You can relax.

—SA


这篇关于软件安全的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆