首页> 外文会议>IEEE/ACM International Conference on Software Engineering >“Do this! Do that!, And nothing will happen” Do specifications lead to securely stored passwords?
【24h】

“Do this! Do that!, And nothing will happen” Do specifications lead to securely stored passwords?

机译:“做这个! 做那个!,没有任何事情会发生“DU规格导致安全存储密码?

获取原文

摘要

Does the act of writing a specification (how the code should behave) for a piece of security sensitive code lead to developers producing more secure code? We asked 138 developers to write a snippet of code to store a password: Half of them were asked to write down a specification of how the code should behave before writing the program, the other half were asked to write the code but without being prompted to write a specification first. We find that explicitly prompting developers to write a specification has a small positive effect on the security of password storage approaches implemented. However, developers often fail to store passwords securely, despite claiming to be confident and knowledgeable in their approaches, and despite considering an appropriate range of threats. We find a need for developer-centered usable mechanisms for telling developers how to store passwords: lists of what they must do are not working.
机译:编写规范的行为(代码应该如何行为)对一条安全敏感代码导致开发人员产生更安全的代码? 我们要求138名开发人员编写一个代码片段来存储密码:其中一半被要求写下代码在编写程序之前的表现,另一半被要求编写代码但没有提示 首先写一个规范。 我们发现,明确提示开发人员编写规范对所实现的密码存储方法的安全性具有很小的积极影响。 然而,尽管声称在其方法中,尽管有考虑了适当的威胁,但开发人员往往无法安全地存储密码。 我们发现需要以开发人员为中心的可用机制来告诉开发人员如何存储密码:他们必须确实的列表都不工作。

著录项

相似文献

  • 外文文献
  • 中文文献
  • 专利
获取原文

客服邮箱:kefu@zhangqiaokeyan.com

京公网安备:11010802029741号 ICP备案号:京ICP备15016152号-6 六维联合信息科技 (北京) 有限公司©版权所有
  • 客服微信

  • 服务号