Re:斜方投CVE ID语法

重新提交——简单的推理。基本上我的观点与史蒂夫的但对于完整性(所以我的投票数. .):

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
投票选举
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

Sourcefire投票

第一选择:选择B

原因(首选):

——可扩展性意味着我们不需要在不久的将来再次回到这个讨论。宽度允许大量的条目。�

——这种格式是更多的搜索引擎友好关系到我们客户通常会把ID时显示在我们的产品和生产搜索。�

——额外的跑道时间津贴。重构我们的UI的CVE需要时间,我们需要它。前10 k的一致性给我们跑道,�

第二个选择:选择一个

原因(第二选择):

这通常是对我的吸引力,因为它是更少的用户界面友好。我们坚持对命名,便于客户使用和参考。�

2013年5月13日15的,阿尔弗雷德迅速发展<ahuger@sourcefire.com>写道:

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
投票选举
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

Sourcefire投票

第一选择:选择B
第二个选择:选择一个



- - -
发展副总裁
先进的恶意软件组
Sourcefire公司。
办公室:403-616-7186

- - -
发展副总裁
先进的恶意软件组
Sourcefire公司。
办公室:403-616-7186