{"id":25876,"date":"2014-09-09T11:46:34","date_gmt":"2014-09-09T15:46:34","guid":{"rendered":"http:\/\/www.opensource.im\/?p=25876"},"modified":"2014-09-09T11:46:34","modified_gmt":"2014-09-09T15:46:34","slug":"openssl-warns-vendors-against-using-vulnerability-info-for-marketing","status":"publish","type":"post","link":"https:\/\/euvolution.com\/open-source-convergence\/cryptography\/openssl-warns-vendors-against-using-vulnerability-info-for-marketing.php","title":{"rendered":"OpenSSL warns vendors against using vulnerability info for marketing"},"content":{"rendered":"<p><p>    Security advisories for OpenSSL should not be used for    competitive advantage, according to the development project    behind the widely used cryptography component.  <\/p>\n<p>    The    warning comes from the OpenSSL Project, which has published for    the first time guidelines    for how it internally handles security problems, part of an    ongoing effort to strengthen the project following the     Heartbleed security scare in April.  <\/p>\n<p>    High    severity issues such as remote code execution vulnerabilities    will be kept private within OpenSSLs development team, ideally    for no longer than a month until a new release is ready.  <\/p>\n<p>    If an    update is planned, a notification will be released on the    openssl-announce email list, but no further information about    the issues will be given, it said.  <\/p>\n<p>    Some    organizations that develop a general purpose OS that includes    OpenSSL will be prenotified with more details about the patches    in order to have a few days to prepare. But the OpenSSL Project    warned that the more people that are notified in advance, the    higher the likelihood that a leak will occur.  <\/p>\n<p>    We may    withdraw notifying individual organizations from future    prenotifications if they leak issues before they are public or    over time do not add value (value can be added by providing    feedback, corrections, test results, etc.), it wrote.  <\/p>\n<p>    If    information on a vulnerability leaks, it makes it more likely    that attackers may be able to figure out the software flaw and    launch attacks before software products are patched.  <\/p>\n<p>    The    OpenSSL Project also advised that it is not acceptable for    organizations to use advance notice in marketing as a    competitive advantage. It objects, for example, to marketing    claims such as if you had bought our product\/used our service    you would have been protected a week ago.  <\/p>\n<p>    OpenSSL    has been undergoing an intense code review since the Heartbleed    vulnerability was discovered in April. The flaw affected tens    of thousands of websites across the Internet and many software    applications.  <\/p>\n<p>    OpenSSL    is a cryptographic library that enables SSL (Secure Sockets    Layer) or TLS (Transport Security Layer) encryption. Most    websites use either SSL or TLS, which is indicated in browsers    with a padlock symbol.  <\/p>\n<p><!-- Auto Generated --><\/p>\n<p>More here:<br \/>\n<a target=\"_blank\" href=\"http:\/\/www.pcworld.com\/article\/2604440\/openssl-warns-vendors-against-using-vulnerability-info-for-marketing.html\/RK=0\/RS=3zIU0Bf5Bi55fbNzGZp1.3kw55g-\" title=\"OpenSSL warns vendors against using vulnerability info for marketing\">OpenSSL warns vendors against using vulnerability info for marketing<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p> Security advisories for OpenSSL should not be used for competitive advantage, according to the development project behind the widely used cryptography component. The warning comes from the OpenSSL Project, which has published for the first time guidelines for how it internally handles security problems, part of an ongoing effort to strengthen the project following the Heartbleed security scare in April<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1600],"tags":[],"class_list":["post-25876","post","type-post","status-publish","format-standard","hentry","category-cryptography"],"_links":{"self":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/posts\/25876"}],"collection":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/comments?post=25876"}],"version-history":[{"count":0,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/posts\/25876\/revisions"}],"wp:attachment":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/media?parent=25876"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/categories?post=25876"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/tags?post=25876"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}