Introduction

The CORA API provides Quantum safe encryption today and tomorrow.

CORA-X lite is a portable applicaton to protect your sensitive data. CORA stands for context ordered replacement algorithm. CORA Cyber Security Inc empowers data security and cloud security in a manner that supersedes encryption. CORA is quantum safe (safe from all computers including quantum computers) cryptography for your data security.

CORA-X lite allows individuals, teams, businesses, offices, and organizations to secure their data.
This application uses the CORA API which can be used to protect any application, cloud or enterprise solution.
The CORA API incorporates our MUPs (Multiple Use Pads) and CORA blocs to provide probabilistic encryption rather than factorization based which is one of the reasons why quantum computers will not break CORA.

Using CORA help

The Information is presented (except in small viewing devices, such as a smartphone) along the left side of the browser and the Topics are "Affixed" to the right side of the browser.

If your viewing width is less than 768px then the Affixed Topics are hidden and the Information is presented on its own.

Thanks to jQuery and Bootstrap, these help files should be continuously readable and usable on any device or browser.

The topic, or sub-topic you are viewing will be reflected in the color and marker shown in the Affixed Topic section.

You may jump quickly to any topic by clicking/pressing on it in this Affixed Topic pane.


When you link to a particular topic, through an internal hyperlink, or the Affixed topic pane, an entry in the history chain is created and available for you to quickly move back and forth using the arrows at the bottom of the page.

In this example, the Next icon is disabled, meaning that you are at the right end of the history chain; there aren't any other topics that have been linked to after this current topic.


Quantum Safe Cryptography

Quantum safe means that, no computer, including quantum computers, will break CORA's encryption.

This relys on you, the user, properly implement CORA-X with best practices; after all, the best 'safe' in the world only works 'if' you lock it, and don't leave the keys on top of the safe.

Safety, security and protection... what are these all about? Let's start with a brief analogy, think of your home. Security is like the locks on your doors and windows; it is important to secure your home. This prevents most unwanted visitors from violating your space, your home - they need your permission to enter.

Despite your best efforts, some thieves might break in without your permission. How might you protect your valuables? With a safe. Yes, this safe provides an additional level of protection, however, if the thief takes your safe home, then they have all the time in the world to crack it open.

In the digital world, this safe is better known as encryption. When standard forms of encryption lock a file, that file is essentially in a safe.
The problem here is that, if a thief takes the "safe" with the data from the server, they have all the time in the world to break it open.
Unlike a physical safe which is heavy and difficult to carry, when a computer is hacked, the digital files are light and easy to carry away.

This just isn't good enough, and that is where CORA comes in to play!

Context Order Replacement Algorithm

CORA is an acronym. CORA takes parts of the original file and breaks them up into different pieces (containers). More importantly, these fragments are chosen in a context based manner so that, if someone steels one of them, they don't have enough to put "anything together".
Imagine encrypting a file, then breaking it into two pieces... this isn't context based! Each piece can provide "too much information" about the original file.
With CORA, we don't want the thieves to know anything, not even a single word from the original file!

CORA is a probabilistic encryption that relies on unfathomably large probabilities rather than complex mathematical algorithms. This makes CORA safe even when Quantum computers become a reality that breaks all other current standards of encryption.

Probabilistic Encryption

  • MUP sizes begin at 1 million bits. 1 million bit encryption is 10300,413 times stronger than 2048 bit encryption.
  • CORA varies the size of each MUP (encryption key). Unlike 2048 bit encryption in which the size is known, the size of the MUP is not known. Could this be relevant to side channel attacks?
  • CORA does not use a single "safe"; CORA distributes the encrypted solution using CORA blocs.
  • The number of CORA blocs is unknown and varies from one encryption to another.
  • The size of CORA blocs varies. The last one or two CORA blocs may be limited in size to allow for a fast transfer to a remote cloud or data centre.

Why is CORA Unbreakable

Why CORA is unbreakable when properly implemented and used! Let us consider the main layers to CORA:

Notice above that the user must 'authenticate', then, the user must install the Encryption package which includes their MUP, which is different for every user, and at least 1 million bits long.

Why does this matter? Consider other forms of encryption, such as 1024 bit AES. This encryption always uses 1024 bits. It isn’t like yours might be 1025 bits and mine is 1031 bits. Here at CORAcsi, we don’t like giving away “any information” to a hacker or thief.

Lets talk about 1,000,000+ bit Encryption. How much stronger is a 1,000,000 bit encryption compared to a 2048? It is 10 300,413 times stronger; a number that we simply cannot relate to, however, consider that the age of our universe is approx 10 17 seconds old.

Note:

  • The number of CORA blocs may vary between 2 and 40.
  • The user has control over where the CORA blocs are stored.
  • The last 1 or 2 CORA blocs may be limited in size to 2-3 kB to allow for fast transfer to the Cloud, should a user prefer added security by storing 1 or more blocs in the Cloud.
  • The Primary System refers to the Encryption package which is mostly made up of CORAcsi's MUP (Multiple Use Pad).
  • It is highly recommended that users disperse their system and their CORA blocs onto different devices. See examples below.

