Peer 2 Peer Open Source Encrypted Text, Voice & Video Communications

[Xenland]

The new client written in C/C++/QT is about half way done for the total GTK -> QT conversion process. You can find the updates here: https://github.com/Xenland/P2PCrypt-Client

Available thus far in the QT version:
*Shows Generate/Load Identity buttons
*Ability to generate an RSA 2048+ bit identity

Next version:
*Saves identity to database
*Display information from the currently generated identity, and asks to connect to the network or generate a new identity

[1715654924]

1715654924

[1715654924]

1715654924

[1715654924]

1715654924

[Xenland]

https://github.com/Xenland/P2PCrypt-Client/commit/113d5269077a9ff33b830e4d0b73247f9db2dedf

Available now:
*Saved identity to database
*Displayed Sha512 -> md5 (Handle) after generating an identity

Next Version:
*Ask to connect to network with new identity
*Ask to "attach a password to identity
*Ask to go back to the main boot menu

[Xenland]

The goal has been posted up here: https://github.com/Xenland/P2PCrypt-Client/blob/master/README.md
and reposted below for convenience

Abstract Goal of P2P Crypt Client & Servers
Provide global use of communications ran by the world instead of a single (or multiple) centralized controllable entity. To provide free and paid incentives in a way that each server operator will strive to run a P2P Server Node themselves 24 hours a day in either hopes of profit or communication freedom. Also at the same time allowing "mixed" incentives for the server operator to set-up their node how they wish to be compensated for their clients to use their services so that there will be a good balance of "Free" and "Paid" services.


More at the link above....

UPDATED (EDITED)
Link was updated to proper link, it was really late for me when i posted this....

[Xenland]

For the p2pcrypt web version we'll be using this, just leaving this here for notes for later
http://www-cs-students.stanford.edu/~tjw/jsbn/

[bitjoint]

Interesting project.. but I'm wondering why aren't you building it on top of existing open solutions focused specially on P2P audio/video communications.. i.e: OpenPeer... https://github.com/openpeer/

I think the most difficult part will be the implementation of the audio/video engine and the always-present "NAT traversal" issue. So a WebRTC stack is defo the way you want to go, cos all that problems are already solved. Also, DTLS-SRTP point-to-point Encryption is built-in and mandatory for WebRTC.

http://www.ietf.org/proceedings/82/slides/rtcweb-13.pdf

Maybe you should take a deep look at P2P/WebRTC oriented technologies (OpenPeer, Peer.js, etc) and extract how they have solved the common issues for this kind of deployments (NAT traversal, DHT Nodes configuration, identity managament, etc), and then explore the way to extend it to the level of security you want.

I don't know if this helps, but either way... Good luck!

[Xenland]

Interesting project.. but I'm wondering why aren't you building it on top of existing open solutions focused specially on P2P audio/video communications.. i.e: OpenPeer... https://github.com/openpeer/

I think the most difficult part will be the implementation of the audio/video engine and the always-present "NAT traversal" issue. So a WebRTC stack is defo the way you want to go, cos all that problems are already solved. Also, DTLS-SRTP point-to-point Encryption is built-in and mandatory for WebRTC.

http://www.ietf.org/proceedings/82/slides/rtcweb-13.pdf

Maybe you should take a deep look at P2P/WebRTC oriented technologies (OpenPeer, Peer.js, etc) and extract how they have solved the common issues for this kind of deployments (NAT traversal, DHT Nodes configuration, identity managament, etc), and then explore the way to extend it to the level of security you want.

I don't know if this helps, but either way... Good luck!

Thanks for the loads of resources, The only thing i can respond to at the moment is the NAT traversal in my notes the solution is to have "pings" to out going connections of peers that are labled as always on. to keep the ports open. I don't know if that is related though or not.

[zero3112]

Is there a way to encrypt a regular text messages on a cell phones using today's network?

[Xenland]

Is there a way to encrypt a regular text messages on a cell phones using today's network?

not unless you want to pay ALOT of text message fees.. as i think one message of 1024 characters divided by the (240 or 140?) limit multiply that times txt fees

[fixxi.net]

Great Project.

Any plan to get the chat / voice system work on Windows ?

[CIYAM]

Any plan to get the chat / voice system work on Windows ?

I believe that Xenland is going to use Qt for the UI so a Windows version shouldn't be a big problem.

BTW - the project is listed on CIYAM Open (http://ciyam.org/open/?cmd=view&data=20121222131254938000&ident=M100V137&chksum=24be696c) so if anyone wants to contribute then 14NqZ1w7x9gFFzt65Mxy38EPFrbrnR11is is the relevant address (that address is under Xenland's control - please confirm that with him if at all concerned).

[Xenland]

Great Project.

Any plan to get the chat / voice system work on Windows ?

short answer yes

[Xenland]

I posted on another thread I was going to release my compiled prototypes into one professional put together client & server apps, I will be doing that today and posting on this thread(Didn't get to finish it last night). So if you are interesting in this project, gather testers