2 ms·
> He has his bona fides; where are yours? I called him out for his specific replies in this specific thread. I didn't call out his reputation or character. Ma
by Someone1234 11y ago
> He has his bona fides; where are yours?
I called him out for his specific replies in this specific thread. I didn't call out his reputation or character.
Maybe you should stick to what they and I actually posted here today, and not try to draw the conversation off track into reputation wars.
> It's entirely unnecessary to be a jerk towards him for saying this.
I don't appreciate being called a "jerk."
I stand by what I said, and what I said was that I felt (and feel) that they have a bad attitude to security. They're trying to shift blame from the rails developers to every rails user, and their excuses are weak.
If you think that is "jerky," that's fine, but I feel like name calling and playing the reputation card for no reason is only going to take a conversation down a bad and unconstructive path.
- enraged_camel 11y ago>>I don't appreciate being called a "jerk Then try not to sound like one? The OP went out of his way to compile and document the important bugs and post them here. You, on the other hand, completely ignored the value of his contribution and instead rudely called him out on a very minor (and frankly, subjective) tonal issue, and went so far as to call it "whitewashing," which implies that he has an agenda.
- ryanlol 11y agoDid you not notice how OP had absolutely nothing to say about the more serious bugs and instead entirely focused on the less serious ones? (Except for the rails-html-sanitizer bug, which is fairly serious) He does make multiple valid points though.
- bpchaps 11y agoI don't understand comments like these.. He's pointing out a legitimate attitude problem which I, and many others, also agree with. There's absolutely no need for the flippant attitude. If the users of your framework are consistently causing major security problems and the framework is built in a way that it can't be fixed without compromise.. I dunno.. document it? Maybe? Your documentation is basically the API to learning your framework, so if the API is broken to the extent of causing security problems, then it's not god damn production ready! Remember, if every student is failing your class, the student probably isn't the one to blame.
- enraged_camel 11y ago>>Remember, if every student is failing your class, the student probably isn't the one to blame. Except not every student is failing the class. Only those not following best practices are. For example, if you're using params.permit!, you're simply being lazy. This is clearly documented[1]: "Extreme care should be taken when using permit! as it will allow all current and future model attributes to be mass-assigned." [1]https://github.com/rails/strong_parameters#permitted-scalar-values https://github.com/rails/strong_parameters#permitted-scalar-...
- brazzledazzle 11y ago>I called him out for his specific replies in this specific thread. I didn't call out his reputation or character. Eh, I'm not sure about that. When I see "Wow you have a terrible attitude about security" I'm inclined to think that's exactly what you're doing. I don't have a horse in this race but you seem to be unnecessarily aggressive/antagonistic and you could have discussed the individual merits of his comment without doing that.