U tweetove putem weba ili aplikacija drugih proizvođača možete dodati podatke o lokaciji, kao što su grad ili točna lokacija. Povijest lokacija tweetova uvijek možete izbrisati. Saznajte više
Always wanted #golang to be the first to support structured fuzzing as first-class citizen:
func FuzzRegexp(f *testing.F, re string, data []byte, posix bool) {...}
https://docs.google.com/document/u/1/d/1zXR-TFL3BfnceEAWytV8bnzB2Tfp6EPFinWVJ5V4QC8/pub …
But #rust it is!
Glad it's slowly moving to industry standard. Maybe it will urge Go :)https://twitter.com/fitzgen/status/1217862506514829312 …
Announcing better support for fuzzing with structured inputs in Rust!
New releases of `cargo fuzz`, `libfuzzer-sys`, and `arbitrary` better support writing fuzz targets that take well-formed instances of custom input types.
Details: https://fitzgeraldnick.com/2020/01/16/better-support-for-fuzzing-structured-inputs-in-rust.html …
Though, I think eventually we need to make structure first-class citizen in the fuzzer engine as well. In rust it's still bolted on top of traditional blob fuzzer. It needs to be the other way around: single blob is a special case of structured input.
Can you perhaps point to a good article for non-kernel non-C software engineers re: what a fuzzing is? E.g. ELI5 After following you for a while I grew fascinated by how fuzzy testing helps uncover subtle bugs, but my understanding of fuzzy testing remains limited by intuition
Not sure what's the definitive source. If you understand Russian, I gave 2 talks about fuzzing, one with Go flavor: https://www.youtube.com/watch?v=EJVp13f_aIs … and another with C++ flavor:https://www.youtube.com/watch?v=FD30Qzd6ylk …
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.