CORA-X lite is designed to have a user initialized their system once when this application is first opened so that there isn’t a risk of a thief discovering which dispersed files are used to generate the system files.

Ideally this application will run until it is time to restart the computer. The user may lock and unlock CORA-X lite as often as needed, rather than closing then opening the application which would require loading the system each time.

CORA-X lite

CORA-X lite has been designed to be used on home computers and servers so that this application is loaded on startup, then runs until the computer needs to be restarted.

  1. CORA-X lite is a 64-bit application.
  2. The end user has a number of options to choose from. These will be described in greater detail below.
  3. CORA-X lite endeavors to monitor itself and the 'protected memory' used for possible intrustion and/or manipulation.
  4. The CORA API provides a number of security warnings:
    • Processes that attach to CORA will produce a popup message (unless you opt out of this) and entries in the 'Security Messages' dialog.
      Your operating system and anti-virus software involve many such DLLs that may attach to CORA without concern.
    • You may choose to accept select processes as 'trustworthy'.
    • Processes that change after you have accepted them as trustworthy will result in another security message.
    • Minor time violations. Should a process take too much time, a warning will be provided. This might occur on slower machines, or if another program (or hacker) is debugging your application.
    • A major time violation. This warning occurs when there is a significant concern for the time required to complete select tasks within the CORA API.
  5. It is crucial that you Backup your User data and your System data. If a single byte of your system data becomes corrupt or removed, then you will never decrypt (unCORAfy) your secured data!

The first time you start CORA-X lite on a given computer.

The First time you start CORA-X, you will see this dialog box:

You must read and accept the End User License Agreement (EULA).

After accepting the EULA, you may close this Dialog and continue to CORA-X lite.

You may use the View EULA link at any time to read the EULA again.

Quick Start

CORA-X may be used from your device (HDD or SDD), or you may use it from a portable flash drive.

  1. When first started, it will confirm that the computer is ready for CORA-X lite (has the necessary Operating System and DLLs).
  2. If this is your first use, then you will be shown the 'About Dialog Window' and asked to read, then agree to the End User License Agreement (EULA). If you do not agree to the EULA, then you are not authorized to use CORA-X lite.
  3. Enter a User Name
  4. As soon as you have your User name entered, the password selection dialog will appear asking you to enter your Password (& confirm it). You may also enter a password hint.
    Record you password, and backup your User data. Without your password, you will not unCORAfy (decrypt) your proteced data - ever!
  5. Sign in by entering your password in the 'Authentication area' of the Main Window, then select 'Unlock'. Note the minimum requirement for a password.
  6. Use the CORA-X Actions menu and select 'Setup' (Ctrl+S). Complete this form and your Primary System (Encryption package) will be created and installed.

You are now ready to use CORA-X lite. Use the 'File & Folder' Actions to add 'Actionable items' to the List box.

Once your Actionable items are in the List box, select the files you want to encrypt (CORAfy) then use the . Once the selected files have been CORAfied, this icon will change to . Select this icon again and you will unCORAfy (decrypt) the selected files.


Register with CORA-X.com

Registration provides two important identifiers:

  • A unique Id for the instance of CORA-X that is running on your computer.
  • A unique ID for the "Registered User" that is signed in to CORA-X.

Registration requies the ability to connect to the Internet.

Registration provides a number of benefits, including but not limited to:

  • Unique identifiers.
  • One or more unique system binaries.
  • The ability to check for Upgrades.
  • The opportunity to submit Reports and suggestions.
  • Coming soon: the ability to store CORA blocs and/or dispersed keys with CloudCORA.
  • Coming soon: the ability to initiate an Emergency Stop with CloudCORA.

Usernames

The same installation of CORA-X allows for one or more usernames. The same individual may create multiple usernames (profiles) to facilitate having different system files at different locations, and for different purposes.

For example:

  • An individual might create a ‘home’ based system (username), and a work based system.
  • An individual might desire to have one set of files secured using Google Drive and OneDrive for the dispersed system files (keys), and a separate set of work files secured using their hard drive and a flash drive.
  • A second individual might want to temporarily use your instance of CORA-X to access select files that are not often needed.
    It should be noted that this second individual would be advised to install their own instance of CORA-X in their work area (desktop), however, one of the underlying premises behind the building of CORA-X is to afford the end user their choice.

The Main Window

The Main CORA-X lite Interface is also known as the Main Window.

The Sections that make up this Application are listed below in order from top to bottom:

  1. Titlebar
  2. Menubar
  3. Authentication Control section
  4. Main Actions
  5. List box in which your selected Files and Folders are displayed and may be selected.
  6. Statusbar

The Layout of CORA-X lite.


Authentication

The First Textbox on the left is for your "User Name". Next to it is your password. The eye icon can toggle between viewing or hiding your passwords.

You may Unlock and Lock the access to CORA-X multiple times.

Ideally you will run CORA-X lite continuously, locking it when you are away from your desk and then unlocking it when you need to use it again.

