Do This Before Putting Your Files in the Cloud

Never change your video editing formula. This format is perfect, no music, no intro, no time-wasting bullsh, just fact and pure content. Good job.

Starting to think Mental Outlaw is the one looking at my history rather than Google. I searched this shit like yesterday.

As someone in cyber sec I like that he doesn't use buzzwords and try to wow us. He knows what he's talking about, he doesn't add anything on top. This is what it is

No intro, no outro, and shit is still sofa king good. Thanks, man. You're the 🐐 Edit: and no background music.

I haven’t trusted Google since I made a dummy account, uploaded a picture of an apple named “racecar” to Drive, and immediately saw ads for healthy foods.

I watched a speech about password cracking a while ago, where the guy (who I forgot the name, but who works professionally in pass-cracking) was saying an 8 digit password can be brute-forced in a few days with a cheap rig with 3 or 4 GPUs, and that a 9th digit exponentially raises that bar to a bunch of years, making it infeasible to brute-force. So, according to that guy, apps should be advising the use of 9 or even 10 minimum digits, not 8. And the takeaway from that video: DO NOT USE PATTERNS. "Obama08!" and "Shekelsteinberg69%" are effectively the exact same password from the perspective of a pattern matching algorithm.

even your vids are like linux, I can customize them by adding my own background music

rm -rf on a single file just for the lulz

Rclone with encryption layer is also a great tool for using 3rd party cloud drives seamlessly

Pretty useful. Especially for coomers. Liking the upload spree so far.

I love your channel, I've watched a couple of them and all of them are informative and useful thank you.

I prefer to use a cryptographic overlay file system like encfs, which is much easier to work with as it's completely automated. You designate a directory for the encrypted data, which will also be the directory that's synced to the Cloud, and the unencrypted mount point is another directory (or drive letter if using windows), where you work with your files as normal. That way you never have to manually encrypt and decrypt your data in order to work with it, and the only data that's ever synced to the Cloud is always encrypted.

Most precious thing I have in Google's servers is a rare version of Vivaldi Four Seasons. All the rest is my external drives. I don't trust "cloud service" because hackers, a war or government could compromise provider's servers and I'd lose my games, music, work projects... No way.

For offsite incremental backup, I recommend restic. It automatically do encryption and leverages rclone as backend to store backup almost any cloud storage providers

I'm sure Google won't bat an eye when I start uploading hundreds of gigabytes of encrypted data to their servers.

there is actually a way to keep integrity with AES by combining it with RSA. You can make a checksum of the encrypted file and then sign that checksum with your private RSA key. This way you can verify whether the data has been tampered with

I'm going to have to do this at some point, unfortunately, because airports are full of glowFRIENDS so it's the only safe way for me to transport my files when I fly to another country.

These tutorial formats make sense, and are to the point. Appreciate your time and explanation of this opsec mitigation method.

In a world where gov agencies keep legally forcing companies to let them access people's files, you can be sure there's one or more ways that someone could be nosing around your files. Maybe even backdoors.

Using symmetric encryption to access files on your employer's computer would be a really bad idea! Really, accessing any kind of secret on someone else's hardware is a bad idea. In the US (and most other places, AFAIK), employers have very few restrictions on what data they can collect about their employees. There are whole software suites dedicated to helping managers sift through data like key logging, screen recording, camera/mic recording, application usage stats, and whatever else you can imagine. It's all fair game to them. You should 100% assume that any password you type on a work computer is known by your employer.