submit shellcodes

7 views
Skip to first unread message

Ali Razmjoo

unread,
Aug 10, 2016, 6:39:39 PM8/10/16
to OWASP ZSC, owasp-research
Hi friends,

My freind Reza suggested me to submit our daily shellcodes to exploit-db, injector, packetstorm and shellstorm, what's your idea ?

should we report them by a user (example: zsc project) and generate some shellcodes, send them to submit and write our github in description ? it's helps us to get known better.


Ali Razmjoo

unread,
Aug 10, 2016, 6:49:38 PM8/10/16
to OWASP ZSC, Reza Espargham
sorry guys, cced wrong, I've cced Reza now.


johanna curiel curiel

unread,
Aug 10, 2016, 7:53:02 PM8/10/16
to Ali Razmjoo, OWASP ZSC, Reza Espargham
+Ali

I think this a great way to let know your work and promote the project

--
You received this message because you are subscribed to the Google Groups "OWASP ZSC" group.
To unsubscribe from this group and stop receiving emails from it, send an email to owasp-zsc+unsubscribe@googlegroups.com.
To post to this group, send email to owas...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/owasp-zsc/CABtz8XnCjaaguNhcQEQRbAg%3D%2BM_Mwmds5%3DQRVk0crN7-QzQXSw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.



--
Johanna Curiel 
OWASP Volunteer

Akash Trehan

unread,
Aug 10, 2016, 11:06:01 PM8/10/16
to johanna curiel curiel, Ali Razmjoo, OWASP ZSC, Reza Espargham

+1

We should also have a link to the repository in the comments on those websites. Would lead visitors to the repo.


On Thu, 11 Aug 2016 05:23 johanna curiel curiel, <johanna...@owasp.org> wrote:
+Ali

I think this a great way to let know your work and promote the project
On Wed, Aug 10, 2016 at 6:49 PM, Ali Razmjoo <ali.r...@owasp.org> wrote:
sorry guys, cced wrong, I've cced Reza now.


On Thu, Aug 11, 2016 at 3:09 AM, Ali Razmjoo <ali.r...@owasp.org> wrote:
Hi friends,

My freind Reza suggested me to submit our daily shellcodes to exploit-db, injector, packetstorm and shellstorm, what's your idea ?

should we report them by a user (example: zsc project) and generate some shellcodes, send them to submit and write our github in description ? it's helps us to get known better.



--
You received this message because you are subscribed to the Google Groups "OWASP ZSC" group.
To unsubscribe from this group and stop receiving emails from it, send an email to owasp-zsc+...@googlegroups.com.

To post to this group, send email to owas...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/owasp-zsc/CABtz8XnCjaaguNhcQEQRbAg%3D%2BM_Mwmds5%3DQRVk0crN7-QzQXSw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
--
Johanna Curiel 
OWASP Volunteer

--
You received this message because you are subscribed to the Google Groups "OWASP ZSC" group.
To unsubscribe from this group and stop receiving emails from it, send an email to owasp-zsc+...@googlegroups.com.

To post to this group, send email to owas...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/owasp-zsc/CACxry_2_unn6pTAK5MxzFoKoQBM6cS1ckdpNEUYGmBqZMDObRw%40mail.gmail.com.

Paras Chetal

unread,
Aug 11, 2016, 12:23:12 AM8/11/16
to OWASP ZSC
It's a good idea. But we'll have to decide which shellcodes we should upload. Since ours is a dynamic shellcode generator we cannot submit all the shellcodes. We should only submit the more common ones.
Reply all
Reply to author
Forward
0 new messages