Sociopath Community

It's a shame you didn't get to the actual spamming part though.

and then other times I log in as jim, just to switch things up a little bit and fuck with you stupid twats.

okay if you are such a HAXXOR then what are the basics of buffer overflow attacks, and what type of XSS did you use to kill the chat?

Simply put a Buffer attack attempts to overflow a systems memory so it can exploit malicious code on the other end. As for Cross site scripting... Well... Who said that's what I used?

because if it was you jim, you'd remember you already told me...

Maybe I'm not really Jim after all...

We are legion... ;)

See, you decided to start off as an idiot from the first second, you should have switched to it later, but can't blame you for being yourself.

First of all I didn't use XSS.

I connected to the WebSocket server and caused a stack overflow by filling the Node.JS process memory and making it crash. This is called an memory overrun.

Second of all, buffer overflow is the kind of an attack where you fill a memory segment with data more than the allocated segment can handle, causing the excess data to spill into the other parts of memory. If you are smart enough, you can even re-write the return address of the application, making it execute the payload (possibly a backdoor) in another memory segment.

And XSS means Cross-site scripting. There was no client-side scripting done for this hacking.

Please learn at least basic computing skills before trying to challenge me, thanks.

No you used this http://www.christian-schneider.net/CrossSiteWebSocketHijacking.html remember. It did make for interesting reading though. I will have to be careful with html5 sockets from now on. I was just testing daddy which does in fact appear to be you. That I never saw coming after your chat battles with him before you killed the chat. I might be wrong though. So hard to tell when dealing with people over the internet.

"I connected to the WebSocket server and caused a stack overflow by filling the Node.JS process memory and making it crash. This is called an memory overrun."

Where do you see the difference between your link and my description? I hope you are trolling me, you can't be this stupid.

As in the article, I connected to the WebSocket server using my PHP session cookie, the encryption key, and launched a 20.000 message sending, which got the chat server from luna's host to have it's process memory filled up over limit and die in a stack overflow.

 Also, I told you that connecting to the chat server directly was my idea 10 minutes before finding the article searching "websocket cookies" on Google. 

I didn't know that I would crash the server though, it's an awesome occurence

Of course I am teasing you. Sometimes humor doesn't come across text. No need to twist your panties up any higher.