disposable-email-domains VS SQLMap

The block list seems to come from https://github.com/disposable-email-domains/disposable-email-domains/ — I think you should cite your sources even if it’s distributed as public domain

This post is a response to https://github.com/disposable-email-domains/disposable-email-domains/pull/298 since they have (probably wisely :) locked down comments. They propose adding Firefox Relay domains to their blocklist.

And this is why users protect themselves with services like Firefox Relay, something Dustin Ingram, a Python Software Foundation Director, doesn't appear to understand [1] or care. My email was leaked in this breach, along with many others, an email I used to really value but one I've relegated to the dumpster fire of "spam slot" because I learned my lesson too late.

Dustin has now locked that GitHub to only previous contributors so users are once again left voiceless and powerless in the continuing war against their privacy.

We've been thinking of the business owners and the children [2] for decades now. It's time to start thinking of the users, people like you and me who are exploited constantly for everything they have to be unceremoniously discarded in a waste heap once they've been used up.

[1] https://github.com/disposable-email-domains/disposable-email...

[2] https://news.ycombinator.com/item?id=29978952

sqlmap

A few weeks ago, I took a short cyber security course on Udemy. SQL injection was a section of the course. I knew about the concept though, I hadn't tried it. I was planning to make a Restful API server and tried SQL injection using a tool sqlmap, which was introduced in the course. While I could have used existing server code, I decided to build one from scratch. It's been a while since I worked on a Restful API server, and I wanted to refresh my knowledge for learning purposes.

I recommend looking for an alternative or if you must do it this way test it with https://sqlmap.org to make sure you are not vulnerable to the lowest effort attacks.

The DAST checks can be automated up to a certain point, where the code should be able to withstand certain scans and attacks. For eg. SQL Injections can be checked with sqlmap which tests with each and every type of sql injection payload and reports it back to the user.

git clone --depth 1 https://github.com/sqlmapproject/sqlmap.git sqlmap-dev

Sounds good, why not try making a simple vulnerability scanner for APIs too? Maybe something similar to SQLMap

Its not that much of a tool than wrappers of few awesome tools that most of you probably know and use today - sqlmap, bbot and nikto.

I'm excited to share with you my latest contributions to the GitHub community: a collection of free GitHub Actions designed to streamline and enhance security practices utilizing DAST and OSINT tooling that is widely used - sqlmap, bbot and nikto. There were no GH Actions that I could find, so I made them for my use case, but figured everyone can benefit from those awesome tools.

SQLMap