For example, when 'the computer' starts up:

  • Start CORA-X lite
  • Sign in
  • Install the System (encryption keys, MUP, etc.)
  • CORAfy (encrypt) and unCORAfy (decrypt) your files as needed, or use the "Auto CORAfy" feature to automatically CORAfy select files when you Lock CORA-X lite, and unCORAfy them when you unlock CORA-X lite.
  • Lock CORA-X lite when you don't need it - keep the System available for when you do need to access or secure select files.

Main Actions

There are three groups of 'Main Actions': 1) Adding Files and Folders, 2) Installing the System, 3) Working with 'Actionable' Items.

The User must be signed in and have a System installed before adding or working on Actionable items.

Each System will maintain its own list of Actionable items. See "Profiles" and "Good for All: Users, Teams and Organizations" below.

Main Actions: Files & Folders

While there may well be millions of files on your computer, not all of them are sensitive and need to be protected.

For those who require encryption of the entire drive, stay tuned for upcoming releases, however, CORA-X lite is intended for "lite" use which protects select files on your device.

You may select files and/or folders to add to the "Actionable List box". These are the items that may be selected and then:

  • CORAfied (encrypt) the selected files (if not already CORAfied).
    *all of the selected files must unCORAfied, otherwise they will be unCORAfied first
  • unCORAfy (decrypt) the selected files (if currently CORAfied).
  • Open the selected file(s). If the selected file is CORAfied, then it will be unCORAfied then opened.
  • Remove the selected file(s) and/or folder(s) from the "Actionable" List box.

Note: Folders that are acted upon will not include 'subFolders'.

Main Actions: Installation

This is the where you install the MUP (1 Million + bit encryption key) and related system files using CORA's "Disperse Files".

What good are encryption keys if a capable hacker knows where to look, or if it is kept in one piece on the same device?

Our "Dispersed Files" protect your System by placing them in separate pieces and ideally in separate locations (devices and/or the cloud).

There are two types of Dispersed Files:

  1. Dispersed Data Files. There are two dispersed data files. You may choose to use a "Silent Load" with these so that you don't have to select them each time you start CORA-X.'
  2. Dispersed Static Files. There must be at least on static file, however, you may choose to use more than one for added security. Static file(s) must be selected using this Button every time a System is installed.

See "Setup" below to understand 'how' you create your unique encryption key (MUP) and system.

You must sign in before Installing a system.

When you select Dispersed Files, the number of files selected is shown in the Button. If you select an incorrect Dispersed File, you may use the "Clear" button to remove them and start over.

Once your System is successfully installed:

  • The Profile, Static and Install Buttons are disabled.
  • The Profiles Dialog is availabe and your System will be the topmost entry in this dialog window.
  • The Actionable items will be placed into the Listbox
  • Any "Auto CORAfy" items will be unCORAfied (decrypted).
  • You may uninstall this system using the "Clear" button.

Actionable Items

Actionable items are shown in the main area (Listbox) of this application. In order to "act" on an actionable item, it must be selected. The files highlight in blue below may be acted upon.

.

Keyboard shortcuts for working with Actionable items.

  • Ctrl + A: select all Actionable items.
  • Ctrl + Up(arrow): select the top Actionable item (only).
  • Ctrl + Down: select the last Actionable item (only).
  • Escape key: deselect all Actionable items.

Main Actions: Working with your 'Selected' files and/or folders

Select one or more files/folders in the Actionable List box.

CORAfy / unCORAfy

If all of the Actionable items selected are currently "readable" (not encrypted), then the "CORAfy" button will appear as , and when selected, will CORAfy the selected items.

If all of the Actionable items selected are currently "CORAfied" (encrypted), then the "CORAfy" button will appear as , and when selected, will unCORAfy (decrypt) the selected items.

If some of the Actionable items selected are currently "CORAfied" (encrypted), but not all of them, then the "CORAfy" button will appear as , and when selected, will unCORAfy (decrypt) those selected items that were CORAfied so that all selected items are the same.

Auto CORAfy

The "Auto CORAfy" button allows you to mark the selected 'Actionable items' to be automatically CORAfied when locking or closing CORA-X, and to be unCORAfied when unlocking with the System installed. Each System profile maintains a separate list of 'Actionable items' and 'Auto CORAfy' attributes.

If all of the Actionable items selected have previously selected "Auto CORAfy" then the button will appear as . If it is then selected all of the selected files will have this attribute removed.

If some of the Actionable items selected are currently "CORAfied" (encrypted), but not all of them, then the "CORAfy" button will appear as , and when selected, will unCORAfy (decrypt) those selected items that were CORAfied so that all selected items are the same.

Open

The Open Action will open the 'Actionable items' in their default programs. If the item is currently CORAfied (encrypted), then it will first be unCORAfied (decrypted).

Example: you 'Open' a Microsoft Word document that has been CORAfied, then CORA-X will decrypt this document and then open it in Microsoft Word.

If the 'Actionable item' is a folder, then it will be opened using your default 'File Explorer'.

The following icons are used for this 'Open' Action:
all of the Selected items are files
all of the Selected items are Folders
a mixture of files & Folders

Remove

The action will remove the selected 'Actionable items' from the List box.

An item that is being removed and is currently CORAfied will be unCORAfied (decrypted) before being removed.

