Skip to content

Commit f01c3c9

Browse files
authored
Update README.md
1 parent af6634e commit f01c3c9

File tree

1 file changed

+1
-1
lines changed
  • lightningtalks/MichaelMcLoughlin-TheFuzzyTaleOfAnXCryptoVulnerability

1 file changed

+1
-1
lines changed

lightningtalks/MichaelMcLoughlin-TheFuzzyTaleOfAnXCryptoVulnerability/README.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ Michael McLoughlin ([@mmcloughlin](https://github.com/mmcloughlin))
55
* [Slides](slides.pdf)
66
* [`cryptofuzz` Project](https://github.com/mmcloughlin/cryptofuzz)
77

8-
On March 20, 2019, the [Go team released a patch for a security vulnerability in `x/crypto/salsa20`](https://groups.google.com/forum/#!topic/golang-dev/1X7VG7FDw2A). This talk will regale you with the full story from [discovery by differential fuzzing](https://github.com/mmcloughlin/cryptofuzz), via low-level assembly root cause analysis to the [contentious disclosure process](https://twitter.com/hashbreaker/status/1108637226089496577).
8+
On March 20, 2019, the [Go team released a patch for a security vulnerability in `x/crypto/salsa20`](https://groups.google.com/forum/#!topic/golang-dev/1X7VG7FDw2A). This talk will regale you with the full story from [discovery by differential fuzzing](https://github.com/mmcloughlin/cryptofuzz), via low-level assembly root cause analysis to the disclosure process.
99

1010
Along the way we'll explore testing practices for security-critical software, in particular the use of `go-fuzz` to check compatibility with reference implementations. Ultimately we'll see how even the most subtle of mistakes in assembly code can have catastrophic implications.
1111

0 commit comments

Comments
 (0)