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
"Regression Fuzzing": a team responsible for fixing a security bug should be also responsible for implementing a fuzz target that could find that bug.
Here is a good example: https://bugs.chromium.org/p/chromium/issues/detail?id=994957 … OOB read in libc++ fixed, and then a bunch of new fuzz targets added:https://github.com/llvm/llvm-project/commit/daacf57032450079b44b8a7f9b976700d3bc38f8#diff-a020123e9cf2d0b9d0d6f0ca236b6521 …
this sounds reasonable, how is it this is not common?! -.- looks like more often than not the most obvious and best solution is the most overlooked one
Until recently, fuzzing was not widely known and not available out of the box for most developers. Now these obstacles are removed, but most of the devs still don't have the habit.
Perhaps.... Bug -> variant analysis -> other bugs -> IDE coaching and break the build checks on new secure way that avoids that whole class of bugs. Fuzzing unit tests for that part of code base
I would separate having a case reproducing the specific bug from test coverage improvement. When such a bug is found both are needed but you want your regression tests to be separate from your long running fuzz tests
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.
