Yakking Yak

Yakking Yak is an end to end encrypted group chat app built with Rust and Node JS for the server.

What is it:

It is a group chat app that uses elliptic-curve diffie hellman to set up an AES-GCM 256 secure channel between devices.

By default, other users are untrusted, and each message is sent encrypted with a specific target user’s shared key.

This app depends on the Rust programming language, and node js.

It uses port 4000 to communicate with the server, so it will have to be opened locally.

On debian based distros like ubuntu do $ sudo apt install libadwaita-1-dev

Clone this repository

Run $ npm install to install required nodejs libraries
Run $ npm run build to build the rust web assembly library to build the pug files to html
Run $ npm run start to start the node server
Run $ cargo run to start the adwaita client

sign in by adding using your username and password or enter a new username and password to make a new account
- note: usernames are only unque locally
use the text box and the go button in the top right to change your chat room
- note: for now you will have to re-establish trust when entering new chat rooms
when the checkbox in the bottom right is off use the text box and send button at the bottom to send unencrypted messages
to trust someone click on their name in the top right dropdown
once you have trusted one or more people and they have trusted you back you can send a message using the bottom text box with the checkbox turned on to send them an encrypted message

Currently Messages are sent to a server to be sent to out to everyone. I plan on changing this to be peer to peer with the server just acting as an address swapping place. Maybe even a system to select the server you want to meet on.
Add passwords to groups?
Fix the randomness of the constants generated at the beggining
Generate a new shared key every so often for increased security

You may need to create a bin folder in the public folder for the program to build into
You can delete the save folder to delete your users for testing or security. Every user's data is saved as flat files in that folder

Web client is gone I dont want to manage two clients at once. It increases the workload too much. I went with libawaita as I want the client to be lightweight, and web clients are anything but.
When voice and video chat is added (probably in the decently far future) there is a significant bandwidth penatly to the way I am handling end to end encryption. The data is encrypted once for each recipt, meaning the bandwidth usage is multiplied by the number of recipients.