Practical Laravel Security update

Dear friends,

It's been a while since my last Practical Laravel Security update, so I wanted to reach out and let you know what's going on.

In my original schedule for building the modules, I was going to have the Cross-Site Request Forgery (CSRF) module, the SQL Injection (SQLi) module, and the next Attack module, along with their associated Defend modules, completed by this point. None of that has happened, and for that I apologise.

To give you a bit of a sense of why the modules are delayed, February and March have been the hardest 2 months of my life. I won't go into any details, but in short, a couple of different family crises have layered on top of each other to drain me utterly, and finding time to work on the course has been virtually impossible. Things have finally reached a point where they can't really get any worse, which I hope means they will start improving, and I'm working on changes that will allow me to dedicate the time and energy I need to build the course.

I am still very excited about the course and I have a lot of great plans. It may take longer than expected, but I promise I won't let you down, and the course will definitely be worth the wait. I want to thank each of you sincerely for your interest and support. It means so much to me that over 400 people have signed up to the announcements list and care about Laravel security. 🥰

Regarding the upcoming CSRF module - I am hoping to have it out next week, if I can. As a teaser, for those who have already signed up for the course, the first two CSRF challenges are up for testing - check them out here. (You'll need to use that link, it's hidden from the modules list.)

Once again, I apologise for the lack of updates and delays with the course. I hope you can understand why, and I promise more course modules are coming soon. 🙂

Thanks,
Stephen