jesusprubio
Exhaustive checklist to assist in security reviews of Node.js web services
Delightful Node.js packages for pentest, exploit, reversing, crypto
I wanted to implement it in this way. But I'm waiting for async/await, it should be trivial with a map function or something similar. But now it already tries a fallback connection if the first one fails.
Good point about the countries, I need to add an issue to cover it.
You can relax, I know how they work. My final year project was about DoS. I would send you the link but it's Spanish.
But I can say you I've written a tool to implement this vector (among others) against VoIP services and it was presented even at the BlackHat conference.
Please feel free to contribute ;).
But I truly believe in this micro modules way of building things. If it reduces complexity it's welcome. :)
But I truly believe in this micro modules way of building things. If it reduces complexity it's welcome. :)
But I couldn't find a better way to check if I am online than making a request to any server. In fact, I'm using two over different protocols just in case.
About DoS attack, I think you need to review how those work, the library is not implementing amplification or something similar.
So, your solution to "left-pad" is to write all your own code? xD. I think you need to review what was the problem there.
About the support to different services, those are the ones I use in my applications. But you are right, it would be a nice feature. PR's are welcome by the way ;).
The same about IPv6 support, this is an important feature.
Added both as issues: - https://github.com/jesusprubio/online/issues/5 - https://github.com/jesusprubio/online/issues/6
Thank you! :)
Thank you for the feedback!
Thank you for the feedback.
Thinking in a CLI, do you think the timestamp is important? I also had this doubt, but it only bothers me.
Thank you for the feedback.
I prefer to keep lower complexity and there are some crates that cover that case better.
Thank you :).