TCPChat
Description:
Multi-user chat with mixed architecture: client-server, p2p. Server tightly works with certificates. Server and users should have certificates. But program can generate self signed certificates that supports too, but with some peculiarities.
First of all if server has self-signed certificate then users that connect to him will be warned. Users also can use self-signed certificates, if them have it, then them will be marked with the appropriate icons in users list. Also user can save certificates to local trusted TCPChat storage.
Here is this user icons:
This is approved certificate. This certificate is valid or it was saved in local TCPChat trusted certificates storage. Also user nick match to certificate common name.
This is also approved certificate, but nick does't match to certificate common name.
This is not approved self-signed certificate.
Main idea:
Main idea of this project - is multiple servers without databases. Where you can find friends and recognize that this is really them with he help of certificates.
Server address:
IP: 93.170.186.160
Port: 10021
Server certificate tumbprint: 839292da057678529acd42f414a51f8f8b16d1ff
Server certificate: file
Supports:
- Full trafic encryption. Key exchange with certificates. AES-256 CBC.
- Private messages. (P2P)
- Rooms.
- Voice chat. (P2P)
- Files sharing. (P2P)
- Plugins (Example of simple plugin: https://github.com/Nirklav/ScreenshotPlugin).
P2P means that connection is established directly between clients without server.
OpenAL required for audio services. You can download it from official site.