Darkwire.io alternatives and similar software solutions
Based on the "Custom communication systems" category.
Alternatively, view Darkwire.io alternatives based on common mentions on social networks and blogs.
9.4 9.8 Darkwire.io VS ChatwootOpen-source customer engagement suite, an alternative to Intercom, Zendesk, Salesforce Service Cloud etc. 🔥💬
9.1 8.9 Darkwire.io VS TinodeInstant messaging platform. Backend in Go. Clients: Swift iOS, Java Android, JS webapp, scriptable command line; chatbots
8.7 4.5 Darkwire.io VS GotifyA simple server for sending and receiving messages in real-time per WebSocket. (Includes a sleek web-ui)
2.7 8.2 Darkwire.io VS PushBitsA simple server for push notifications via Matrix (and a minimalistic alternative to Pushover and Gotify with a strong focus on security) 🚀📯
Do you think we are missing an alternative of Darkwire.io or a related project?
Darkwire server is a Node.js application that requires redis.
Darkwire Web Client
.env.dist files in
client/ directories without the
extensions and adapt them to your needs.
You need Redis in order to make the server works. A simple way to achieve this, if you have docker, is to execute the following command:
docker run --name darkwire-redis --rm -p 6379:6379 -d redis redis-server --appendonly yes
Alternatively, you can select the memory
STORE_BACKEND instead of redis
in your server
.env file to avoid Redis use.
Start server and client
$ yarn setup $ yarn dev
Just run the following:
$ docker-compose up
This will automatically create the default
.env files, and run redis for you.
Create server and client production builds
$ yarn build
$ yarn start
$ docker build --tag darkwire.io:latest .
Then run it. Example:
$ docker run --name darkwire.io --env STORE_HOST=redis://redis.host:6379 darkwire.io
You are able to use any of the enviroment variables available in
client/.env.dist. The defaults are available in [Dockerfile](Dockerfile)
Please report any security issues to
How it works
Darkwire uses a combination of asymmetric encryption (RSA-OAEP), symmetric session keys (AES-CBC) and signing keys (HMAC) for security.
Here's an overview of a chat between Alice and Bob (also applies to group chats):
- Bob creates a room and immediately creates a public/private key pair (RSA-OAEP).
- Alice joins the room and also creates a public/private key pair. She is sent Bob's public key and she sends Bob her public key.
- When Bob goes to send a message, three things are created: a session key (AES-CBC), a signing key (HMAC SHA-256) and an initialization vector (used in the encryption process).
- Bob's message is encrypted with the session key and initialization vector, and a signature is created using the signing key.
- The session key and signing key are encrypted with each recipient's public key (in this case only Alice, but in a group chat multiple).
- The encrypted message, initialization vector, signature, encrypted session key and encrypted signing key are sent to all recipients (in this case just Alice) as a package.
- Alice receives the package and decrypts the session key and signing key using her private key. She decrypts the message with the decrypted session key and vector, and verifies the signature with the decrypted signing key.
Group chats work the same way because in step 5 we encrypt keys with everyone's public key. When a message is sent out, it includes encrypted keys for everyone in the room, and the recipients then pick out the ones for them based on their user ID.
Darkwire does not provide any guarantee that the person you're communicating with is who you think they are. Authentication functionality may be incorporated in future versions.
Darkwire encodes documents into base64 using btoa and is encrypted the same way chat messages are.
- When a file is "uploaded", the document is encoded on the client and the server recieves the encrypted base64 string.
- The server sends the encrypted base64 string to clients in the same chat room.
- Clients recieving the encrypted base64 string then decrypts and decodes the base64 string using atob.
The default transferable file size limit is 4MB, but can be changed in
.env file with the
Sockets & Server
Rooms are stored in memory on the server until all participants have left, at which point the room is destroyed. Only public keys are stored in server memory for the duration of the room's life.
Chat history is stored in each participant's browser, so it is effectively erased (for that user) when their window is closed.