Today I brainstormed and solved a server-side problem: basic storage. Since the server will need to store usernames, password hashes, and probably other information in the future, I needed a fast, easy, and lightweight solution to store a bunch of data.
I came up with some ideas of creating my own database system, but they were all either extremely complicated or had way too much overhead. I found a nice simple key-value storage database online which I will be using (yes, I actually used someone else's code this time!). There isn't really much to visualize here, but... twenty ninth step complete!
Thursday, June 25, 2015
Friday, June 19, 2015
Made the Strong Hashing Algorithm Bidirectional!
I've been rather busy lately, and I had some trouble trying to implement known bidirectional (two-way) hashing algorithms, which is why I haven't made much progress lately. I decided instead to build off of my unidirectional (one-way) hashing algorithm from last time and make it bidirectional.
I have just finished doing so, it works well, and, most importantly, it is entirely uncrackable (again, joking). Twenty eighth step complete; here is some sample output in hex form (I can easily change the seed, shared data between both ends, salt, iterations, and hash length):
I have just finished doing so, it works well, and, most importantly, it is entirely uncrackable (again, joking). Twenty eighth step complete; here is some sample output in hex form (I can easily change the seed, shared data between both ends, salt, iterations, and hash length):
Now I can resume work on the login process.
Sunday, June 7, 2015
Strong Hashing Algorithm Complete!
Due to the need for security, as I am currently developing the client-server communication for Fragile, I was in need of a strong one way hashing (encryption) algorithm. So, I found a good one floating around on the internet and improved it significantly.
I have been doing a lot of research lately on secure hashing algorithms, good ways to inhibit hackers, many different ways to mess up encryption, etc., and I'm fairly certain that my hashing algorithm is entirely uncrackable. For those of you who don't know me, that was a joke.
I did put forth my best effort to develop the strongest implementation of the hash that I could for passwords though, and it is versatile in usage and should be resistant to all kinds of malice.
Twenty seventh step complete; here is some sample output, in both integer and hex form (I can easily change the salt, iterations, and key size):
Next, I'll need to implement a good two way encryption algorithm in order to insure Fragile against two things:
I have been doing a lot of research lately on secure hashing algorithms, good ways to inhibit hackers, many different ways to mess up encryption, etc., and I'm fairly certain that my hashing algorithm is entirely uncrackable. For those of you who don't know me, that was a joke.
I did put forth my best effort to develop the strongest implementation of the hash that I could for passwords though, and it is versatile in usage and should be resistant to all kinds of malice.
Twenty seventh step complete; here is some sample output, in both integer and hex form (I can easily change the salt, iterations, and key size):
Next, I'll need to implement a good two way encryption algorithm in order to insure Fragile against two things:
- Hackers trying to steal your password as you set or change it.
- Hackers trying to view, inject, and/or manipulate packets being sent between Fragile and Durable (the server).
Subscribe to:
Posts (Atom)