Re: [Full-disclosure] requesting info
- From: Paul Sebastian Ziegler <psz@xxxxxxxxxxx>
- Date: Wed, 25 Apr 2007 14:28:39 +0200
also what is the right procedure to make in order to publish a new hacking
technique to that it's know by the name of the publisher
First make sure that it is actually a NEW technique. If you just
discovered a new flavor of XSS or some addition to another technique it
won't work. Make sure you know _exactly_ what you are talking about
before releasing such a thing.
Then write _documentation_. That is the key issue. I have no idea who
first came up with BufferOverflows. But I'm pretty sure almost everybody
knows AlephOne. FYI: When he wrote "Smashing the stack for fun and
profit" those attacks had already been around for about a decade.
But his paper hit it off - so he is remembered for it.
Oh, and most off all: Check your attitude.
If your primary intention is fame then there is probably something
wrong. If you are 1337 enough, you'll get accreditation.
MTC
Paul
_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/
- References:
- [Full-disclosure] requesting info
- From: n n
- [Full-disclosure] requesting info
- Prev by Date: [Full-disclosure] requesting info
- Next by Date: Re: [Full-disclosure] Apache/PHP REQUEST_METHOD XSS Vulnerability
- Previous by thread: [Full-disclosure] requesting info
- Next by thread: Re: [Full-disclosure] requesting info
- Index(es):
Relevant Pages
|
|