3 ms·

No one has forgotten Cloudbleed. It's something we talk about internally and every single day I look at a report that shows me status of software running around

No one has forgotten Cloudbleed. It's something we talk about internally and every single day I look at a report that shows me status of software running around the world so that I never, ever again let a piece of software running on our edge crash and leak information.

bogomipz 7y ago
The point wasn't whether or not Cloudbleed was forgotten but rather acting with some civility towards other when these mistakes do happen. Your suggestion that "there's no good reason, other than sloppiness or laziness, that they wouldn't have such limits in place" is absurd. Misconfigurations and mistakes are a fact of life, they happen to everyone. To suggest that AS 701 which is old enough to have a 3 digit ASN, somehow doesn't use any ingress prefix filtering as a matter of course is disingenuous at best. The cause is quite likely that this was a misconfiguration on a single interface on a single router. I think you know this though.
- jgrahamc 7y ago
  Yeah, because everyone was so civil towards me and Cloudflare when Cloudbleed happened.
  - bogomipz 7y ago
    Wow. So you've decided to propagate only the negative behavior from that incident? "Someone did it to me so I'm going to do it to someone else" - is that the thinking? There were also no shortage of people who showed support and understanding for your folks during that time(me included.) What's the old adage - "be the change you want to see in the world." Seems like a real missed leadership opportunity.
  - nikisweeting 7y ago
    (You handled both admirably well, I would just stop responding to this person.)
    - bogomipz 7y ago
      I'm sorry is holding a differing opinion and discussing that in a civil manner such an issue for you that you feel compelled to step in and offer prescriptive advice? Long live the filter bubble I guess huh?
      - dang 7y ago
        Would you please stop posting like this to HN? At a certain point it only weakens your case, and you passed that point a while ago. https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html

bogomipz 7y ago

The point wasn't whether or not Cloudbleed was forgotten but rather acting with some civility towards other when these mistakes do happen. Your suggestion that "there's no good reason, other than sloppiness or laziness, that they wouldn't have such limits in place" is absurd. Misconfigurations and mistakes are a fact of life, they happen to everyone. To suggest that AS 701 which is old enough to have a 3 digit ASN, somehow doesn't use any ingress prefix filtering as a matter of course is disingenuous at best. The cause is quite likely that this was a misconfiguration on a single interface on a single router. I think you know this though.

jgrahamc 7y ago
Yeah, because everyone was so civil towards me and Cloudflare when Cloudbleed happened.
- bogomipz 7y ago
  Wow. So you've decided to propagate only the negative behavior from that incident? "Someone did it to me so I'm going to do it to someone else" - is that the thinking? There were also no shortage of people who showed support and understanding for your folks during that time(me included.) What's the old adage - "be the change you want to see in the world." Seems like a real missed leadership opportunity.
- nikisweeting 7y ago
  (You handled both admirably well, I would just stop responding to this person.)
  - bogomipz 7y ago
    I'm sorry is holding a differing opinion and discussing that in a civil manner such an issue for you that you feel compelled to step in and offer prescriptive advice? Long live the filter bubble I guess huh?
    - dang 7y ago
      Would you please stop posting like this to HN? At a certain point it only weakens your case, and you passed that point a while ago. https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html