Starting from:
$35

$29

Input Validation Solution

The goal of this assignment is to produce a program that validates its input using regular expressions.

This will be an individual assignment (no teams).

Detail:

Produce a command-line driven telephone listing program. The program shall be capable of receiving and storing a list of people with their full name and telephone. The program shall include the following commands:

    • ADD “<Person>” “<Telephone #>” - Add a new person to the database

    • DEL “<Person>” - Remove someone from the database by name

    • DEL “<Telephone #>” - Remove someone by telephone #

    • LIST - Produce a list of the members of the database

The above shall all be specifiable on the command line directly (e.g. <executable name> <mode> <arguments>) so that testing and verification of functionality can be scripted. When no arguments are specified, a usage (help) screen shall be displayed. The quotation marks around each of the arguments allows for spaces to be embedded in names and phone numbers (the shell should strip off the enclosing quotation marks before your program sees the arguments, but it should ensure that the entire name will be captured as a single argument, even with embedded spaces).

Create regular expressions for <Person> and <Telephone #>. Use these regular expressions to verify that the user is supplying valid data. More flexible specifications will be graded higher. For example:

    • Allowing for international or US format telephone numbers

    • Allowing for <first middle last>, <first last> or <last, first MI>)

Reject any attempts to provide invalid data. When valid input is provided, an exit code of 0 shall be returned; when invalid input is provided, an exit code of 1 shall be returned and an appropriate error message displayed to standard error (STDERR). An attempt to remove a non-existent name
from    the    directory    shall    return    an    exit    code    of    1.

You have the freedom to choose the implementation that you are comfortable with for persisting the phonebook to disk (e.g. XML, text file, binary file, CSV, database, etc.). If you are attempting the bonus at the bottom of the assignment, you might choose to use a SQL database initially to avoid rework later (our recommendation would be to use SQLite as it is portable and doesn’t require excessive setup steps).
To provide an opportunity to demonstrate other skills learned this semester, the following are additional requirements that must be met:

    • Make the program a Set-UID privileged program which runs under a separate user account (doesn’t have to be root) that is able to read/write the persisted data store for the names and phone numbers. File system access controls should restrict the ability of other users from directly reading/writing the file itself. They have to use your program to manipulate it.

    • Create an audit log to contain timestamped log entries written anytime a user adds a name, removes a name, or lists the names. These entries should include the real user ID that ran the program. For add/remove entries, include the name of the person that was added/removed in the log. This log should also be access controlled so that other users cannot directly read/write it (it’s accessible only to the privileged user under which the program runs).

You will need to do the assignment in a Linux environment.

If you do use a client/server database product, you should create a config file to contain database connectivity information and have your script read that rather than hardcoding those values in the application (also, the config file should not be readable by users running the program).

Permissible languages: C/C++, Any .Net Language, Java, Perl, Python, others with permission

Requirements for Phone Numbers:

The following are some rules to follow for phone numbers:

    • The country code may or may not be preceded by a + which indicates that an international dialing prefix, such as 00 or 011, must be included when dialing. If not using the plus, the dialing prefix itself may be included.

    • Some organizations use 5-digit extensions only for dialing from one internal phone to another.

    • North American phone numbers dialed within the countries of North America use a country code of 1, have a 3-digit area code, and a 7-digit subscriber number. Calls to local numbers in the same area code may omit the area code if not in a metro area; therefore, a subscriber only format may be used. Acceptable entry for North American phone numbers are as follows:

o  <Subscriber Number> (e.g. 123-4567)

o (<Area Code>)<Subscriber Number> (e.g. (670)123-4567) o <Area Code>-<Subscriber Number> (e.g. 670-123-4567)

o 1-<Area Code>-<Subscriber Number> (e.g. 1-670-123-4567) o 1(<Area Code>)<Subscriber Number> (e.g. 1(670)123-4567) o <Area Code> <Subscriber Number> (e.g. 670 123 4567)
o  <Area Code>.<Subscriber Number> (e.g. 670.123.4567)

o 1 <Area Code> <Subscriber Number> (e.g. 1 670 123 4567) o 1.<Area Code>.<Subscriber Number> (e.g. 1.670.123.4567)

    • Danish telephone numbers are 8 digits long, and normally written in four groups of two separated by spaces, AA AA AA AA. In recent years it has also become common to write them in two groups of four, AAAA AAAA. Also, allow dots instead of spaces. Denmark's country code is 45 and may be included as well for international formats.

    • Some notations use 2-digit area codes.

    • Some notations with 10 digits in two groups of five separated by either a space or a dot.

Sample Inputs:

Acceptable inputs for name:
    • Bruce Schneier

    • Schneier, Bruce

    • Schneier, Bruce Wayne

    • O’Malley, John F.

    • John O’Malley-Smith

    • Cher

Unacceptable inputs for name:
    • Ron O’’Henry

    • Ron O’Henry-Smith-Barnes

    • L33t Hacker

    • <Script>alert(“XSS”)</Script>

    • Brad Everett Samuel Smith

    • select * from users;

Acceptable inputs for phone: *remember these are also international numbers
    • 12345

    • (703)111-2121

    • 123-1234

    • +1(703)111-2121

    • +32 (21) 212-2324

    • 1(703)123-1234

    • 011 701 111 1234

    • 12345.12345

    • 011 1 703 111 1234

Unacceptable inputs for phone:
    • 123

    • 1/703/123/1234

    • Nr 102-123-1234

    • <script>alert(“XSS”)</script>

    • 7031111234

    • +1234 (201) 123-1234
    • (001) 123-1234

    • +01 (703) 123-1234

    • (703) 123-1234 ext 204

The TA will utilize a script to test your program using all of the above acceptable and unacceptable inputs for name and phone number, as well as additional ones not listed here.

Submission instructions:

You are required to provide the source code including instructions on how to compile, install, and run the software. Please indicate if your code has any dependencies (e.g. libraries, external programs, etc.) that must be installed prior to running your code. I would strongly prefer that you do not rely upon anything that is not freely available. If this is not possible, please let me or the TA know in advance so we can work out some way for us to evaluate and grade your assignment. In addition to the code and instructions, you must also turn in a report that describes your submission. This report should include a description of how your code works, the design of your regular expressions, any assumptions you have made, and the pros/cons of your approach.

Bonus (10 points):

Assuming a database backend wasn’t used, change to use a SQL database engine, such as SQLite, to persist the phonebook to disk. For reading and writing to the database, use an API that supports parameterized queries (also known as prepared statements) in SELECT and INSERT statements which will avoid SQL insertion vulnerabilities.

Grading Criteria:

    • The source code should be provided along with submission (0 point out of 100 if there is no code attached)

    • Report <<40 points>>:

        o Description of how your code works (10 points)

        o Compilation/build instructions (10 points)

        o Installation, setup, and execution instructions (10 points)

        o Assumptions you have made (5 points)

        o Pros/Cons of your approach (5 points)

    • Program is running successfully <<60 point>>:

        o ADD operation (15 points)

        o DEL operation (15 points)

        o LIST operation (15 points)

        o Privileged mode and audit log functionality (15 points)

    • Bonus <<10 points>>:

        o Using database to store the input data (5 points)

    o Using an API that supports parameterized queries (prepared statements) (5 points)

More products