Encryption in Oops! File Manager Professional

Oops! File Manager 1.3 is out and the biggest improvement is encryption. This article will explain how it works and how you can take advantage of it.

The New Feature

Previous versions of OFM hashes then copies the file you are monitoring whenever the original hash of that file changes. When OFM copies a file it copies it at the bit level and just makes an exact duplicate.

With encryption enabled, if a change occurred or if you’re initially backing up a file, then when OFM copies the file it is encrypted at the bit level then placed in the backup directory. To make sure that you can tell which files are encrypted we added “.aes” to the file name.

The encryption used is AES 256-bit with 128-bit and 256-bit keys for maximum protection. This new encryption feature in 1.3 is not on by default. You will have to set a Master Password under the “Tools” menu.

Once you set a master password, that password will be used to encrypt your files. The password itself is encrypted using the same level of encryption. Once you set a password you can undo the password and decrypt all files. You would have to “Restore” all the encrypted files to recover them. You can change your password too; however, files encrypted with an old password will be locked until you backup these files again. Running another backup uses the new password, thus enabling the file to be restored if needed.

So what isn’t encrypted?

The database and majority of the files in the installed directory is not encrypted. The database does contain information that is encrypted (i.e. master password). However most of the database isn’t encrypted.

Will more encryption be added and will it be available for free?

We plan to add more encryption to the database and force passwords for file restoring and other features in the future. Once these features are in the Professional Edition the Free Edition will receive encryption. Our overall goal is to protect backup files and make a portable USB version.

What else is in the works?

You may see other features like Google Drive and Dropbox integration, Live Monitoring, and advance notifications by email coming in the near future.

As always thanks for reading and using Oops! File Manager!!!

How to NOT accidentally overwrite your OFM Database

If you haven’t downloaded Oops! File Manager yet, I’ll say give it a try. This article is mostly about the OFM database. If you haven’t read any relatable articles on OFM then let me reiterate by saying that OFM uses a single file database to store everything that’s going on with the application. This makes the possibilities of this file to be corrupted or overwritten, a little high but still rare.

However, the most confirmed way of damaging the OFM DB is installing updates. When updating OFM you must only use the “Update_Only” install file to make sure that the installer doesn’t overwrite the DB by accident. If you are downloading it for the fist time then the regular install file will work fine. If by some freak of nature you use the typical “setup” install file, while trying to update your older version of OFM, then its a good chance that the OFM DB is gone.

To stop this from being a possibility, locate the DB file (OFMdb.sdf) in the installation folder, which should be in the “AppData\Roaming” folder (i.e. C:\users\yourUserName\AppData\Roaming\Oops File Manager\). After you found it, simply copy it to a safe place. If this ever becomes a reality you can easily restore it by moving it back to the install folder.

SNEAK PEEK: Good news is that version 1.2 of Oops! File Manager will have a built in database backup that will happen every 5 days. Right now it is locked in at every 5 days; however, we are exploring the options of the Professional Edition having the ability to change it.

As always, thanks for reading!

Connect Oops File Manager to Google Drive (Windows)

Did you know you can connect Oops! File Manager (OFM) with Google Drive? Well, you can and its pretty easy.

OFM uses a single file database along with file hashing to keep track of your hard work. If your have OFM professional then you will be able to link your OFM backup hashes to Google Drive and you also need to have Google Drive installed on your Windows device (laptop, PC or tablet). Before we begin there are some choices to make about this mod. Doing this will mean that OFM will constantly feed update and file changes to Google Drive, which means if your tracking lots of files you can easily take up lots of space on your Google Drive account. I would suggest doing this slight mod if you want some redundancy in the case your computer catches on fire or decides to quit life.

First, you must locate your Google Drive folder. This is usually located under your user name on your computer (i.e. c:\users\yourusername\Google Drive). Copy this address to Notepad or anything else (word, notes, etc) you will need this path later.

Second, make a folder in Google Drive called “Oops File Manager”, this is optional; however, it’s a good idea if you want to make sure your backups are separate from other files that are on your Google Drive.


Step 1 and 2

Third, open OFM and click on “Tools” in the menu, then click on “Properties”. Notice the first choice, “Default Backup Directory”, you will need to change this to the Google Driver Folder. Click “Browse”, it will ask you if you are sure you want to change the backup directory, click “Yes” and navigate to the Google Drive folder. Once there, select the Oops File Manager folder you created. Lastly, click “Save”. Now OFM should start moving your backups to the Google Drive folder.


Step 3

Now that OFM is backing up to your Google Drive its now best to copy (from time to time) the OFM database in the case of your computer blowing up. Find the file OFMdb.sdf in the OFM install directory (see pic below) which should be located in your AppData folder (i.e. c:\users\yourusername\AppData\Roaming\Oops File Manager\), simply copy this file to the Oops File Manager folder you create in your Google Drive.


Step 4

Hope this mod helps some people out!

As always, thanks for reading!