Encryption vs. Formatted File

In response to a post I wrote earlier this week, I Can Read ANY Format. I'm a Mac User., I figured a follow up post was necessary behind reasoning for calling what I submitted a file format and not an encrypted file. Even though I do use the word encrypt in my earlier post.

 

What is encryption? (from Webopedia)

The translation of data into a secret code. Encryption is the most effective way to achieve data security. To read an encrypted file, you must have access to a secret key or password that enables you to decrypt it. Unencrypted data is called plain text ; encrypted data is referred to as cipher text.

 

There are two main types of encryption: asymmetric encryption (also called public-key encryption) and symmetric encryption

 

What is a file format? (from Wikipedia)

A file format is a particular way to encode information for storage in a computer file.

 

Since a disk drive, or indeed any computer storage, can store only bits, the computer must have some way of converting information to 0s and 1s and vice-versa. There are different kinds of formats for different kinds of information. However, within any format type e.g. word processor documents, there will typically be several different - and sometimes competing - formats.

 

What is a file format specification? (from the state of MD)

A file format specification is instructions for creating and saving data that covers the following three components:

• The file type that must be used;
  A file format specification could require that all files be saved as a Word document, an Excel Spreadsheet, or as a Text file (as is required by this document).
• The order of the data; and
  The file format specification provides an exact order in which the data must be presented. For example, the format specification could require that the information for a contribution be ordered as follows: contributor last name, contributor first name, contributor middle initial, contribution amount, contributor address, etc.
• Specific instructions for each field of data.
  At a minimum each field of data has a specified type (i.e. text or number) and length (i.e. the number of character that can be used). In addition, some fields require the use of specified codes in place of an actual description. For example, name suffixes are each assigned a code (Jr. = 1, Sr. = 2 etc.) which must be used in the suffix data field.

 

The MCF file I have created while some people in cryptography may consider it encrypted, because I am trying to obscure data from another entity, I do not feel this is the case. Instead I have just created a new file format that has a closed specification.

 

I honestly thought about posting the spec in this post, but that defeats the purpose of discussing open document specifications in class on Tuesday. If Paul sends me an email I will gladly disclose the specification or send him the tool to do it, but until Tuesday the specification will be closed.

 

--Eric (Grand Valley State University)