StarMirror/toxcore
1
0
Fork 0
mirror of https://github.com/irungentoo/toxcore.git synced 2024-03-22 13:30:51 +08:00
Code Issues Projects Releases Wiki Activity
The future of online communications.
3,982 Commits 2 Branches 1 Tag 69 MiB
C 90.2%
C++ 5.1%
M4 2.6%
Makefile 1%
Python 0.5%
Other 0.5%
7122d2e862
Go to file
mannol 7122d2e862 Use after free reported in #278 occurs because toxav_kill() 
calls msi_kill() (toxav.c:180) which frees msi_call instances (msi.c:161)
which are then used when call_remove() (toxav.c:1136) is called.
This fix prevents call_remove() from calling invalid pointer.

Fixes #278
2016-12-21 00:16:22 +01:00
auto_tests Add test to check if tox_new/tox_kill leaks. 2016-12-20 20:27:51 +00:00
build Fix include paths 2016-01-01 20:28:48 -05:00
cmake Enable all possible C compiler warning flags. 2016-11-06 01:32:10 +00:00
dist-build Removed unnecessary parameters 2014-08-25 10:00:09 +04:00
docs Rebuild apidsl'd headers in cmake. 2016-10-02 23:54:03 +01:00
m4 Build system now automatically enables epoll support in TCP server 2014-07-17 20:44:49 -04:00
other Fix unresolved reference in toxencryptsave API. 2016-12-14 11:35:43 +00:00
super_donators Added my pixfile! 2015-12-12 20:40:57 +01:00
testing add NAT hole punching level to Tox API 2016-11-24 17:38:34 -08:00
toxav Use after free reported in #278 occurs because toxav_kill() 2016-12-21 00:16:22 +01:00
toxcore Avoid array out of bounds read in friend saving. 2016-12-20 14:01:23 +00:00
toxdns Remove return after no-return situation (and other cleanups). 2016-09-30 19:06:44 +01:00
toxencryptsave Remove unused get/set salt/key functions from toxencryptsave. 2016-12-19 15:48:24 +00:00
.gitignore Add and use CMake build script 2016-08-12 01:13:11 +01:00
.travis.yml TravisCI shorten IRC message 2016-10-30 21:04:54 +00:00
autogen.sh Some configuration/build fixes, so building basicaly everything else than the library can be disabled 2013-10-07 02:01:16 +02:00
CMakeLists.txt Add test to check if tox_new/tox_kill leaks. 2016-12-20 20:27:51 +00:00
configure.ac Release v0.1.1 2016-12-17 00:47:08 +00:00
COPYING Removed the unused autotools files 2015-10-05 15:18:55 -07:00
DONATORS If we receive a packet from a node we are searching for, ping it. 2015-12-08 15:43:03 -05:00
INSTALL.md Merge remote-tracking branch 'zetok/docs-install' 2016-10-26 13:07:26 +01:00
libtoxav.pc.in Build system fixes. 2014-12-18 10:04:31 -05:00
libtoxcore.pc.in Move -ltoxcore to be the first linked library 2016-12-12 14:09:34 +01:00
Makefile.am Fixed make dist. 2015-06-24 21:03:16 -04:00
README.md Update readme, moved the roadmap to a higher position 2016-10-17 11:26:17 -07:00
tox.spec.in Add spec file for rpm generation 2015-03-04 00:35:25 +01:00

README.md

Project Tox

Current build status: Build Status Current Coverage: Coverage Status

Website | Wiki | Blog | FAQ | Binaries/Downloads | Clients | Compiling

IRC Channels: Users: #tox@freenode, Developers: #toktok@freenode

Toxcore Development Roadmap

This Roadmap is somewhat tentative, but should give you a good idea of where we're going, and where we've been.

Currently unsorted, the following is intended to function as a discussion guide to developers/contributors.

In Progress

  • Toxcore
    • 100% unit testing
    • Make ToxAV stateless
    • Allow a single toxcore instance to handle multiple keypairs (or 'clients')
    • Consistent naming scheme throughout toxcore
    • Make toxcore stateless
  • Messenger
    • Improve group chat implementation
    • Improve A/V implementation
    • Multiple device support

Done

  • Create Toxcore
  • Create DHT
  • Create Onion
  • Implement Crypto
  • Create Messenger

Q&A:

What is Tox?

Tox is a fully encrypted, censor resistant, private, distributed network library with a focus on personal communications.

No, really, what's Tox?

It's a VERY secure Instant Messenger that supports Text, Audio/Video calls, group chats, audio group chats, and file transfers. There's dozens, but our advantage is we put security first, from day 1. We didn't decide to add it in after.

What are your goals with Tox?

We want Tox to be as simple as possible while remaining as secure as possible.

Documentation:

The Complex Stuff:

UDP vs. TCP

Tox must use UDP simply because hole punching with TCP is not as reliable. However, Tox does use TCP relays as a fallback if it encounters a firewall that prevents UDP hole punching.

Connecting & Communicating

Every peer is represented as a byte string (the public key [Tox ID] of the peer). By using torrent-style DHT, peers can find the IP of other peers by using their Tox ID. Once the IP is obtained, peers can initiate a secure connection with each other. Once the connection is made, peers can exchange messages, send files, start video chats, etc. using encrypted communications.