+- Hack Forums (https://hackforums.net)
+-- Forum: Tech (https://hackforums.net/forumdisplay.php?fid=444)
+--- Forum: Coding (https://hackforums.net/forumdisplay.php?fid=151)
+---- Forum: Software Development (https://hackforums.net/forumdisplay.php?fid=118)
+---- Thread: [.NET] [OpenSource][TCP] Secure Socket Protocol3 (/showthread.php?tid=4004452)
* - DragonHunter - Jan 26, 2014
Good to see people like it ^.^
Commit: https://github.com/AnguisCaptor/SecureSocketProtocol/commit/3333a178cd54bd1d13b8f42f948d15562ef171ed
Fix for the Deserializing objects which came from a different assembly
Thanks to Banksy for this fix :)
Commit: https://github.com/AnguisCaptor/SecureSocketProtocol/commit/a06f7f92dad0c954cd8d7cc56a997dcd5d3f7a84
Fixed the stability for the HandShake, it's also more strict now when to receive/send a message
Minor changes to Diffie-Hellman
Channels are working again, this time barely any performance loss!
Some bugfix at receiving packets
And some other minor changes...
* - LethalNET - Jan 26, 2014
yayyy dragon c: I think I may use this in my project c:
* - DragonHunter - Feb 8, 2014
Commit: https://github.com/AnguisCaptor/SecureSocketProtocol/commit/e6cf73f55bd5f15b44bfe0f0b0405574001363bd
Updated the key exchange, it's more powerful now
Updated the onException, it will show if it's user or SSP error
Removed some not used code
Updated the UnsafeXor encryption
Minor changes to the RSA class
Note: If you want to feel more secure grab this update!
* - N3oNight - Feb 11, 2014
Grate to see it back again Dragon,
Keep up the grate work..
* - DragonHunter - Feb 17, 2014
Will commit the changes soon, just making some other security updates
Current changes:
Updated the checksum (data hash) at the messages you're going to send, to make it a little bit harder to modify the messages easily in man-in-the-middle attack
All the handshake messages will get checked with SHA-512bit
Upcoming New features (Both are working but need to check a few things and making sure it's still secure):
SecureStream - Read/Write bytes like you would with e.g. a FileStream or MemoryStream, tested at 150 MegaByte A Second
Requests - Create a request class where messages can be received at and to send back a response, could be handy for a login or a database query you're executing
* - Banksу - Feb 17, 2014
(Feb 11, 2014 01:33 AM)N3oNight Wrote: Grate to see it back again Dragon,
Keep up the grate work..
For the millionth fucking time, it is GREAT.
It is not cheese.
[img]http://pad1.whstatic.com/images/thumb/b/ba/Grate-Cheese-Step-4.jpg/670px-Grate-Cheese-Step-4.jpg[/img]
* - #Kat - Feb 17, 2014
well jeez so many people using it now yes amazing project good job
* - DragonHunter - Feb 23, 2014
I'm having the idea in my head for a few days, thinking about how to make it easier for users how to use SSP
Currently how you'd be able to process messages you're receiving is currently by calling the ProcessPayload(....) from IMessage or casting the IMessage to let's say MsgTest
In LiteCode at the other hand you have to share a class at client or server side and at the other side you're able to do GetSharedClass so you can call methods at the remote side
You'd have to create a Interface and at the other side is the SharedClass with the source code
More information about LiteCode: https://hackforums.net/showthread.php?tid=2655105
Well it's just a thought, I'll put a poll up at the first post, vote and we'll see :)
* - DragonHunter - Mar 8, 2014
Commit: https://github.com/AnguisCaptor/SecureSocketProtocol/commit/c37ba375807706eaa0d405badb38150aacdce849
Merged LiteCode and SSP
Fixed quite a few LiteCode bugs regarding to Delegates and Responses
Fixed a key exchange bug
At disconnect you'll get a reason why it disconnected
Only at the channel you're able to use the Messages
And few other bug fixes
* - DragonHunter - Apr 2, 2014
Commit: https://github.com/AnguisCaptor/SecureSocketProtocol/commit/8ed033e643f758a297380be0fcc72db575f33919
Merged RootSocket project, BETA
Merged LiteCode project, BETA
LiteCode is now a lot more stable then the original release sometime back
Made some adjustments to the handshake as it's more stable now
RootSocket is optimized for the server to handle a lot of traffic with less cpu usage
Made a few changes to the certificate
Added a few encryption methods
Need todo futher testing whether it's completely stable or not
* - DragonHunter - Jun 10, 2014
It's been a while since I've posted progress about the project, but no worries I'm still working at it ;)
The last commits for SSP2 as I'm working on a re-design for SSP3
[Key Exchange security update] https://github.com/AnguisCaptor/SecureSocketProtocol/commit/e6cf73f55bd5f15b44bfe0f0b0405574001363bd
[LiteCode and Key Exchange fixes] https://github.com/AnguisCaptor/SecureSocketProtocol/commit/c37ba375807706eaa0d405badb38150aacdce849
[Handshake fixes, LiteCode, RootSocket and more] https://github.com/AnguisCaptor/SecureSocketProtocol/commit/8ed033e643f758a297380be0fcc72db575f33919
[Certificate Visualization] https://github.com/AnguisCaptor/SecureSocketProtocol/commit/62c56e549fc5a8656e150deadddf939f254cc3a2
If you're interested in the new re-design, look here, https://github.com/AnguisCaptor/SecureSocketProtocol3
Currently it's estimated to reach 800MBps, so I will be trying to maintain this kind of performance ;)
SSP3 is really new so don't use it yet as a project to use, use SSP2 for now if you want to try out my lib 🤝
* - DragonHunter - Jun 28, 2014
Commit: https://github.com/AnguisCaptor/SecureSocketProtocol/commit/a4482292b32b65207ad981111a2442c6ebf9dd05
Replaced the Receiveasync with BeginReceive (ALOT MORE STABLE)
"Random" is now using the server sided seed for randomness, less errors
Updates for LiteCode, some error fixes
Just did this update for people still using SSP2, as I am still working at SSP3
* - taktaktak - Jun 30, 2014
Looks sweet man! Can't wait to use it! +1
* - DragonHunter - Jul 13, 2014
Commit: https://github.com/AnguisCaptor/SecureSocketProtocol/commit/6142f64d990074b820d8a3f3d533e2f1c5b8a19d
New packet to get a random number provided by the server
LiteCode is now more stable because of the id provided by the server (fixes the most annoying bug in the world, Key already exists in the dictionary)
To accept clients we are now using BeginAccept instead of the Async (more stable)
* - Rvaveo - Jul 13, 2014
(Jul 13, 2014 04:38 AM)DragonHunter Wrote: Commit: https://github.com/AnguisCaptor/SecureSocketProtocol/commit/6142f64d990074b820d8a3f3d533e2f1c5b8a19d
New packet to get a random number provided by the server
LiteCode is now more stable because of the id provided by the server (fixes the most annoying bug in the world, Key already exists in the dictionary)
To accept clients we are now using BeginAccept instead of the Async (more stable)
Add some documentation in the wiki or source code. It would make life a lot easier. 😧