ESAPI.NET 是一个死项目吗?
我最近的任务是领导一项工作,以改进我们的输入(和输出)验证,同时考虑到 OWASP 建议和 PCI 合规性。在此过程中,我试图评估 ESAPI.NET 项目的价值,该项目自 09 年春季以来似乎没有任何活动,而且目前的情况是不完整的。
有人有使用或扩展 ESAPI.NET v0.2 的经验吗?如今,这是构建基础设施来解决目标漏洞的良好起点吗?
仅供参考:我正在研究 MS AntiXSS,当然,它仅解决 ESAPI 范围的一部分。尽管我们还需要改进,但我们已经在 SQL 注入方面做得很好。
(如果有人想创建 ESAPI 标签,请随意。我没有这个魔力。)
I've been recently tasked with leading an effort to improve our input (and output) validation with OWASP recommendations and PCI compliance in mind. In the process, I'm trying to assess the value of the ESAPI.NET project which does not appear to have seen any activity since the spring of '09 and as it stands is incomplete.
Does anyone have experience using or extending ESAPI.NET v0.2? Is it a good starting place today for building out an infrastructure to address the targeted vulnerabilities?
FYI: I am looking at MS AntiXSS which, of course, only addresses a portion of ESAPI's scope. We already do a good job with SQL injection though there are improvements we need to make.
(If someone wants to create an ESAPI tag, feel free. I don't have the mojo.)
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(3)
上周似乎有一些更新:http://code.google .com/p/owasp-esapi-dotnet/source/list
您可以联系该列表上的项目负责人之一,询问发生了什么事。
注意:2012 年 5 月 26 日:该项目的最后一次更新是 2010 年 12 月 4 日。是的,它已经死了。
Looks like there were a couple updates last week: http://code.google.com/p/owasp-esapi-dotnet/source/list
You might contact one of the project leads on that list to ask what's going on.
NOTE: 05/26/2012: the last update on that project was dec 4, 2010. Yes, it is dead.
看来 ESAPI 已经进入死胡同了。没有人使用它,没有问题,没有论坛,没有信息,什么都没有。列表服务(这是什么,1996 年?)也很贫乏。文档很糟糕,swingset 中的示例不起作用(安装的服务器是 HTTP 而不是 HTTPS,并且不能在 HTTP 模式下进行任何事务)。
似乎是一个没有出路的项目。
It looks like ESAPI is dead period. There's nobody using it, there are no questions, no forums, no information, nothing. The listservs (what is this, 1996?) are barren too. The documentation is terrible and the samples in the swingset don't work (server that installs is HTTP not HTTPS, and no transactions can be made in HTTP mode).
Seems to be a dead end project.
该项目本身似乎已经死了,但是有些人维护着 github 副本,并添加了一些(次要的?)添加内容...
https://github.com/haldiggs/owasp-esapi-dotnet
https://github.com/jstemerdink/owasp-esapi-dotnet
The project itself seems dead there are however some people who maintain a github copy with several (minor?) additions...
https://github.com/haldiggs/owasp-esapi-dotnet
https://github.com/jstemerdink/owasp-esapi-dotnet