Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Have you read their incident response? If you had, you would know they weren't using Go for this and it was actually an issue an a parser generated by ragel (C++) which was then used as an nginx module.


To be clear, it was mis-use of Ragel, not the fault of the Ragel module




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: