Rebranding project from IPFSS to Dagnerous-net
- To avoid confusion with the IPFS protocol and to also referance the great support from the Dangerous Things community.
- Dangerous-net is not affiliated with, a part of, or owned by Dangerous Things, it is a community project.
A unique IPFS frontend that you can use to push your files through. Encrypt all traffic with a Asymmetric RSA keypair and GPG. Ensure that you can upload private data to IPFS, and only you can receive and view on another machine. The HTTPS of IPFS.
Recommended to use keycard, Apex, or Keycard for Multi Factor Authentication (MFA), encrypting and decrypting data. Using IPFS in general.
Dangerous Net is an application and library set that integrates the InterPlanetary File System (IPFS) with robust RSA encryption in Go, providing a secure method to store and retrieve files. It encrypts files before uploading to IPFS and decrypts them using a corresponding key pair. The project will also be expanding into a self-sufficient decentralised network for messaging, file transfer, cloud like storage, and incentivisation to contribute to the network.
In order to accelerate development I am accepting bounties for people who can build the below implementations
- IPFS Kubo Implementation. >
0ETH
- ✅ Complete
- Keycard Implementation. >
0ETH
- ✅ Complete
-
Ways to contribute:
- 🟡 Anything in issues is fair game to fix or submit an enhancement for.
-
IPFS Cluster Implementation 0.05 ETH
- ✖️ TO DO!! Implement IPFS clustering so that all users of this application can opt in for the Dangerous Net, the IPFS cluster keeping your encrypted files available and ready to use anytime anywhere.
-
GPG Applet Integration 0.025 ETH
- ✖️ Build support for the GPG / PGP applets used in keycard and flexSecure implants.
- ✖️ Allow for encryption on chip outside of the application and machine itself, use the in-vivo crypto chips.
The Apex Flex and FlexSecure allow us mortal humans to perform cryptographic functions in vivo (under the skin) this fact paired with the above cryptographic MFA, provides the user a secure way to keep their data safe.
You may be asking "but satunix why is this so special?" "These implants can do PGP and OTP!!!" Well, they sure can, but thats it, good luck loading several applets onto your keycard for each purpose, then trying to navigate and use all of the different block positions keys, algorithims.... and whatever tf. Me personally, I kave a FlexSecure loaded with Keycard. Thus, Keycard must be used for this process. This allows even the noobiest of users ease of control and access. A load and swipe process.
"The ability to carry your OTP authenticator, PGP, and other cryptographic keys, and perform cryptographic functions all in vivo (generate OTP codes, encrypt & decrypt data, etc.) without ever revealing private keys to the NFC interface you are interacting with is a huge step forward for personal digital identity and data security."
- Asymmetric Encryption: Utilize AES encryption to secure your files. Files are encrypted with a temporary AES key, its generation of which depends on random machine generated phrases + user password + keycard implant data.
- Symmetric Encryption: Utilize a Apex or FlexSecure implant with keycard to use Multi Factor Symmetric encryption on your files, supply a passphrase, scan your card, files secured.
- Decentralized Storage: Leverage IPFS for secure, encrypted, decentralized, and immutable file storage.
- Go Implementation: Built with Go, taking advantage of its powerful concurrency features and efficient data handling.
Before you begin, ensure you have the following installed on your system:
- Go programming language
- IPFS daemon running locally or accessible remotely
- Relevant Go libraries for IPFS and encryption
- Run binary
- OR Build
go build && ./Dangerous-net
Contributions to SecureIPFS / Dangerous Net are welcome! Please read our upcoming contributing guidelines for details on how to submit pull requests. For now just create a fork and then create a pull request with your changes.
This project is licensed under the MIT, Apache2 and GPL3 License - see the LICENSE file for details. Much credit to the IPFS, Keycard, and AES / GPG developers for inspiration and library support for this project. See acknowledgements bellow.
- IPFS Team for the IPFS protocol
- Go community for the extensive libraries and support
- All contributors who participate in this project
2023
- Completion of initial encryption and sys arg functions / data flow to ipfs get and ipfs add.
Early 2024
- Completion / Signifficant progress towards the Dangerous Net (Building scalable decentralised infrastructure for cloud storage)
- Usage of JAVA Keycard or other implants for storing the CID log
- Encryption on chip
- Upload rule set, provide double of uploads, node uploads is under 50% of total size, monetisation of uploads via blockchain signing and CID list smartcontract.
- Checking function to check if CIDs on cluster are incentivised.
- if not paid for > cluster unpin CID
- Uptime incentives, airdrops / ETH streaming to follower nodes based on storage provisions.
- Downtime disciplinary action, culling of files if base node off-line for 30+ Days
- Exploration of other additions, social networking, news feed, basic marketplace via ETH/WAN and IPFS integration (required monetisation of storage)
Late 2024
- Reach of critical mass of the Dangerous Net by application users to support itself and be self sufficient.
- Decentralised network needs to reach a critical undertermined size to support itself without daemons running in cloud or in my own servers while also maintaining full file availability.
Late 2024 to Early 2025
- Android support
This project is going to undergo a major overall in networking capability
Donations are not needed, though are very welcome to support this project and speed up the expansion of the network, all funds sent will directly go towards hardware for this project to support the Dangerous Network.
Uploaded under GPL3.0, MIT, and Apache 2.0 licenses as per dependency usage
copyright C2023 Tritium Cyber Defence All Rights Reserved