Menus

The CORA-X Actions Menu

Setup

Keyboard Shortcut: Ctrl+S (hold the Ctrl key down while pressing the S key)

The Setup Dialog Window is used to create and modify System Profiles.

The first two 'files' (data1.jpg & data2.gif) are data files. The Silent load checkbox is used if you not want to find and enter these 2 files using the 'Profile' button during installation. While this is a faster way to Install a system, it is not as secure.

The next file is the static file '2011-08-03 16.50.38.jpg'. This static file must be found and entered with the 'Static' button when installing a Dispersed system. There is no 'silent' option for static files. If you use more than 1 static file, each of them must be found and identified when installing the Dispersed system files.

The final textbox allows you to select multiple directores to receive the CORA blocs.

Ideally these directories should be on different devices for optimal security.

In this demo there is a single Directory (Folder) "CBs". Since this is for demonstration purposes, the author chose to disregard the warning and opted to have all CORA blocs saved to this single directory.

Change Password

You may change your password. You will first need to confirm this action by entering your current password.

Once your current password is authenticated, you may enter and confirm your new password.

Note: once CloudCORA.com officially launches, there will be additional options and subscriptions to empower a highler level of security and redundancy. Until that time, you "must" safeguard and record you password; without a valid password it is impossible to load the System files and therefore decrypt your data.

This convenient action relies on the special Package named "Data Backup" and allows the user to backup the selected actionable items to a separate Package location.

This action, unlike the CORAfy action, does not encrypt the original data, but rather, provides a separate, dated, secure copy of the selecte file(s).

Ideally the Package locations for these "Backups" will be in separate Cloud based locations. For example, as a Trust Independant backup solution, place 1 CORA bloc on Microsoft's OneDrive, and another in Google Drive.'

The catalogs for these backups are kept in a special folder available for being restored with the next, "Restore Data" action.

The name of a Backup Catalog has the following format: FileName.day_month_year__hour_minute.ext(file type).cora
For example: FamilyPortrait.01_Jan_2022__09_05.jpg.cora - is a backup of "FamilyPortrait.jpg" secured on Jan 1, 2022 at 9:05.

This action relies on the special Package named "Data Backup". When a user selects this action, a Browse dialog is opened to the Special folder in which each 'dated' Data backup catalog has been saved.

Select one or more Dated backup catalogs and restore the data that was original, securely, backed up.

After Restoring select files, the "Restore" directory will be opened in 'File Explorer'.

Profiles

Keyboard Shortcut: Ctrl+P

This command opens the "Profiles Dialog Window". This will list your System profile first, and then any and all Imported Encryption packages.

This Window allows you to 'Auto load' imported files and to readily switch between Encryption packages. See the 'Profiles Dialog Window' below for more information.

Note: a single parent "System profile" may be in use at any given time. CORA-X does not allow you to Install more than one System profile. If you want to have access to additional System profiles, then you must export, and then import, such packages. This is by design.

Sign out

Keyboard Shortcut: Ctrl+G

It is recommended that you use the Lock and Unlock buttons in the Authentication Controls section.

Sign out does more than 'lock' CORA-X. It will remove all Encrytion packages, uninstall your System profile, and then completely remove all authentication parameters including your 'user data'.

This essential returns CORA-X to the same state that it was in when you first started this application.

The CORA-X Options Menu

Backup and Restore

Keyboard Shortcut: Ctrl+B

This menu action opens the 'Backup and Restore' Dialog Window.

Options

Keyboard Shortcut: Ctrl+O

This menu action opens the 'Options' Dialog Window.

This Dialog Window provides you with an alternative to selecting/deselecting the menu items included below:

For example, you may use the "Delete CORA blocs" menu item in this menu, or you may use the 'Options Dialog Window' to access this same property.

Export System

Keyboard Shortcut: Ctrl+E

You may export the Encryption keys (MUP+) once your System has been installed.

An Export is similar to a 'System Backup' except that with an export, only the MUP and related support files are included. The user preferences, Actional items list, and related authentication files are not included.

This empowers teams and organizations to share Encryption packages so that they may read and share secured data.

For example, the HR department would export their Encryption package, which is different than that used by the IT department.

Import System

Keyboard Shortcut: Ctrl+I

Import an Encryption package:

  • From another system profile that you have created.
    For example, Profile #1 may be your general profile used for banking. Profile #2 may be used for family pictures. Profile #3 may is for your investment.
  • For particular teams.
    If you are bringing your work home, then you may import the Encryption package for work.
    As an Entrepreneur, such as an IT professional who is working for multiple clients, such as doctors offices, each client should have their own Encryption package.
  • Within an Organization. Similar to teams, each department may have a separate Encryption package.

Security Messages

Keyboard Shortcut: Ctrl+M

This menu action opens the 'Security Messages' Dialog Window.

When selected and a CORAfied file is unCORAfied (decrypted), the CORA blocs used to encrypt this readable file will be removed.

If this is not selected, then the number of CORA blocs will increase with use. This holds an advantage if used "occasionally".

