td4b / gocrypt

Encrypt & Share Data Securely with Go/IPFS

GoCrypt

Work In Progress

When your afraid of forgetting a bunch of secrets.

Keep one in you're head.

With AES256 bit encryption, expedient they said!

Description

This is a CLI tool for encyrpting and uploading files to the IPFS blockchain network. The tool also generates unique file signatures and records them in a local database for one to keep track of the files. The reason behind this is due to the nature of AES256, at some point potentially a second block chain could be leveraged to track (file uniqueness). This would be the "Public" or non-confidential metadata assosciated with a file. The data will be nearly impossible to decrypt unless the client has the private key since the encryption method is symmetric (AES256).

Done.

• Migrated IPFS Node to Container System.
• Migrated Postgres Services to Container Service.
• Updated golang routines to support Postgres Container Service.

TODO.

@@ GoCrypt @@

• Migrate additional Services over to Containers.
• Need to implement multiple API's & MicroServices to support this.
• Remove I/O Based Encryption method and implement an HTTP interface for this.

@@ Sending a File @@

 curl --request POST --data-binary "@secret.pem" \
      http://192.168.0.215:8000/upload/secret.pem=secretpassword

@@ Getting a File List @@

http://192.168.0.215:8000/api/

@@ IPFS @@

• Configure Persistent Data Caching.
• Configure Private Node Network (SSL Verification).

@@ Database @@

• Configure SSL Security.
• Add in Database security via Generated ENV userid & password variables when DB is spun up.
• Enable Database Replication & Configure Cluster Network.

Planned / Additional Features

• Convert each service into a microservice!
• File handling / API. Would like to implement the ability to upload the data from the Client side.
• Client Side Mutual Authentication to allow connectivity to encryption/storage service.
• API Interface to easily view storage metadata information and query attributes of specific files.

gocrypt's Issues

The Password Fatfinger.

Need to add password (secretkey) verification to avoid a risk of the dreaded "Fatfinger."