Thanks for the video! I love how you don't edit out the problems you run into - it's very helpful to see how you work through them. Thanks again, and keep them coming!
i m watching all your videos and your content is just amazing ! thank you for the efforts that you are putting u re really helping a lot of people out there.
Can you Please upload the script for the slack webhook and a export from the task scheduler to GitHub? Id love to not have to retype the whole thing ;-}
Is this approach vulnerable to command injection? If an attacker is capable of controlling the filename they could attempt to write to: "&& malicious_command && exit", which should also prevent the Slack notification from coming through.
Thanks for the video! I love how you don't edit out the problems you run into - it's very helpful to see how you work through them. Thanks again, and keep them coming!
"Wait a second, it worked! It shouldn't happen !" That sums it all for me
i m watching all your videos and your content is just amazing !
thank you for the efforts that you are putting u re really helping a lot of people out there.
This is the most beautiful thing I've ever seen. I love You
This is SO COOL!
This is amazing.
Good Content !!!
wo! thanx
Awesome! Thanks!
Can you Please upload the script for the slack webhook and a export from the task scheduler to GitHub?
Id love to not have to retype the whole thing ;-}
Top ! Thanks
You can send any message from any user with the token not sure if that's a risk.
There's no way to really get around that, it's limited to sending messages and to the channel.
Is this approach vulnerable to command injection? If an attacker is capable of controlling the filename they could attempt to write to: "&& malicious_command && exit", which should also prevent the Slack notification from coming through.
You should try it out. I did try it briefly and it didn't work but I didn't spend a lot of time on it.
If YMS was a hacker, you'd have Ippsec