Add missing presentations and fix consistency issues#640
Merged
Conversation
- DeFi Hacks and Future Threats (Prysm Group panel, Jun 2020) - Traditional Infosec for Blockchain Firms (Dan Guido) - Evidence-driven Security Engineering (Dan Guido) Closes #112 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Closed
- DeFi Hacks and Future Threats (Blockchain, 2020) - Traditional Infosec for Blockchain Firms (Blockchain, 2019) - Evidence-driven Security Engineering (Engineering, 2019) Refs #112 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Rename "How to fuzz like a pro-Defi Security Summit-EthCC-EthTaipei" to "How to Fuzz Like a Pro" (directory names should be talk titles only, not include venue names) - Fix broken README link to that directory (was missing -EthTaipei) - Add missing "Semantic Labeling of Parsers" talk to README (Automated bug finding section, LangSec 2020) - Document presentation directory and README standards in CLAUDE.md Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Create proper directory + README for langsec_2023_ubet.pdf (was a
loose file, now "Automatically Detecting Variability Bugs Through
Hybrid Control and Data Flow Analysis" with IEEE Xplore link)
- Fix broken Build Provenance link (unescape parentheses in URL)
- Remove trailing slashes from 5 presentation links
- Fix leading whitespace on "A Sermon on the Indulgences" table row
- Fix double space in MLIR directory name ("across the" -> "across the")
- Remove underscore from Differential fuzzing directory name
("or_" -> "or")
- Fix year: Buttercup CSAW was Nov 2024, not 2025
- Fix year: Present and Future of AI was Code Blue Nov 2024, not 2025
- Re-sort entries to maintain newest-first order after year corrections
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
dguido
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Closes #112 and fixes several pre-existing consistency issues discovered during the audit.
New presentations added
Directory renames
How to fuzz like a pro-Defi Security Summit-EthCC-EthTaipeiHow to Fuzz Like a ProDifferential fuzzing, or_ how to find...Differential fuzzing, or how to find......across the Tower of IRs...across the Tower of IRslangsec_2023_ubet.pdf(loose file)Automatically Detecting Variability Bugs.../README fixes
Documentation
Test plan
🤖 Generated with Claude Code