{"id":1531,"date":"2021-09-27T09:53:08","date_gmt":"2021-09-27T15:53:08","guid":{"rendered":"http:\/\/jaredrobinson.com\/blog\/?p=1531"},"modified":"2021-09-27T09:53:08","modified_gmt":"2021-09-27T15:53:08","slug":"investment-in-memory-safety-chrome-rust-and-other-tooling","status":"publish","type":"post","link":"https:\/\/jaredrobinson.com\/blog\/investment-in-memory-safety-chrome-rust-and-other-tooling\/","title":{"rendered":"Investment in memory safety: Chrome, Rust and other tooling"},"content":{"rendered":"\n<p>The software most of us use on a daily basis wasn&#8217;t built with robust security in mind. If it was built with any effort toward security, it was most likely built with &#8220;casual&#8221;, or &#8220;good intentions&#8221; security.<\/p>\n\n\n\n<p>The process that gives us our modern software has typically focused on features and value rather than preventing malicious actors. Yet we live in a connected world, and although connectivity brings power and opportunity, it also brings risk. <\/p>\n\n\n\n<p>Risk because there&#8217;s gain in hacking our lives and the organizations with which we interact &#8212; schools, hospitals, insurance providers, municipalities, government agencies, social media networks and smaller scale entities.<\/p>\n\n\n\n<p>So I&#8217;m glad that Google engineers are vigilant in looking for ways to improve the security of the Chrome browser that so many of us use on a daily basis.<\/p>\n\n\n\n<p><a href=\"https:\/\/security.googleblog.com\/2021\/09\/an-update-on-memory-safety-in-chrome.html\">https:\/\/security.googleblog.com\/2021\/09\/an-update-on-memory-safety-in-chrome.html<\/a><\/p>\n\n\n\n<p>Using better tooling will not solve all security problems &#8212; nowhere close, but it&#8217;s helpful.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>The software most of us use on a daily basis wasn&#8217;t built with robust security in mind. If it was built with any effort toward security, it was most likely built with &#8220;casual&#8221;, or &#8220;good intentions&#8221; security. The process that gives us our modern software has typically focused on features and value rather than preventing &hellip; <\/p>\n<p class=\"link-more\"><a href=\"https:\/\/jaredrobinson.com\/blog\/investment-in-memory-safety-chrome-rust-and-other-tooling\/\" class=\"more-link\">Continue reading<span class=\"screen-reader-text\"> &#8220;Investment in memory safety: Chrome, Rust and other tooling&#8221;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[17],"tags":[26],"class_list":["post-1531","post","type-post","status-publish","format-standard","hentry","category-tech","tag-tech-2"],"_links":{"self":[{"href":"https:\/\/jaredrobinson.com\/blog\/wp-json\/wp\/v2\/posts\/1531","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/jaredrobinson.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/jaredrobinson.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/jaredrobinson.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/jaredrobinson.com\/blog\/wp-json\/wp\/v2\/comments?post=1531"}],"version-history":[{"count":1,"href":"https:\/\/jaredrobinson.com\/blog\/wp-json\/wp\/v2\/posts\/1531\/revisions"}],"predecessor-version":[{"id":1533,"href":"https:\/\/jaredrobinson.com\/blog\/wp-json\/wp\/v2\/posts\/1531\/revisions\/1533"}],"wp:attachment":[{"href":"https:\/\/jaredrobinson.com\/blog\/wp-json\/wp\/v2\/media?parent=1531"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/jaredrobinson.com\/blog\/wp-json\/wp\/v2\/categories?post=1531"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/jaredrobinson.com\/blog\/wp-json\/wp\/v2\/tags?post=1531"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}