One Article Review
| Source |  Errata Security |
|---|---|
| Identifiant | 1297576 |
| Date de publication | 2019-08-31 10:18:49 (vue: 2019-08-31 17:02:37) |
| Titre | Thread on network input parsers |
| Texte | This blogpost contains a long Twitter thread on input parsers. I thought I'd copy the thread here as a blogpost. I am spending far too long on this chapter on "parsers". It's this huge gaping hole in Computer Science where academics don't realize it's a thing. It's like physics missing one of Newton's laws, or medicine ignoring broken bones, or chemistry ignoring fluorine.The problem is that without existing templates of how "parsing" should be taught, it's really hard coming up with a structure for describing it from scratch."Langsec" has the best model, but at the same time, it's a bit abstract ("input is a language that drives computation"), so I want to ease into it with practical examples for programmers. |
| Envoyé | Oui |
| Condensat | about actually against all also annoyed another approaches appropriate are arithmetic asynchronously away because benefit better brings chapter cite clicks code com/robertdavidgraham/masscan/blob/master/src/proto concept constant culled cwhich defend defined defining discuss discussion doing don down elsewhere entire enum even everything field from get good hand has have hoping http hunt ide implementations improving input internet ipv4 ipver just later length like little machine magic match means minutes much multiple needs network next non notes number numbers often optimization optimizations other overlays packets parsers people performance point pointer port possible premature prescription prescriptions program read reason reassembly rfc right robertdavidgraham/masscanhttps://github robertdavidgraham/masscantcp scanner scanning separate should shouldn simply: sorry source spec specification specifications spews standard state stop storm string structure/integer such syn than them then things those thread tweet under unhelpful uptight useful values vendor very want way when where which who why will won worry writing wrong |
| Tags | Guideline |
| Stories | |
| Notes | |
| Move | 
|
L'article ne semble pas avoir été repris aprés sa publication.
L'article ne semble pas avoir été repris sur un précédent.