再保险:CVE ID语法——寻求拓展建议

它也让我反感。另一部分的我说的话做,当它完成,风口最好很快完成,也许(注意的是史蒂夫的邮件),最好是宣布一个日期,当我们计划打破东西。我思考,我希望安全人员可以忙迁移从XP在不久的将来,并期望他们会忙于Blackhat-related公告在8月的开始。所以很快的日期可能是7月,日期可能在9月。后来我们把liklihood越高,我们打算争夺。亚当在星期四,2014年4月3日在-0400年10:58:22AM,帕斯卡贝写道:|我想到这样做(测试CVE),但一想到打破|生产目的,早于此前宣布|(预期已经设置),让我恶心。会|容易胃如果做”就在“我们的老id。帕斯卡| | | |在星期四,-0400 | 2014年4月10:40:23亚当Shostack < adam@homeport.org >写道:| | >在星期四,4月3日,2014年在09:04:11AM -0400年帕斯卡贝写道:| | > > |我期望大多数客户只会订婚的时候休息。| > |我认为这将是最有用的宣传开关和发送| | >通知你之前的旧格式id。“只是| >之前”是什么意思|可以“一周”,但当然是有争议的。 | > | > I think Pascal nails it here: we will get incremental value from | > additional rounds of PR, but at some level, there will be folks who | > don't feel a need to act until there's a need. | > | > So allow me to advocate for "propaganda through action": issue a | > single CVE soon which is intended to stress the toolchains. Make it | > a real CVE, so that the customers have a way to check if their | > toolchains really work. | > | > I'll further advocate that this should be done soon, and should be the | > focus of the new round of PR. | > | > | > Adam | > | > PS: I don't actually know if this a good idea, but wanted to | > throw it out for consideration. | > | > -- Join my mailing list, and be the first to hear about my new projects!http://www.homeport.org/ ~亚当/ newthing.html