Good morning!

After a real server hammering from various people, bugs, holes in security, connection flooding, threading issues.... and finally a real corker from Jacob, I have re-written the Server connection handling this afternoon.

I am now fairly confident the Networking Code is solid and the Server cannot be killed (aside from perhaps a DDOS attack on my laptop), but alas I exist to be proven wrong so here you go - Dustmite v0.2!

Some noteable changes:

- No more than one connection will be accepted from a given IP address.
- New connections cannot be made within 5 seconds of the last attempt
- Fixed some client bugs with the Online list
- Fixed handshake packet vulnerability
- Added 3 new layers of Security to the Server involving access to commands
- Complete re-write of Connection handling
- Fixed several threading issues
- Added OS-Specific look and feel to the Client & Server
- Added "always on top" File Menu to the Client & Server
- The Server now has a Chat Log so I can see what you have been up to ^_^
- Tons of re-structuring Server Side...

Please find the download attached to this post in the Forums, as ever - please break it, and let me know how you did it!

Best Regards,
Liam

Edit: Update to v0.3 - Testing out some visual goodies ^_^;

Edit 2: Sorry guys! Still v0.3 but this time I remembered to package the Icons! Please re-download if you already have this version but didn't see any pretty icons :3

Just a progress shot I guess on how things are... progressing ^_^

I know not everyone can be bothored to test it (:cry:) but its always nice to look.

Just noticed from the Screenshots that the version in the Titles of the JFrames is not being taken from the Global Var. Tut tut tut!!

Ok Liam, I am just going to make a list of things that should be fixed and I will gradually add to it.

1. If the Client version is not exactly cased, for example if "Alpha" was put "alpha" or "ALPHA" it will detect an incorrect client version, even though it actually is the same thing, this should be fixed.
2. Null chat text entry needs to be checked server-side, not client-side.
3. Looking...

The client version exact-case is deliberate, as anyone using the client would be oblivious to this!

Null and length checks added, can't believe I forgot those.

In light of your love of Spam the next thing I am adding is packet Spam prevention - I think I have a very good way of dealing with each packets type's maximum number of packets sent within a period of time really nicely it too

Fox

I attempted to rape your server with packets

Nice Anti-Spam!
I couldn't find a way around it!

Time to spam and add to that list.
What does the anti-spam do? Spam back?
I havent found anything that stopped spam yet o.o

Ok.

1. Can still enter whitespace, I just have my client automatically entering a space.
2. I can auto-login.
3. I can still spam tons of packets in seconds.
4. I can still use names longer than 15 characters.
5. I can login with a null name, it should kick me because it is under 4 characters however.
6. The max text is 500, the length inside that chatbox that restricts it to 5000 is worthless, I think you hit zero one too many times.
7. I disconnected god knows how long ago, and now the server still thinks that I am logged in.

I have socket connect anti-spam but no packet spam protection as of yet - I have an idea for a good system that would deal with that and let me specify different times for each type of packet tidily without much code so I'll see to that when I get home.

Good work guys keep it coming ^^