IT’S NOW ENCRYPTED!!!

There have been a lot of new updates and improvements to psfsp. Here’s all of them:

• Added a better UI for the client side
• Fixed bug where if the file is larger, verifying the hashes would fail.
• Added the ability to query the files available
  and, the big one
• Added username and password authentication

- Added TLS encryption so everything is encrypted including your password and username and the files you download

The TLS certificates are generated locally on the first startup and saved to the home folder. They are self signed and do not depend on a machine name.

Future goals:

• Graphical User Interface for the client (current)
• Ability to delete, rename and upload files
• Compression
• Key based authentication
• Control panel for the server
• DDOS protection

That’s it for now

hashes are cool

It’s new devlog time. There have been a ton of features added to pretty simple file sharing protocol. - First of all, you can share files.

• Second of all, files are hashed to verify their integrity

What are some of the future goals?

• Username / password authentication
• Encryption
• Docker container

Currently known bugs

• If you put the END byte in the file being sent, it will be interpreted as the end of the file and will result in a broken download

What’s the goal of this program?

This is meant to be a replacement for the dated FTP protocol, and even a competitor though there is a long way to go.

PSFSP is a custom file sharing protocol built completely from scratch. It would reroute every new connection to a new thread on an ephemeral port, and send the data in chunks along with hashes. I currently started writing the definitions for the bytes and the documentation for them but also set up cargo and other stuff.