C and C++: A Security Perspective Security Beyond Memory Safety Using Modern C++ to Avoid Vulnerabilities by DesignMax Hoffmann Security Beyond Memory Safety CppCon 2024 2 Security Beyond Memory Safety Hoffmann Security Beyond Memory Safety CppCon 2024 3 FIFTY SHADES OF SHOOTING YOURSELF IN THE FOOT WITH A RAILGUNMax Hoffmann Security Beyond Memory Safety CppCon 2024 4Max Hoffmann Security Beyond yearsMax Hoffmann Security Beyond Memory Safety CppCon 2024 6Max Hoffmann Security Beyond Memory Safety CppCon 2024 7Max Hoffmann Security Beyond Memory Safety CppCon 2024 8Max Hoffmann Security Beyond Memory

Embracing an Adversarial Mindset for C++ Security Amanda Rousseau 9/18/2024 This presentation is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS SUMMARY1 Strategies for Secure C++ DevelopmentWHOAMI 0x401006 Microsoft 0x40100C Offensive 0x40100F Research & Security 0x401018 Engineering 0x40101A (MORSE) CURRENT 0x401000 MALWARE UNICORN AMANDA ROUSSEAU 0x402001 perspectiveFactors Influencing Trends Increased Security Awareness and Practices Adoption of Modern Technologies •secure coding, regular patching, comprehensive security testing •Improved Discovery Methods -

Spring Security Shiro Plugin - Reference Documentation Burt Beckwith Version 3.1.2.BUILD-SNAPSHOT Table of Contents 1. Introduction to the Spring Security Shiro Plugin . . . . . . . . . . . . . . Chapter 1. Introduction to the Spring Security Shiro Plugin The Spring Security Shiro plugin adds some support for using a hybrid approach combining Spring Security and Shiro. It currently only supports supports Shiro ACLs, since Spring Security ACLs are very powerful but can be very cumbersome to use, and the Shiro approach is straightforward and simple. The majority of the authentication and authorization

1 Shiro support for the Spring Security plugin Table of contents 2 Shiro support for the Spring Security plugin - Reference Documentation Authors: Burt Beckwith Version: 0.1 Table of Contents 1 Introduction The Spring Security Shiro plugin adds some support for using a hybrid approach combining Spring Security and . It currently only supports Shiro ACLs, since Spring Security ACLs are very Shiro authentication and authorization work is still done by Spring Security. This plugin listens for Spring Security authentication events and uses the Spring Security Authentication instance to build and register a Shiro

the Spring Security plugin Shiro support for the Spring Security plugin - Reference Documentation Authors: Burt Beckwith Version: 1.0.0 Table of Contents 1 Introduction to the Spring Security Shiro Plugin Spring Security Shiro Plugin The Spring Security Shiro plugin adds some support for using a hybrid approach combining Spring and . It currently only supports Shiro ACLs, since Spring Security ACLs are are very Security Shiro powerful but can be very cumbersome to use, and the Shiro approach is straightforward and simple. The majority of the authentication and authorization work is still done by Spring

"polls_cms_integration/poll_plugin.html" def render(self, context, instance, placeholder): context.update({'instance': instance}) return context Note All plugin classes must inherit from cms.plugin_base TEMPLATE_CONTEXT_PROCESSORS settings are rolled into the TEMPLATES setting. We’re assuming you’re using Django 1.8 here. TEMPLATES = [ { # ... 'OPTIONS': { 'context_processors': 'context_processors': [ # ... 'aldryn_boilerplates.context_processors.boilerplate', ], 'loaders': [ # ... 'aldryn_boilerplates

"polls_cms_integration/poll_plugin.html" def render(self, context, instance, placeholder): context.update({'instance': instance}) return context Note All plugin classes must inherit from cms.plugin_base TEMPLATE_CONTEXT_PROCESSORS settings are rolled into the TEMPLATES setting. We’re assuming you’re using Django 1.8 here. TEMPLATES = [ { # ... 'OPTIONS': { 'context_processors': 'context_processors': [ # ... 'aldryn_boilerplates.context_processors.boilerplate', ], 'loaders': [ # ... 'aldryn_boilerplates

plugin in the interface render_template = "polls_cms_integration/poll_plugin.html" def render(self, context, instance, placeholder): (continues on next page) 18 Chapter 4. Software version requirements and notes django cms Documentation, Release 3.9.0 (continued from previous page) context.update({'instance': instance}) return context Note: All plugin classes must inherit from cms.plugin_base.CMSPluginBase and TEMPLATE_LOADERS and TEMPLATE_CONTEXT_PROCESSORS settings are rolled into the TEMPLATES setting. We’re assuming you’re using Django 1.8 here. TEMPLATES = [ { # ... 'OPTIONS': { 'context_processors': [ # ... 'aldryn_boilerplates

"polls_cms_integration/poll_plugin.html" def render(self, context, instance, placeholder): context.update({'instance': instance}) return context Note: All plugin classes must inherit from cms.plugin_base TEMPLATE_LOADERS and TEMPLATE_CONTEXT_PROCESSORS settings are rolled into the TEMPLATES setting. We’re assuming you’re using Django 1.8 here. TEMPLATES = [ { # ... 'OPTIONS': { 'context_processors': [ # ... 'aldryn_boilerplates 'aldryn_boilerplates.context_processors.boilerplate', ], 'loaders': [ (continues on next page) 28 Chapter 4. Software version requirements and release notes django cms Documentation, Release 3.10.0 (continued

INSTALLED_APPS, and: in the TEMPLATES['OPTIONS']['context_processors']: CMS_CONFIRM_VERSION4 = True python manage.py migrate "sekizai" "sekizai.context_processors.sekizai" TEMPLATES = [ { ... "OPTIONS": { "context_processors": [ ... "django.template.context_processors.i18n", Middleware in your MIDDLEWARE [https://docs.djangoproject configuration to your settings.py: Context processors Add "cms.context_processors.cms_settings" to TEMPLATES['OPTIONS'] ['context_processors']. Also add 'django.template.context_processors.i18n' if it’s not