ASW #233 - Josh Goldberg

<p>Static analysis is the art of scrutinizing your code without building or running it. Common static analysis tools are formatters (which change whitespace and other trivia), linters (which detect likely best practice and style issues), and type checkers (which detect likely bugs). Each of these can aid in improving application security by detecting real issues at development-time.</p> <p>Segment Resources:</p> <ul> <li><a href= "https://typescript-eslint.io">https://typescript-eslint.io</a> </li> <li><a href="https://eslint.org">https://eslint.org</a></li> <li><a href= "https://blog.joshuakgoldberg.com">https://blog.joshuakgoldberg.com</a></li> </ul> <p> </p> <p>Outlook can leak NTLM hashes, potential RCE in a chipset for Wi-Fi calling in phones (and autos!?), the design of OpenSSH's sandboxes, more on the direction of OWASP, celebrating 25 years of Curl.</p> <p> </p> <p>Visit <a href= "https://www.securityweekly.com/asw">https://www.securityweekly.com/asw</a> for all the latest episodes!</p> <p>Follow us on Twitter: <a href= "https://www.twitter.com/secweekly">https://www.twitter.com/secweekly</a></p> <p>Like us on Facebook: <a href= "https://www.facebook.com/secweekly">https://www.facebook.com/secweekly</a></p> <p> </p> <p>Show Notes: <a href= "https://securityweekly.com/asw233">https://securityweekly.com/asw233</a></p>