Evil people probably won't bother to leave positive comments, so I wouldn't judge the impact of your article based on a few positive comments.
Articles that are truly designed for positive security impact usually focus on mitigation and prevention. Here you have almost none of that info. It's more like a "look at all the ways I know how to mess up a system - you can copy and paste these!"
It's great to discuss security risks, but if you don't talk about techniques for prevention, then it's really just a cookbook of evil recipes.
Thanks again for your explanation. I agree with your last point, so I added a 🛡 section for each point explaining some ideas of prevention for the corresponding bash command.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Evil people probably won't bother to leave positive comments, so I wouldn't judge the impact of your article based on a few positive comments.
Articles that are truly designed for positive security impact usually focus on mitigation and prevention. Here you have almost none of that info. It's more like a "look at all the ways I know how to mess up a system - you can copy and paste these!"
It's great to discuss security risks, but if you don't talk about techniques for prevention, then it's really just a cookbook of evil recipes.
Thanks again for your explanation. I agree with your last point, so I added a 🛡 section for each point explaining some ideas of prevention for the corresponding bash command.