Lab46 Wiki

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
<WRAP centeralign round box>
<WRAP><color red><fs 200%>Corning Community College</fs></color></WRAP>
<WRAP><fs 150%>CSCS1320 C/C++ Programming</fs></WRAP>
</WRAP>

~~TOC~~

======Project: Data Obfuscation - SECRET AGENT MESSAGES (sam0)======

=====Objective=====
To explore the implementation of caesar cipher encoding and decoding programs.

=====Background=====
A cipher is defined as "a secret or disguised way of writing; a code", and (as a verb): to put (a message) into secret writing; encode.

In the realm of secrecy (think elementary school secret agent), obfuscation is key. If we can remove direct accessibility to the message (encode), yet still preserve its intent, it can be transmit to a recipient who has the ability to retrieve the message (decode).

The caesar cipher (or shift cipher) is a relatively simple cipher, where each letter of the alphabet is shifted by a fixed amount, enabling a once legible message to appear unrecognizeable (at least directly).

Further background information can be found here:

  * https://en.wikipedia.org/wiki/Caesar_cipher

There are two processes related to a lossless obfuscation of data:

  * encoding - taking the readable text and making it obfuscated, according to a set process
  * decoding - taking the obfuscated text and making it readable, by reversing the process
=====Program=====
You are to implement two programs (or at least a program with two fundamental modes of operation):
  * encode program: takes plain text message as input, along with a cipher key, and outputs the encoded (obfuscated) result
    * key should be provided via command-line argument (or, if present, a file in the current directory called 'cipher.key')
  * decode program: takes the encoded (obfuscated) message, along with a cipher key, and outputs the decoded (readable, plain text) result
    * key should be provided via command-line argument (or, if present, a file in the current directory called 'cipher.key')

The key should be a **signed char**, allowing for a cipher shift of -128 to +127 (your shift can be left or right, depending on the sign of the number).

You can implement this as two separate programs, or as one program that behaves fundamentally different depending on how it is named (ie **encode-sam0** operates in encode mode, **decode-sam0** operates in decode mode).

Your program(s) should:
  * load the provided input (via STDIN) into an array for processing (you may want to check for an EOF character to terminate input)
    * you may assume a maximum input size of 4096 bytes
    * use the **fgetc()** function instead of **fscanf()** for reading input from STDIN
  * obtain the signed char key value from the command-line, if present, or read from the 'cipher.key' file
    * if neither command-line nor key file are available, display error and exit
  * appropriately "shift" the alphabet according to the key (magnitude and direction and mode), storing the results in an array
  * for encoding, display the resultant enciphered string to STDOUT
  * for decoding, display the resultant deciphered string to STDOUT

====Sample execution: encode====
Via positive command-line key:

<cli>
lab46:~/src/cprog/sam0$ ./encode-sam0 2
hello
jgnnq
^D
lab46:~/src/cprog/sam0$ 
</cli>

Via negative command-line key:

<cli>
lab46:~/src/cprog/sam0$ ./encode-sam0 -3
hello there
ebiil qebob
^D
lab46:~/src/cprog/sam0$ 
</cli>

Without command-line nor cipher.key file:

<cli>
lab46:~/src/cprog/sam0$ ./encode-sam0
ERROR: key not found
lab46:~/src/cprog/sam0$ 
</cli>

With 4 in the cipher.key file:

<cli>
lab46:~/src/cprog/sam0$ ./encode-sam0
hello there
lipps xlivi
^D
lab46:~/src/cprog/sam0$ 
</cli>

With 4 in the cipher.key file, decoding previous message:

<cli>
lab46:~/src/cprog/sam0$ ./decode-sam0
lipps xlivi
hello there
^D
lab46:~/src/cprog/sam0$ 
</cli>

Via positive command-line key, decoding:

<cli>
lab46:~/src/cprog/sam0$ ./decode-sam0 2
jgnnq 
hello
^D
lab46:~/src/cprog/sam0$ 
</cli>

You can also save typing, by providing your input via a here string (also a nice way to check for EOF):

<cli>
lab46:~/src/cprog/sam0$ ./decode-sam0 2 <<< "jgnnq" 
hello
lab46:~/src/cprog/sam0$ 
</cli>
=====Submission=====
To successfully complete this project, the following criteria must be met:

  * Code must compile cleanly (no warnings or errors)
  * Output must be correct, and resemble the form given in the sample output above.
  * Code must be nicely and consistently indented (you may use the **indent** tool)
  * Code must utilize the algorithm presented above
  * Code must be commented
    * have a properly filled-out comment banner at the top
    * have at least 20% of your program consist of **<nowiki>//</nowiki>**-style descriptive comments
  * Track/version the source code in a repository
  * Submit a copy of your source code to me using the **submit** tool.

To submit this program to me using the **submit** tool, run the following command at your lab46 prompt:

<cli>
$ submit cprog sam0 sam0-encode.c sam0-decode.c
Submitting cprog project "sam0":
    -> sam0-encode.c(OK)
    -> sam0-decode.c(OK)

SUCCESSFULLY SUBMITTED
</cli>

You should get some sort of confirmation indicating successful submission if all went according to plan. If not, check for typos and or locational mismatches.
Lab46 Wiki

User Tools

Site Tools

Page Tools
