{"id":31452,"date":"2017-02-22T23:46:29","date_gmt":"2017-02-23T04:46:29","guid":{"rendered":"http:\/\/www.opensource.im\/uncategorized\/php-will-incorporate-libsodium-for-crypto-security-intelligence-blog.php"},"modified":"2017-02-22T23:46:29","modified_gmt":"2017-02-23T04:46:29","slug":"php-will-incorporate-libsodium-for-crypto-security-intelligence-blog","status":"publish","type":"post","link":"https:\/\/euvolution.com\/open-source-convergence\/cryptography\/php-will-incorporate-libsodium-for-crypto-security-intelligence-blog.php","title":{"rendered":"PHP Will Incorporate Libsodium for Crypto &#8211; Security Intelligence (blog)"},"content":{"rendered":"<p><p>    Many developers consider the Libsodium library the go-to source    of application-layer cryptography. It is thought to offer a    portable, cross-compilable, easy-to-use library that can be    applied to most standard crypto functions such as encryption,    decryption, signatures and password hashing.  <\/p>\n<p>    Now, the PHP core will be bound with the Libsodium cryptography    libraries as of version 7.2. This merger is scheduled to emerge    toward the end of this year,     Bleeping Computer reported.  <\/p>\n<p>    The impetus for the change involved a new kind of environment    that PHP  which powers at least 82 percent of websites,    according to Bleeping Computer  encountered when running the    WordPress content management system (CMS). Researchers have    found numerous     WordPress vulnerabilities of late, and the solution usually    includes another PHP extension that functions as a CMS    security-oriented extension.  <\/p>\n<p>    However, problems can arise when using a shared host provider    (SHP) rather than kind that provides root access in the cloud    by default. SHPs do not want all sorts of PHP extensions    roaming throughout their systems because if PHP breaks breaks    something, they have to clean up the resulting mess. These    limitations could lead to unsecured WordPress environments.  <\/p>\n<p>    Scott Arciszewski, chief development officer at Paragon    Initiative Enterprises, told Bleeping Computer that having all    the raw, cryptographical goodness of Libsodium under the hood    of PHP will have many salutary effects.  <\/p>\n<p>    For example, he believes that Libsodium can eliminate the need    for the number of PHP extensions otherwise required for a    WordPress installation. The basic and secure cryptography, he    reasoned, would be supported by default, and WordPress    developers will be attracted to the newer and more secure    functions.  <\/p>\n<p>    Arciszewski further explained his reasoning on the     Paragon Initiative blog. There he added that PHPs    commitment to cryptography is the first of its kind, and any    future developments or similar relationships should only    enhance security.  <\/p>\n<p>    It remains to be seen whether adding Libsodium to PHP will    increase the use of cryptography tools and result in more    concrete security. However, its a step in the right direction    for sure.  <\/p>\n<p><!-- Auto Generated --><\/p>\n<p>View original post here:<br \/>\n<a target=\"_blank\" href=\"https:\/\/securityintelligence.com\/news\/php-will-incorporate-libsodium-for-crypto\/\" title=\"PHP Will Incorporate Libsodium for Crypto - Security Intelligence (blog)\">PHP Will Incorporate Libsodium for Crypto - Security Intelligence (blog)<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p> Many developers consider the Libsodium library the go-to source of application-layer cryptography. It is thought to offer a portable, cross-compilable, easy-to-use library that can be applied to most standard crypto functions such as encryption, decryption, signatures and password hashing. <\/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-31452","post","type-post","status-publish","format-standard","hentry","category-cryptography"],"_links":{"self":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/posts\/31452"}],"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=31452"}],"version-history":[{"count":0,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/posts\/31452\/revisions"}],"wp:attachment":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/media?parent=31452"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/categories?post=31452"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/tags?post=31452"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}