6 ms·
Can you please take some time here to explain why their post was incorrect, with a brief technical explanation of why SELinux enforcement failed to stop the att
by otterley 10y ago
Can you please take some time here to explain why their post was incorrect, with a brief technical explanation of why SELinux enforcement failed to stop the attack that exploits the particular vulnerability?
I realize you're busy, but it would be much more helpful than a curt statement that simply claims they are wrong.
- bigmac 10y agoWe're working with Red Hat now. Folks can expect more technical details when everyone is on the same page. That said, the solution is the same as with every other piece of software -- update to latest to get security fixes.
- krakensden 10y agoEspecially given Docker Inc.'s history of counterproductive Red Hat hostility.
- andrewguenther 10y agoThis shouldn't be downvoted. Docker has been very openly history towards Red Hat in the past. To the point of openly mocking their developers at DockerCon.
- m-p-3 10y agoVery openly history?
- nanodeath 10y agoGuessing "hostile" was intended.
- JadeNB 10y ago> Very openly history? Given krakensden's posting (https://news.ycombinator.com/item?id=13399853 https://news.ycombinator.com/item?id=13399853): > Especially given Docker Inc.'s history of counterproductive Red Hat hostility. I think that it is clear that andrewguenther meant 'hostile' instead of 'history' in (https://news.ycombinator.com/item?id=13400383 https://news.ycombinator.com/item?id=13400383): > Docker has been very openly history towards Red Hat in the past. Let he who has never typed a passing thought rather than the word he meant cast the first stone.
- m-p-3 10y agoVery openly history?
- shykes 10y agoHi, I'm the founder of Docker. It's not my place to say whether comments should be downvoted or not, and I don't want to ignite teenage-drama arguments over who was mean to whom at recess - we get enough of that level of discourse on the US political scene these days. But I think there is an interesting topic to address here, that we deal with a lot at Docker. The problem in a nutshell: if you choose to take the moral high ground and only promote your products with positive marketing (and that is our strategy at Docker - you will never see any Docker marketing content criticizing competitors), you are vulnerable to bullying and unfair criticism by competitors who don't mind hitting under the belt. Then the question is: do you allow yourself to respond and set the record straight? Or would that just legitimize the criticism by bringing more attention to it? On the other hand, not responding is also risky because it emboldens the trolls to take more and more liberties with facts and ethics. This dilemma becomes more and more pressing as you become more successful and more incumbents start considering you a possible threat to their business. Some of these incumbents have been defending their turf for decades by perfecting negative messaging. Like one competing executive once told me - "we eat startups like yours for breakfast". This situation can be bad for morale also, because your team sees their work and reputation dragged in the mud, and can interpret their employer's silence as a failure to stand up and defend them. The most perverse variation of this problem is when trolls start preemptively painting you as bullies. If that narrative sticks, then you're in trouble, because any attempt to set the record straight will be interpreted as hostility. Now you have two problems: defending yourself against the bullies AND defending yourself against unfair accusations of being a bully. The root cause of the problem, I think, is the diminishing importance of facts and critical reasoning in the tech community. We are all guilty of this: when was the last time you repeated a factoid about "X doesn't scale", "Y isn't secure", "I heard Z is really evil" without fact-checking it yourself? Be honest. Because of this collective failure to do our own thinking and researching, bullies have a huge first-mover advantage. I see an direct parallel between the problem of corporate bullying in tech and the problem of partisan bullying in politics. And I think in both cases, there is a big unresolved problem: how do you succeed and do the right thing? How do we collectively change the rules of the game to make bullying and negative communication a less attractive strategy? I tried really hard to make this a constructive post about a topic I care about. If you interpret any of this as hostile or defensive, that is not at all the intention.
- nul_byte 10y agoThat whole thing with the docker developer smugly wearing a name badge with 'I reject red hat patches' was just sad.
- cpuguy83 10y agoThis isn't even true. The badge, which was a joke btw, said "I say no to systemd specific PRs."
- veidr 10y agoThat's a funny comment, because you are "taking liberties with facts" exactly as lamented by shykes above. You start with a grain of truth — something that actually happened in reality. In this case, it was a joke protesting systemd hegemony. Perhaps you thought that joke was in poor taste. But lets leave that aside for now. So you start with an actual fact. Then, you exaggerate/falsify it, changing the details pretty wildly, and present this story of something that supposedly happened. In fact, nothing like that happened... but it sort of feels like something that might have happened. It vaguely resembles the actual event that did happen (in that, a Docker employee did wear a badge with an opinionated phrase on it at a conference). The key thing, though, is that what you describe is completely and utterly different from the thing that actually happened in reality world[1]. You might not even be the person who changed the details to make the story more compelling (and false). Maybe you got this information from a post shared on Facebook, or from an email forwarded by your uncle. Either way, though, the impact of your comment is to pollute the body of discussion and degrade the collective understanding of this topic. (If this process feels familiar, it's because it is exactly the process that eventually caused the failure of the American democracy... just at a much smaller scale). Personally I don't have any stake in the Docker/RedHat relationship and I don't care about it. I only looked up what actually happened[1] because the idea of a Docker employee wearing an official badge that says "I reject red hat patches" seemed so unlikely to have occurred that it sent my bullshitometer into the red. Suggestion: when something smells like bullshit, don't eat it without conducting a bit of research. [1]: https://www.facebook.com/hackerspace.budapest/photos/a.407034809350059.105001.360688243984716/975141302539404/?type=3&theater https://www.facebook.com/hackerspace.budapest/photos/a.40703...