A simple tool for encrypting and syncing files to the Amazon cloud using S3.
Are you using services like Dropbox, Google Drive, Microsoft OneDrive, etc? Do you trust them not to look at your personal photos, read your documents, etc? If so, why? Don't you know that surveillance is big business, and that your data is the currency?
Nobody knows what the future brings: What kind of society will we be living in? What kind of government will we have to endure? Is it (still) going to be a free country? What kind of new criminal laws will be passed? ….. So what is your data going to tell about you, in the future, if everything is turned upside down? Are you suddenly a suspicious person that needs to be watched 24/7? Are you even fit to be left alone, drive a car, own a gun or raise children? Can you be trusted not to do something stupid when flying? …. Anything can be cherry picked out of context, twisted around, and used against you. Race, religion, political affiliation, you name it.
Remember, everything you upload is very likely to stay in the cloud forever. And if you think you're in control, it's only imaginary. Legal mumbo jumbo in a terms of service (ToS) agreement, or something like GDPR, does nothing to make your data unreadable. You should instead put your trust in technical implementations that make it impossible.
...
Read the rest of the pitch at Docs/WhyUseMyS3.pdf
If you're uploading downloaded content like wallpapers, music, software, etc. you don't need MyS3 or client-side encryption. You can just sync your folders directly to S3 buckets instead, using the AWS CLI.
For upload something like aws s3 sync [path-to-folder] [path-to-s3-bucket] works fine. For download you switch folder path with S3 bucket path and get aws s3 sync [path-to-folder] [path-to-S3-bucket]. Tip: Make a sync script that runs every hour or day.
MyS3 is a tool that makes is possible to encrypt file data on the fly and upload to Simple Storage Service (S3), which is part of Amazon Web Services (AWS).
Anyone can register an AWS account and create S3 buckets for file uploads. But enabling hassle free and secure file encryption is an entirely different matter. MyS3 does this for you after you setup your own AWS resources.
MyS3 is built using NET Core. It can be copied or imported into any kind of NET project.
See Docs/UserManual.pdf to get precise instructions with screenshots for complete AWS and MyS3 setup.
- Constantly monitoring for file changes.
- Uses symmetric encryption (AES-128 GCM) to encrypt file and it's file path.
- Supports use of multiple AWS S3 buckets at the same time.
- Can be run from multiple computers at the same time.
- Has two types of clients. A graphical interface client (Windows only) and a console client.
IMPORTANT: Yes, MyS3 can run on multiple computers at the same time and share the same S3 bucket. But MyS3 doesn't support merging of files with identical file paths. It creates new S3 object versions instead. So whoever saves his file last "wins". Avoid this by not writing to the same file path from different locations at the same time. Each person using a shared bucket should put his files in his own unique folder. (And if your file still gets overwritten just restore it.)
The GUI client:
- Download the ZIP file with the GUI client. (This is
MyS3.GUI.win-x64.zip) - Unzip it's contents and move the entire folder to
C:\Program Files. - Open the folder and double click the EXE file.
- Right click on the MyS3 icon down at the taskbar and select to pin it.
The console client (CLI client):
- Download the ZIP-file with the CLI client for your operating system. (For Windows this is
MyS3.CLI.win-x64.zip) - Unzip the content and move the entire folder to where you want it.
- Open a console window / a terminal and change directory to the MyS3's executable.
- Type and run
MyS3.CLI.exeon Windows or./MyS3.CLIon Linux. - Consider putting your command line arguments in a BAT or SH file when everything works OK.
Has a regular MIT license.
MyS3 started out as a pet project the summer of 2020 when I was getting to know AWS S3 better.
It was supposed to be a simple tool for encrypting and uploading files to S3. It was also supposed to be a lightweight Windows console executable. And I was only going to spend -2- weeks. But alas, I realized again and again that this very simple tool just needed a bit more functionality .. And before I knew it a month had gone by.
I was always hurrying and trying to finish it in the end. This is the reason the project documentation is poor and lacking. (Because I usually keep everything in my head when doing small projects.)
So a documented re-write is one day going to be necessary if more people start to use it.