@mikelo2 do you have a status on your article?

Busy at work, will try to have it by mid June or end of June.

@mikelo2 any update on this article?

Good morning, I joined recently and was looking for a way to contribute. If mikelo2 is busy with work and family duties that can happen quite often these days, I would be glad to write a draft respecting the bulet points mikelo2 outlined in the description. Modsecurity landscape and context can be quite hard to grap and understand let alone put in a production environment. Do let me know if you agree.

Hi @rlengland Added a small draft here
https://fedoramagazine.org/?p=39012&preview=true&preview_id=39012

Since @mikelo2 proposed this article I think it only fair if they have a say in turning it over to you.

Perhaps you two can collaborate on it?

Let's wait for his input

Hi @mikelo2 , I hope you're well, not sure how the collaboration is supposed to happen, I could not find a way to reach you.

@romangherta I would say a month is enough time for @mikelo2 to respond so if you want to carry on with this article I say go.

Keep us abreast of your status and drop a WP preview link here whe you are ready for a review.

Thanks.

Good evening @rlengland
To be fair I contacted mikelo on linkedin without success. I think the idea for this article was very good I remember googling a few years back trying to find some working examples.

I attach a preview here
https://fedoramagazine.org/?p=39012&preview=true&preview_id=39012

there is currently an outdated rpm mod_modsecurity_crs package. I decided to import the latest rules from github, using with this occasion a little bit of tar commands. It was tested on fedora 38 and 39 with selinux enabled... Any questions or ideas of improvement do let me know. I did not want the article to be loo long and confusing.

@romangherta Your article has been edited and scheduled to go live on December 4th at 08:00 UTC. Let us know with a comment here if you see any problems. Thanks for your contribution to Fedora Magazine!

No problems from my side @glb although I know you must have felt insulted when you saw those sudo commands but there was no way of making this short and clear. I would appreciate if we could omit my name from the article if the system allows it... since the article wasnt my idea and to eliminate further rants. If not, I am still opk with that. See you in the kubernetes thread later on.

... you must have felt insulted when you saw those sudo commands but there was no way of making this short and clear.

I don't see any problem with the commands. But if you are concerned about the article in any way, we can still cancel or delay its publication. Just let us know if you want to do that.

I would appreciate if we could omit my name from the article if the system allows it... since the article wasnt my idea ...

The "Posted by ..." line doesn't indicate who had the idea to post about the topic. It indicates who authored the content. "Openness" (including who created the content) is part of the Free and Open-Source philosophy and the Fedora Magazine policies include properly citing the name of the author (docs.fedoraproject.org → Fedora Magazine → Editorial Checklist → Formatting). We do not want to post anonymous content on Fedora Magazine. If you are uncomfortable with this, we can still retract the article.

... and to eliminate further rants.

I fully understand that you do not want to see any negative comments that the readers might make about your article. The best way to do that would be to create a filter in your email client to automatically send any emails related to this article to the trash. Also, since you have stated that you do not want to see any "rants", I will be more discriminating than I normally am when it comes to moderating the comments to your article.

Thanks.

Thanks for the explanation. All good from my side.