|
1 |
| -# IPFSS_IPFS-Secure |
2 |
| -A unique IPFS frontend that you can use to push your files through. Encrypt all traffic with a Asymmetric RSA keypair. Ensure that you can upload private data to IPFS, and only you can receive and view on another machine. The HTTPS of IPFS. |
| 1 | +# IPFSS / SecureIPFS |
3 | 2 |
|
| 3 | +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. |
| 4 | +Recommended to use keycard, Apex, or Keycard for Multi Factor Authentication (MFA) |
4 | 5 |
|
5 |
| -# SecureIPFS |
6 | 6 |
|
7 | 7 | SecureIPFS 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.
|
8 | 8 |
|
| 9 | +## For developers |
| 10 | + |
| 11 | +1. **IPFS Kubo Implementation.** |
| 12 | + - I can do this but some help would be appreciated. |
| 13 | + - Just need to add IPFS Kubo implementation - this is just a front end for IPFS Get and IPFS Add. |
| 14 | + |
| 15 | +2. **Keycard Implementation.** |
| 16 | + - This is stage two and if you are a developer wanting to help, make a fork, see /Docs/* and add your software, finish / upload with a pull request. |
| 17 | + - Ive therorised a way to securely use the keycard for encrypting and decrypting data. Since a EDCSA Signature is unique to the signers private key and the data they are signing. This is all we need. |
| 18 | + - You just reverse the process, the file is not being signed, the users unique passphrase is. This way the unique EDCSA signature is unique to the user and the application, |
| 19 | + - This way an attacker cannot decrypt the IPFS data without the keycard, and they cant just scan the keycard, the need to know the passphrase used for that file, and swipe or otherwise steal the keycard. |
| 20 | + - This is a way of using in vivo crypto coprocessors for secure MFA and file privacy / security. |
| 21 | + |
| 22 | + |
| 23 | +## From Dangerous Things with love. |
| 24 | + |
| 25 | +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. |
| 26 | + |
| 27 | + |
| 28 | + |
| 29 | +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. |
| 30 | +*A load and swipe process.* |
| 31 | + |
| 32 | +>"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." |
| 33 | + |
9 | 34 | ## Key Features
|
10 | 35 |
|
11 | 36 | - **Asymmetric Encryption**: Utilize RSA encryption to secure your files. Files are encrypted with a public key and can only be decrypted with the corresponding passphrase protected private key.
|
|
0 commit comments