Home

TacoNET

What is TacoNET? It's an open-source, Friend 2 Friend, cross platform, encrypted Darknet written in python. Currently in Alpha, it's functional, but nowhere near what it will be. There will be gui weirdness, useless error messages, spelling/grammer mistakes, and of course some features may not work 100% in all cases. This will, of course, improve over time.

Quick Links

• Want to get TacoNET Installed and running? See: [How to Install]
• Want to get TacoNET to do something once it's installed? See: [Configuring TacoNET]
• Want to understand the TacoNET protocol? See: [The TacoNET Prototol]

Features

• Open Source
  • TacoNET itself is released under an open source license.
  • Some of TacoNET's dependencies and includes may be released under different licenses. Check the relevant readme's for their specifics.
• Cross Platform
  • TacoNET is written in Python, and has minimal dependencies. We actively develop on both linux and windows system. We test it every step of the way to ensure cross platform functionality. None of us have MacOS machines, but we assume it should work there as well.
• Friend 2 Friend
  • TacoNET utilizes no centralized server. It's 100% peer 2 peer. We call it Friend to Friend, as we recommend you know and trust all the people with whom you set up a TacoNET.
  • Since TacoNET has no centralized server, and is friend 2 friend, it will not scale well. We currently recommend your TacoNET consist of less than 50 active peers.
• Encrypted
  • TacoNET use 256 bit AES Encryption. Don't know much about AES? Google it, it's what the US Goverment uses. It's rock solid. Any encryption method is only as good as the keys and passwords you set up, but that's up to you. Use good passwords, and keep them secret.
  • There is no, over-the-wire, key exchange. Everything except the AES Initialization Vector are sent encrypted. A good AES Initialization Vector is to AES Encyption what a good salt is to hashing. Sending an IV or Salt unencrypted is not in and of itself insecure, and is commonly done. Too much techno-talk? Basically, it's encrypted. Don't worry.
  • TacoNET Peer Encryption Keys must be manually exchanged with at least one other peer. See [Configuring TacoNET] on how this process works.
• New Node Discovery
  • Once a new peer is added to your TacoNET, all other peers are made aware of it's existence, and all relevant info need to communicate with it. Peers must still be manual enabled from there, a simple "check box" will do this for you. Make sure you trust who you enable. See [Configuring TacoNET] for more info on this.
• Peer File Browsing
  • Once a peer has set up some shares, you can start browsing their files. Our goal is to keep this a very simple, easy to understand interface.
• File Transfers
  • TacoNET has support for download queues and file transfers from peers. It can enforce upload and download rate limits if you wish.
• Chat
  • There is a rudimentary chat client built into TacoNET should you want to send simple messages between TacoNET peers.
• No Logging
  • We may change our minds on this at some point, but currently TacoNET saves no information between program restarts about your download queue, files you downloaded, or chat logs.

Planned Features

• Search
  • At some point, you'll be able to search for files amongst all your TacoNET Peers.
• Subscriptions
  • At some point, you'll be able to "subscribe" to remote directories on a peer. TacoNET will then monitor and transfer any new files that show up and transfer them to you.

Word of Warning

TacoNET is in alpha, there may be security issues or huge bugs. Run at your own risk for now. We have reasonable confidence that the alpha has no major security flaws. Wait until beta if you want to play it safer.

Lots of validation and troll prevention is not coded in this alpha. You can break your connection pretty easy, and be a pain to your peers. This will all be improved as time goes on.

Need Help?

Put in a trouble ticket, or email TacoScott.

email address: tacoscott at symbol users dot sourceforge dot net