One of the advantages of CORA is that it becomes heuristically impossible to guess which CORA blocs go together in a particular solution. The greater the number of CORA blocs, the larger the number of permutations.
Remember that each combination of CORA blocs (2,3,4,12,21...) would require the "MUP" (Multiple Use Pad) to test; hence the 'impossible' rather than 'improbable'.

This opens another submenu in which you may 'limit' the size of the last 1 or 2 CORA blocs.

This is intended to be used when the 1 or 2 CORA blocs are being saved online (in the Cloud). For example, when CORAfying a large file, having 1 or 2 'small' CORA blocs saved to the Cloud increases security without having to wait for a long upload or download.

Normally 'Auto CORAfy' will encrypt the file when CORA-X closes, when the System is unloaded, or when CORA-X is Locked. This option allows you to keep your 'Auto CORAfy' items available when you Lock CORA-X.

With this option, you may comfortably lock your CORA-X and have access to the readable data. Then when you are done with using this readable data, you may manually CORAfy it, or wait until you exit CORA-X.

CORA-X allows you to switch between active profiles. For example, if your System profile is 'Team $3 - CORA gold' have 3 'imported profiles' loaded, 'Profile #1', 'Profile #2' and 'Profile #5', you may switch between these.
When you select 'Team $3 - CORA gold' as the active profile, then:

  1. If this option is selected, the other profiles that have 'Actionable items' marked as 'Auto CORAfy', will be encrypted.
  2. If this option is not selected, the other profiles with 'Auto CORAfy' will not be encrypted. Hence all profiles will remain 'readable' regardless of which profile is active.

When this property is selected, there will be a checkmark next to this menu item.

When this is selected, the 'User name' of the last authenticated user will appear in the User name text field when CORA-X is started.

The Help Menu

FAQ

This menu action opens your Default Browser and loads the 'Frequently Asked Questions'.

Report an issue

This menu action allows you to provide Feedback about CORA-X lite.

In order to use this you needed to register with a valid email address. See Reports

Password Hint

This menu action displays your password hint.

Factory Reset

This menu action resets CORA-X lite to the state it was in before your first use.

Warning: Everything will be gone, your Authentication, User data and System Profiles will be deleted! You should have a Backup of your User data and System data, always, especially before doing a Factor Restart.

"If you do a Factory Reset", then you shoudl insure that 'all' of your data is unCORAfied (decrypted) before proceeding!

About

Keyboard Shortcut: Alt+?

This menu action opens the 'About' Dialog Window.

Statusbar

The statusbar at the bottom of the Main Window should provide you with you important details:

  1. The date and time when CORA-X was 'last' started.
  2. How long this instance of CORA-X has been running.

Assuming your CPU's battery and clock are operational, this allows you to monitor the use of CORA-X within your account.

Dialog Windows

Dialog Windows are modal which means that they remain topmost until they are closed.

The About Dialog

The first time you open CORA-X you must agree to the End User License Agreement (EULA). When the About Dialog Window is opened subsequently, you will may read the EULA again by selecting the "Show EULA" link


The Change Password Dialog

The first step in changing your password is to enter your currently active password.

If your password is properly entered, and the system has not been corrupted, then you will be prompted for your new password.

The Minimum Requirement for a Password

