The vuln-database VDB term has always seemed too-specific to me. I'm seriously considering VDR: Vulnerability Data Repository.
-
-
Replying to @SushiDude
@SushiDude which definition is "too specific"? http://bit.ly/eqQLBm http://bit.ly/1890xqz http://bit.ly/1890zyJ http://bit.ly/1890xqA1 reply 0 retweets 0 likes -
Replying to @attritionorg
@attritionorg I posit that the DB term to our collective audiences implies DBMS & excludes packetstorm, l33tday, CVE "dictionary" etc.1 reply 0 retweets 0 likes -
Replying to @SushiDude
@SushiDude any evidence of this? when I put forth 'VDB', I specifically qualified those were VDBs, just 'specialty'.1 reply 0 retweets 0 likes -
Replying to @attritionorg
@attritionorg no evidence that VDB term being misconstrued, just my suspicion. Despite mult defs, "DB" implies "high structure" to many3 replies 0 retweets 0 likes -
Replying to @SushiDude
@SushiDude while we're at it, let's discuss the term "dictionary" as commonly used by "everyone". http://bit.ly/1cYZozo1 reply 0 retweets 0 likes -
Replying to @attritionorg
@attritionorg well played. But you have not had to deal with > 10 years of wrong expectations when ppl think CVE is a "database"1 reply 0 retweets 0 likes -
Replying to @SushiDude
@SushiDude with that specifically? no. dealing with > 10 years of incorrect expectations... definitely been there.1 reply 0 retweets 0 likes -
Replying to @attritionorg
@attritionorg seems 'database' triggers diff assumptions by diff people, and I want a baggage-free term that includes P-storm, CVE, OSVDB2 replies 0 retweets 0 likes
@SushiDude i have a hunch that it triggers diff assumptions all in a very focused, highly technical part of society. you know, 0.01%...
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.