Crypto++

和

NDEBUG
缺省情况下，assert（）将在这些环境中启用生产。对于那些环境中的生产，使用不同的断言机制或定义NDEBUG可能很重要。

            Debug builds of the project includes asserts to aide the developer in finding mistakes.

Release builds are built with -DNDEBUG and will NEVER asset. The library will validate the parameters and/or state and throw an exception on failure. Anywhere there is an 'if' statement to validate state includes an assert. Anywhere there is an assert to validate state includes an 'if' statement that throws. They are matched set like bookends.

The Crypto++ library never asserts in production for five reasons. First, it is the application's authors decision to crash their app. The library does not make policy decisions for the application author.

Second, some platforms, like Apple iOS, forbid applications from crashing because it degrades the UI experience. In this case, the App Store has set the policy for the application author. The library will not cause an author's app to be rejected from an App Store.

Third, the library handles sensitive information like private keys, shared secrets and passwords. When an assert fires a core file could be written that includes the sensitive information. That means the sensitive information has been egressed outside the application's security boundary. Folks with access to the mobile device, desktop computer or a computer paired/sync'd with the mobile device will be able to recover the secrets from the filesystem.

Fourth, the core file, if present, may be shipped to an Error Reporting Service. Now Apple, Google, Fedora, Red Hat, Ubuntu or Microsoft have the user's private keys, shared secrets and passwords. Then the information is then passed onto the developer who has the user's private keys, shared secrets and passwords, too.

Fifth, asserts destroy most of Confidentiality-Availability-Integrity (CIA). When an assert crashes a program, it (1) may preserve data Integrity at the expense of (2) Confidentiality of the data and (3) Availability of the program or server. If an author wishes to preserve Integrity, he/she/it merely needs to return false in the offending function or call exit(1) without the loss of Confidentiality or Availability.

          Criterion [dynamic_analysis_fixed]
           完成
           不完整
             N/A
             ?

      通过动态代码分析发现的所有严重性为中，高的可利用漏洞必须在确认后及时修复。

      ^{[dynamic_analysis_fixed]}

         如果 CVSS 2.0 基本分数为4，那么一个漏洞是中等到高的严重性。如果您没有运行动态代码分析，没有发现任何这样的漏洞，选择“不适用”（N/A）。

            The project typically responds to analysis findings within a hour when run manually, or within a day when reported by a user.

        此数据在知识共享署名3.0或更高版本许可证（CC-BY-3.0 +） 下可用。所有内容都可以自由分享和演绎，但必须给予适当的署名。请署名为Jeffrey Walton和OpenSSF最佳实践徽章贡献者。

项目徽章条目拥有者：
Jeffrey Walton.

最后更新于 2020-03-25 18:25:43 UTC,
最后更新于 2020-03-26 03:01:39 UTC。
  最后在 2020-03-25 19:57:57 UTC 获得通过徽章。

后退

         需要帮助？有疑问？发现问题？请 发送邮件 或 提出问题. © 2015-2017 Open Source Security Foundation （核心基础设施计划）, 一个 Linux 基金会 合作项目。版权所有。 请查阅我们的 隐私策略 和 使用条款. 

Crypto++

基本 13/13 ●

识别

基本项目网站内容

FLOSS许可证

文档

其他

变更控制 9/9 ●

公开的版本控制的源代码存储库

唯一版本编号

发行说明

报告 8/8 ●

错误报告流程

漏洞报告流程

质量 13/13 ●

可工作的构建系统

自动测试套件

新功能测试

警告标志

安全 16/16 ●

安全开发知识

使用基础的良好加密实践

安全交付防御中间人（MITM）的攻击

修正公开的漏洞

其他安全问题

分析 8/8 ●

静态代码分析

动态代码分析