The minimum requirements for a password are one of the following:

  1. 10 characters
    Examples (not good examples):
    • SaySomething
    • abcdefghij
    • 1234567890
    • Physics Rocks and physics rules
  2. Six characters with at least one upper case, one lower case, one number and one special character (!, ", #, $, %, &, ', ", "(, ), *, +, -, ., :, ;, <, =, >, ?, @, [, ], ^, _, {, |, }, ~)
    Examples (not necessarily good examples):
    • "Math2""
    • Love2>
    • Math=beauty2
    • DivBy0
    • What do you think? Is this "1 good example"?

Important - it is best to use a password that is 'more than' the minimum requirement!

Spaces are trimmed from the front and end of the password and do not contribute to the minimum requirement.

The Setup (system) Dialog

Next to Authentication (signing in), this is the most important process. Without loading your System profile, you cannot import other Encryption packages.

You may create multiple System Profiles, however, only one System profile may be active at any given time.


Dispersed Files are used to protect your MUP (Multiple Use Pad = encryption key) and supporting files. The bottom line for dispersed files is that they properly protect your encryption key (Encryption package):

  1. It is not safe to keep the encrytion key in a single file on the same device. Imagine have an expensive safe, then keeping the single key hanging in the office. Well they hide were the Encryption keys are kept you say. Really, with so many highly motivated and intelligent hackers, do you really believe it is 'impossible' to find or obtain? It has happened - this is the easiest way to break encryption.
  2. The CORA API doesn't just break apart this one file into 2 pieces (like a treasure map). CORA breaks it down at the binary level and disperses the bits throughout the two files, while using a 3rd static file to ensure that the only way to reconstruct the Encryption package is by having "all of the Dispersed Files, without corruption or exception, along with the authentication fingerprint of this user."
  3. You may opt to use more than 1 static file. While 1 static file is more than enough security, having the option to use more than 1 presents 'another unknown' to a hacker. Only you know how many dispersed files are involved, and which ones they are!
  4. For optimal security, you should store these Dispersed Files on separate devices. Perhaps put one on a flash drive, and another in the Cloud.
  5. CORA has been designed for Enterprise level usage and security. For example, a Server may start up and run for a month. The IT manager uses a Flash drive to load the Encryption package, and then once loaded, removes the Flash drive so that the Dispersed Files are not continuously available (cannot be search for should there be an unexpected Breach).
The Silent Load feature allows user to more quickly Install their System profile by selecting Static file(s) only. It should be noted that this is a convenience feature that is not as secure as having to select the data files each time.

Each System profile must have at least one directory chosen for the CORA blocs. That said, having more directories, especially when placing them on different devices, or clouds, provide greater security.

Recall that in the Options Menu (and Dialog) you may choose to limit the size of the last 1 or 2 CORA blocs to between 1 and 3 kB which is particularly useful if you are saving these to the Cloud. In order to take advantage of these being sent to the Cloud, you should enter a Cloud resource as a second and/or third CB directory.

The Options Dialog

This Dialog window is an alternative to using the checked menu items in the Options menu.

The Profiles Dialog

This is a very useful Dialog. It allows you to:

  • View the Profiles that are active in CORA-X.
  • Change the active Profile which in turn:
    1. Loads a different set of Actionable items into the List box.
      For example:
      • Your System profile has your personal files as Actionable, such as passwords, finances, investments, etc.
      • Your 'imported' family profile holds pictures, videos and correspondances in its Actionable list.
      • Your 'imported team 1' profile holds work related Actionable item (files) needed for work; perhaps as a lead programmer.
      • Your 'imported management' profile holds work related Actionable items related to your adminstrative responsibilities.
    2. This new Actionable list may have their own properties, such as 'Auto CORAfy'.
    3. Allows you to CORAfy or unCORAfy select Files/Folders.
    4. Each profile has its own Encrytion package.
    5. Each profile may specify a unique, or common, Package. Packages are specifications for alternate CORA bloc destinations (locations). Packages allow you to package a particular solution that may be shared between teams and organization.
  • Rename Profiles that make sense to you. For example, an Import of an Encryption package from work may be named "goCORA", however, you might prefer naming this "goCORA - User Interface".
  • Set an 'Imported Encryption package' to 'Automatically Load' when this System Profile is loaded. Yes, each system profile (created with the Setup Dialog) may have its own list of Encryption packages that are automatically loaded and with their own 'names'.
  • Unload an Imported Encryption package.

You may select a different profile using your mouse, and then use the "Ok" button to make that profile active, or you may double click on a particular profile name.

Notice that the Actionable list in the illustrations above and below have changed, depending on the Profile that is active.


The Packages Dialog

Packages provide alternative locations for the CORA blocs used when CORAfying (encrypting) or unCORAfying (decrypting) 'Actionable items'.

  • Without Packages the CORA blocs will be saved to (read from) the locations specified in the Setup Dialog or the Import option of the Backup/Restore dialog.
  • With Packages that are connected to a particular Profile, whenever that Profile is used, the CORA blocs will use the Locations specified in this particular Package.
    For example:
    1. You belong to a programming team at work. You have imported the System Encryption package allowing you to read and write encrypted data with your team.
    2. You import this profile (security key and system files) securely at work.
    3. You then create a "Trust Independant" Package in which 1 CORA bloc is stored on Microsoft's OneDrive, and a second CORA bloc is store in Google Drive, or on a portable flash drive.
    4. Bottom line: you now have secure access to these "team" files while on the road, and at home. It should be noted that this would only be necessary if you needed to restart your notebook when out of the office, otherwise these system files would be active in memory.

Packages - Data Backup

Data Backup is a special Package built in to CORA-X. It is used with the Backup Selected Data CORA-X menu action and the Restore Data CORA-X menu action.


Important: this is an example and should never be used like this - in which both locations are on the same device. Ideally, especially for Data backups, one should use 2 separate "Cloud" based destinations so that if, the computer or device failed, you might recover your 'securely' backed up data.

Reports


The 'Reports dialog' is an online ticket system that allows you to:

  1. Make a recommendation or suggestions to CORA-X.com.
  2. Report a usability issue.
  3. Report an unexpected behaviour.
  4. Report unresponsive behaviour.
  5. Report that CORA-X crashed.
  6. Any other unexpected and/or undesirable behaviour.

The Reporting engine requires that you have Registered with CORA-X.com.

Backup and Restore

The Backup and Restore dialog is not about "data", but rather, the Encryption Package (key) and User data that is needed to encrypt and decrypt your data.

You should Backup your User Data and System data immediately. Keep good records about which files are used in each type of Backup and the password used for each Backup.

Backup User data (manual)

User data includes the files needed for 'Authentication' and the preferences that you have selected.

It must be noted that having a "password alone" is not enough! If one or more of these files are deleted or becomes corrupt, then you will not decrypt your secured data! It is absolutely essential that you backup your 'User data'!

You may use a 1 or 2 Dispersed Files for 'User backups'. While 2 dispersed files is always more secure, even 1 dispersed file will still be CORAfied (encrypted).

You choose the locations (directories) for your dispersed files, and CORA creates the filenames based upon the date and time of the Backup.

Backup User data (automatic)

For Automatic, periodic backups of your 'User data', you will still select 1 or 2 locations for your backups, and must enter and confirm a password.

The Max # of backups limits how many 'automatic' backups are kept at any given time.

Backup System data

A System Backup will safeguard your Encryption package, Actionable list, Profile specifications and validation data. Contrast this to an Export which exports the Encryption package alone.

This Backup requires 2 locations for 2 distinct Dispersed files. You should specify 2 locations on separate devices; ideally one or both in the Cloud. For example, place on in Google Drive, and one in Microsoft's One Drive. Soon CloudCORA will offer advantages to those whose subscribe to our service, however, even then it is best to maintain a 'Trust Independant' policy in which you do not place all of your Dispersed files, (or CORA blocs) within a single Cloud or Corporation.

A password is required and must be confirmed. Hence to recap, in order to Restore a System backup, you must have access to both Dispersed files and to the password.

File Names

For Backups (and Exports) the Dispersed files will be given a filename that begins with the date and time of the backup, followed by a qualifier that identifies the type of backup:

  • .u is a manual backup of User data
  • .a is an automatic backup of User data
  • .s is a System backup.
  • Exports do not have a qualifier such as those listed above
  • _2 identifies the second Dispersed file in a Backup or Export.

For example:

05_Dec_2021__10_05_00.u.pcora is a manual User backup (single file)

15_Nov_2021__11_01_00.a.pcora is the first file in an automatic User backup

15_Nov_2021__11_01_00_2.a.pcora is the second file in an automatic User backup

01_Nov_2021__18_53_00.s.pcora is the first file in a System backup

01_Nov_2021__18_53_00_2.s.pcora is the second file in a System backup

27_Nov_2021__13_22_00.pcora is the first file in the Export of an Encryption package

27_Nov_2021__13_22_00_2.pcora is the second file in the Export of an Encryption package

Restore User data

  • Select the "Restore" Action and the "User data" item to Restore.
  • Select the Dispersed file(s). Enter their locations and name, or Browse for them.
  • Enter the password and confirm it by entering the same password in the 'Confirm' textbox.
  • Execute

Warning - this will overwrite all existing preferences and authentication data 'for this user'. Having this user's password is not enough to install a System Profile!

Restore System data

  • Select the "Restore" Action and the "System (keys)" item to Restore.
  • Select the Dispersed files. System backups always require 2 dispersed files.
  • Enter the password and confirm it by entering the same password in the 'Confirm' textbox.
  • Execute

Good for all: Individuals, Teams & Organizations

The ability to install multiple 'Encryption packages (MUPs)' is a powerful feature that can be used by all.

Export/Import versus Backup/Restore

An Export/Import involves the "Encryption package" alone. It does not handle the Profile characterstics, Profile data, validation files or Actionable list.

The Encryption package is made up of:

  1. The MUP (Multiple Use Pad) - an encrytion key that is at least 1 million bits in length; MUP varies in length and so the size.
  2. The MUP header - a supporting binary array that is 400 - 1000 Bytes in length (everything is probabilistic).
  3. The msa - another supporting binary array that is 500 - 1000 Bytes in length.
  4. An AES key

What is needed to use different Profiles

The reason for CORA-X is simple - the absolute security of your data. Hence to import a profile (Encryption package), all of the following are needed:

  1. You must be authenticated.
  2. You must have a System profile installed.
  3. You must have access to both of the Dispersed Files, and they must be created from an 'Export' operation (not a System backup).
  4. You must have the correct password.

How Individuals might user different Profiles

There are many different scenerios by which users will benefit from using multiple profiles.

Create a 'Primary System Profile' for use with your most import files, like passwords, investments, etc.

Create a 'Portable' Profile for use when you are on the road, or in school.

Create an "Images" Profile for use with select images.

Create a "Videos" Profile

Create a "Gaming Profile"

Import the Encryption packages from your Images and Videos Profiles into your Primary profile.

Import the Encryption packages from your Primary Profile and your Gaming Profil into your Portable Profile

How Teams might user different Profiles

At home or on the road, you would Install your 'Primary System' profile

If you often use multiple "Team" Encryption packages, perhaps one from work, another for you side-business, and a third for volunteer work you are doing, then you would have these "Automatically" set to import. Then switch profiles quickly and easily as needed. When you switch profiles, only the Actionable items for that particular profile (team) will be loaded and actionable.

How Organizations might user different Profiles

In a manner similar to how a Team might benefit from using different profiles, the same is true of an organization. That said, generally an organization might have a greater need for separating departments and teams, resulting in a greater number of Encryption packages.

Another benefit would be having greater control over access to these profiles. The Dispersed files need to be imported, and the passwords needed to import them may be controlled by the IT department according to best practices.

Security Messages

The Security Messages dialog will automatically appear when an alert is sent from the CORA API (unless you have selected "Temporarily hold Security Messages" in the CORA Options Menu). When this happens, only the 'new' messages will appear.

The "Security Messages" menu item will open the Security Messages dialog which will present security messages from the CORA API. These messages may be filtered:

  1. Attached Modules: original (previously accepted) and new (new to this current execution).
    • Original - refers to those modules that have been accepted prior to this current execution of CORA-X.
    • New - refers to those modules that have appeared during this current execution. If you 'Continue' and thus accept these modules, then they will appear in 'Original' the next time you execute (run) CORA-X.

      It should be noted that new modules that attach to CORA-X may not always be of concern, for example, your particular Anti-Virus software may attach to CORA-X. If you recognize this and trust your Anti-Virus software, then choosing to Continue will accept this module/process.
    • Changed Modules - if a module (process) that has been previously identified, changes, then this concern should be reported to you in these Security Messages.
    • Timed messages advise when processes take longer than expected. These may vary depending on your CPU and RAM and should only be used as a guideline unless the time reported is extreem. Extreem depends on the 'Type' of Timed security message:
      1. Type 1 indicate that the self-monitoring and validating routine has taken longer than expected.
      2. Type 2 indicate that an actions, such as CORAfy (encrypt) or unCORAfy (decrypt) has taken longer than expected. This threshold for this type of timed security message is higher than Type 1 messages. This might naturally trigger a message if you CPU is busy and/or you are processing a very large file.

      The following is an example of a "Timed alert"; we 'might' obtained this particular alert by attaching a debugger to CORA-X lite, however, there could be other reasons as well, such as busy CPU, older CPU or limited RAM.


CORAfy (encrypt)

When it comes to securing your data so tht it is protected against hackers and quantum computers, you will want to CORAfy such files:

  • An Actionable item is a file or folder that you have added to the Actionable items List box in the main window.
  • When one or more Actionable items have been selected, and are not currently CORAfied, then you may CORAfy them using the action button.
  • The Options that are currently selected in the CORA Actions menu, or the Options dialog box will be used to CORAfy the selected files:
    • Delete Original File. When CORAfying (encrypting) a file, do not leave a copy of the original file on the device. This should always be selected.
    • CORA bloc sizes. When storing 1 or more CORA blocs in the cloud, limiting the size of the last 1 or 2 may help to avoid bottlenecks depending on the type of connection you have to the internet.
  • A wait cursor will appear while the action(s) are being processed. When done the CORAfy icon will change to indicating that the selected file(s) are now encrypted.

Mixed Files - One or more are CORAfied, and one or more an 'not' CORAfied.

The CORAfy action button will use a dashed line to indicate that 1 or more of the Actionable files selected are CORAfied, and 1 or more of the Actionable files are not CORAfied. See Main Actions: Working with your 'Selected' files and/or folders.


What are your choices?

  1. If you select this 'mixed' CORAfy action button, then the CORAfied items will be unCORAfied. If you want them all to be CORAfied, then select this action button a second time.
  2. If you select the Open action button, then the CORAfied items will be unCORAfied and then all items will be opened.

There are a number of advanced options and combinations for "Auto CORAfy".

When 1 or more items have been seleced with "Auto CORAfy", then:

  1. These selected Actionable items will be automatically CORAfied when locking CORA-X, and automatically unCORAfied when unlocking this application.
  2. There is an inherent problem with this!
    • CORA-X is intended to be loaded once during 'startup', then left to run until the computer/server needs to be restarted.
    • You should not leave CORA-X unlocked. It just isn't secure!
    • Use "CORA-X Options menu" to select the menu item 'Autos' remain readable when Locked to keep these items available when locking CORA-X.
    • With this menu item selected, these "Auto CORAfy" actionable items will remain unCORAfied when CORA-X is locked.
  3. Users, particularly in teams and organizations, may well have multiple Profiles (keys) loaded. When switching profiles, different 'Actionable items' will be loaded, some of which may be marked with "Auto CORAfy".
    The "CORA-X Options menu" has a menu item 'Autos' Lock when Profile is inactive.
    • If this is seleced (checkmark) then when a Profile is inactive (another is selected to be active), the "Auto CORAfy" items will be CORAfied.
    • If this is not selected, then the "Auto CORAfy" items will be unCORAfied (readable) when a Profile is inactive.
    • In all cases, Locking CORA-X will either CORAfy all "Auto CORAfy" items unless the 'Autos' remain readable when Locked is selected (checkmark).

unCORAfy (decrypt)


The Options that are currently selected in the CORA Actions menu, or the Options dialog box will be used to unCORAfy the selected files:

  • Option: 'Delete CORA blocs'. If this option is selected, then when unCORAfying a file, the CORA blocs that were used will be deleted.

Warning - do not close CORA-X lite externally (force a shutdown) before it finishes processing previous actions. To avoid potential losses of information or corruption, you should only close CORA-X using the Exit Command or the Close icon in the Title bar.

Recommendations

  1. Choose a larger password. Record it - you must not forget or lose your password.
  2. Place your Dispersed Files on different devices, such as your computer, a flash drive and in the Cloud.
  3. Place your CORA blocs on different devices.
  4. Backup your User Data.
  5. Backup your System Data.