Projects:2015s1-13 A One-Time Pad Generator - Revision history

A1608430 at 05:20, 17 November 2015

2015-11-17T05:20:49Z

A1608430 at 05:14, 17 November 2015

2015-11-17T05:14:54Z

A1608430 at 05:12, 17 November 2015

2015-11-17T05:12:32Z

A1608430 at 05:11, 17 November 2015

2015-11-17T05:11:56Z

A1608430 at 05:09, 17 November 2015

2015-11-17T05:09:21Z

A1608430 at 05:05, 17 November 2015

2015-11-17T05:05:15Z

A1608430 at 04:46, 17 November 2015

2015-11-17T04:46:28Z

A1608430 at 04:40, 17 November 2015

2015-11-17T04:40:13Z

A1608430 at 04:36, 17 November 2015

2015-11-17T04:36:34Z

A1608430 at 04:35, 17 November 2015

2015-11-17T04:35:03Z

@@ Line 1: / Line 1: @@
-== Introduction and Background ==
+== Introduction ==
 The One Time Pad generator project aimed to create a true random hardware generator in conjunction with a software interface to produce a device capable of generating "one time pad" keys and true random bit streams. The project consisted of several critical elements which included the design and implementation of both hardware and software subsystems into a fully functional true random hardware generator (TRNG) which could output the random data via a software interface and the subsequent testing of data using statistical test suites. The One Time Pad technique itself is a relatively simple and old crytographic method[1] used to encrypt plain text messages using a "pad" or key which comprised of truly random bits or numbers. This key along with the encrypted message would be sent to another person at different times to achieve secure communications.
-== Aims ==
+=== Aims ===
@@ Line 17: / Line 17: @@
-== Significance ==
+=== Significance ===

@@ Line 91: / Line 91: @@
 As a recap:
-- Applied a series of statistical tests to certify that the random number generator
+- Applied a series of statistical tests to certify that the random number generator satisfies the Federal Information Processing Standards for Secure Communications
-satisfies the Federal Information Processing Standards for Secure Communications
+(FIPS 140-2). The ENT test suite also revealed that the true random number generator performed better than the pseudo random generators as well.
-- Constructed a software interface for the generator to interact directly with an external
+- Constructed a software interface for the generator to interact directly with an external secure computer.
-- Extended the hardware number generator beyond One Time Pad through the use of
+- Extended the hardware number generator beyond One Time Pad through the use of software and hardware interfacing.
-- Designed the circuit such that it can fit into a form factor of a USB stick, by using an
+- Designed the circuit such that it can fit into a form factor of a USB stick, by using an I/O chip to handle communications between a host PC and the hardware generator.
@@ Line 111: / Line 107: @@
 == Conclusions ==
-The OTP generator was a very successful project in terms of laying the groundwork for future development from both software and hardware perspective. The prototypes developed in this project were able to meet all the specifications, outcomes and sufficient testing was done over the course of the project to warrant a reliable end product. The team worked together well to produce good harmony in the software and hardware interfacing and this will go a long way in assisting other projects which may need integration of hard and software modules.
+The OTP generator was a very successful project in terms of laying the groundwork for future development from both software and hardware perspective. The prototypes developed in this project were able to meet all the specifications, outcomes and sufficient testing was done over the course of the project to warrant a reliable end product. The team worked together well to produce good harmony in the software and hardware interfacing and this will go a long way in assisting other projects which may need integration of hardware and software modules. All the software is open source and the hardware is open ended, with room for plenty more design and variations.
 == Team Members ==

@@ Line 81: / Line 81: @@
 The GUI started from the main window and from there we routinely added new function once we had tested them seperately using another C compiler. QT is a C++ based program, or rather it uses a C++ compiler as the default for compiling codes, this meant we needed to slightly change some code from C we had written previously. Another thing to note was that we needed to import the LibMPSSE library into the build path, this was done by ensuring we appended the LibMPPSE to the QT.pro file (the configuration file that QT uses to coordinate everything - Makefile) and also by specifying the name of Lib being used.
-=== Statistical Suites ===
+=== Statistical Test Suites ===
 An important aspect for verification to evaluate the performance of the One Time Pad generator was the use of statistical test suites which tested the randomness of the bit streams. By using these we could see how well they performed when compared to other pseudo random generators which are generally used in place of true random generators due to their ease of access and relative randomness. The pseudo random number generators we chose to test alongside our true random generator was the C function srand() fed by time and PHP's rand() function which is seeded by any random value. The test suites used were the FIPS 140-2 Suite and the ENT Test Suite. Both offer a variety of different tests which compared many aspects of the randomness properties of the bit streams, such as arithmetic tests and correlation tests.

@@ Line 51: / Line 51: @@
 '''Research'''
 The USB to SPI interface limited our choices when it came to choosing an I/O chip to handle communications between the PC and the One Time pad Generator. Fortunately for us, it was a good thing as we do not handle an abundance of choices very well. We looked into the FTDI FT232H chip, a relatively new chip which supported the interface format we wanted and also seemed to have power and throughput properties that fell within our design calculations. To be sure we ordered the C232HM which is a FT232H development module in the form of a USB cable, the properties of it are on the FT232H wiki page.
 '''Design'''
 As we got the FT232H development cable module it was simply a case of connecting the C232HM's SPI interface directly to the ADC. In this configuration the ADC would be the slave while the master device is clearly the FT232H chip. Once we hooked it up we needed to find a way to see if the ADC was correctly reading the cable's data input. The first step however, was ensuring the cable was powered on and sending a steady SCLK and CS to make the ADC sample at the correct time.
 === Graphical User Interface ===

@@ Line 62: / Line 62: @@
 '''Research'''
-The first stage of the GUI was to investigate the best software package for the design and implementation stage of development. Having gained experience with QT in  one of my previous subjects we were already familiar with what it offered and we decided to look for other options in case I was missing out. We first looked at Microsoft Visual Studio and it seemed to offer a flexible and powerful package for GUI creation. The only things we were concerned about were the learning curve of using Visual Studio and the fact that it did not C++ GUI libraries meaning that the program would not be cross platform. Given these potential problems we decided to look for maybe another solution. The next one we looked at was GTK+, an apparent rival to QT, it offered a lot of the same QT did but we chose QT based on what we already knew about the program and that we knew we could immediately start developing the GUI on QT.
+The first stage of the GUI was to investigate the best software package for the design and implementation stage of development. Having gained experience with QT in  one of my previous subjects we were already familiar with what it offered and we decided to look for other options in case we were missing out. We first looked at Microsoft Visual Studio and it seemed to offer a flexible and powerful package for GUI creation. The only things we were concerned about were the learning curve of using Visual Studio and the fact that it did not C++ GUI libraries meaning that the program would not be cross platform. Given these potential problems we decided to look for maybe another solution. The next one we looked at was GTK+, an apparent rival to QT, it offered a lot of the same QT did but we chose QT based on what we already knew about the program and that we knew we could immediately start developing the GUI on QT.
 '''Equipment and Resources'''
@@ Line 106: / Line 106: @@
 There is plenty of future work to be had with the OTP generator because there are an incredible amount of applications that could use a cheap, portable and fast TRNG. The main areas of use would be driven by security and research themed ventures. In particular security is an entity which always needs to find better and more improved ways of keeping data and personal information safe. Many applications can be redesigned to use a hardware generator such as this OTP generator as their sole source of random numbers to ensure there is no correlation within the key data. Other software development ideas include the implementation of other encryption standards which can generate industry standard authentication such as PGP and AES encryption. More specifically to the generator is the possibility that it can become further optimized to deliver better throughput and also be developed to fulfill the other compliance levels for FIPS such as physical resistance to tampering and environment factors, making it a more self contained generator.
 == Team Members ==

@@ Line 60: / Line 60: @@
 The Graphical User Interface (GUI) is one of the major components which comprise the software system for the One Time Pad Generator. It's realization is to give user's a friendly and acessible interface when working with the One Time Pad Generator. This section will briefly cover the research, design and development of the GUI and try to discuss in details any problems that were encountered along the way.
-'''Research
+'''Research'''
 '''The first stage of the GUI was to investigate the best software package for the design and implementation stage of development. Having gained experience with QT in  one of my previous subjects we were already familiar with what it offered and we decided to look for other options in case I was missing out. We first looked at Microsoft Visual Studio and it seemed to offer a flexible and powerful package for GUI creation. The only things we were concerned about were the learning curve of using Visual Studio and the fact that it did not C++ GUI libraries meaning that the program would not be cross platform. Given these potential problems we decided to look for maybe another solution. The next one we looked at was GTK+, an apparent rival to QT, it offered a lot of the same QT did but we chose QT based on what we already knew about the program and that we knew we could immediately start developing the GUI on QT.
 '''Equipment and Resources'''
 For this particular part the software used was the QT Creator  5.0 Program. Fortunately QT now comes with the GNU LGPL licensing scheme meaning we can use it for free without having to pay royalties. The flip side is that the project is open source but as we are trying to make this project as open ended at possible it does not make it that different. Finally the last resource we needed was a decent computer so we could keep compiling the results of the GUI after each small revision.
@@ Line 74: / Line 76: @@
 '''Development'''
 The GUI started from the main window and from there we routinely added new function once we had tested them seperately using another C compiler. QT is a C++ based program, or rather it uses a C++ compiler as the default for compiling codes, this meant we needed to slightly change some code from C we had written previously. Another thing to note was that we needed to import the LibMPSSE library into the build path, this was done by ensuring we appended the LibMPPSE to the QT.pro file (the configuration file that QT uses to coordinate everything - Makefile) and also by specifying the name of Lib being used.
 === Statistical Suites ===
 == Results ==
-=== Hardware Testing ===
+All of the aims mentioned above were met and the fact that the design was able to be followed through with both respect to software and hardware subsystems was very fulfilling. Secondly for a non-tangible reason, the experience that comes from applying various technical skills on a single project is invaluable for understanding how projects develop over time. All the skills learnt as well are transferable skills that can be applied to different projects and activities which may be encountered in the future.
-=== Software Testing ===
 == Future Work ==
 == Team Members ==

← Older revision		Revision as of 04:40, 17 November 2015
Line 51:		Line 51:

	=== Graphical User Interface ===		=== Graphical User Interface ===
		+
		+	Introduction
		+
		+	The Graphical User Interface (GUI) is one of the major components which comprise the software system for the One Time Pad Generator. It's realization is to give user's a friendly and acessible interface when working with the One Time Pad Generator. This section will briefly cover the research, design and development of the GUI and try to discuss in details any problems that were encountered along the way.
		+
		+	Research
		+
		+	The first stage of the GUI was to investigate the best software package for the design and implementation stage of development. Having gained experience with QT in one of my previous subjects I was already familiar with what it offered and I decided to look for other options in case I was missing out. I first looked at Microsoft VIsual Studio and it seemed to offer a flexible and powerful package for GUI creation. The only things I were concerned about were the learning curve of using Visual Studio and the fact that it did not C++ GUI libraries meaning that the program would not be cross platform. Given these potential problems I decided to look for maybe another solution. The next one I looked at was GTK+, an apparent rival to QT, it offered a lot of the same QT did but I chose QT based on what I already knew about the program and that I knew I could immediately start developing the GUI on QT.
		+
		+	Equipment and Resources
		+
		+	For this particular milestone I had to first aquisition some software such as the QT Creator 5.0 Program and a few guides on the basics of QT as the last version I used was QT 3.0. Fortunately QT now comes with the GNU LGPL licensing scheme meaning I can use it for free without having to pay royalties. The flip side is that the project is open source but as we are trying to make this project as open ended at possible it does not make it that different. Finally the last resource I needed was a decent computer so I could keep compiling the results of the GUI after each small revision.
		+
		+	QT Creator 5.0
		+	C++ Libraries
		+	FTDI LibMPSSE library
		+	Windows 7 64 bit Operating System
		+	Design
		+	The GUI needed to be user friendly, so I aimed to try to keep the navigation of the program as simple as possible. Thus, I only made the GUI two windows deep, so that they could get to any function they wanted directly from the main window. I maintained a consistent naming convention and layout for each new window to ensure that people did not need remember where all the buttons for each window.
		+
		+	Development
		+
		+	The GUI started from the main window and from there I routinely added new function once I had tested them seperately using another C compiler. QT is a C++ based program, or rather it uses a C++ compiler as the default for compiling codes, this meant I needed to slightly change some code from C I had written previously. Another thing to note was that I needed to import the LibMPSSE library into the build path, this was done by ensuring I appended the LibMPPSE to the QT.pro file (the configuration file that QT uses to coordinate everything - Makefile) and also by specifying the name of Lib being used.
	=== Statistical Suites ===		=== Statistical Suites ===

@@ Line 1: / Line 1: @@
-== Background ==
+== Introduction and Background ==
@@ Line 64: / Line 64: @@
 Andrew Khuu
 Yanni Karvouniaris
@@ Line 69: / Line 70: @@
 Dr. Andrew Allison
 Prof. Derek Abbott
@@ Line 78: / Line 80: @@
 [1] Shannon, Claude (1949). ''Communication Theory of Secrecy Systems'', Bell System
 Technical Journal 28 (4): 656–715.
-[2] R.Sarpeshkar, T Delbruck and C.A. Mead (1993). ''White noise in MOS transistors and resistors'', IEEE Circuits Devices Mag. pp. 23-29, 1993

@@ Line 3: / Line 3: @@
-The One Time Pad generator project aimed to create a true random hardware generator in conjunction with a software interface to produce a device capable of generating OTP keys and true random bit streams. The project consisted of several critical elements which included the design and implementation of both hardware and software subsystems into a fully functional true random hardware generator (TRNG) which could output the random data via a software interface and the subsequent testing of data using statistical test suites.
+The One Time Pad generator project aimed to create a true random hardware generator in conjunction with a software interface to produce a device capable of generating "one time pad" keys and true random bit streams. The project consisted of several critical elements which included the design and implementation of both hardware and software subsystems into a fully functional true random hardware generator (TRNG) which could output the random data via a software interface and the subsequent testing of data using statistical test suites. The One Time Pad technique itself is a relatively simple and old crytographic method[1] used to encrypt plain text messages using a "pad" or key which comprised of truly random bits or numbers. This key along with the encrypted message would be sent to another person at different times to achieve secure communications.
 == Aims ==
@@ Line 28: / Line 28: @@
 === Noise Source ===
-The noise source needed to be a physically based phenomenon due to the fact that anything produced by software would be inherently deterministic and thus predictable causing correlations in the random bit streams. The phenomenon which was chosen to be the source of the noise is called avalanche noise and was produced in this generator by putting two bipolar junction transistors (BJTs) in reverse biased p-n junction at a low voltage. This would result in an effect called quantum mechanical tunneling which would produce an "avalanche" (truly random) noise source. As this technique uses low power it does not require large electrical components to power the generator and at least 15V is needed to produce a suitable amount of noise.
+The noise source needed to be a physically based phenomenon due to the fact that anything produced by software would be inherently deterministic and thus predictable causing correlations in the random bit streams. The phenomenon which was chosen to be the source of the noise is called avalanche noise, this type of noise was chosen as it was found to be the best source of white noise[2].  and was produced in this generator by putting two bipolar junction transistors (BJTs) in reverse biased p-n junction at a low voltage. This would result in an effect called quantum mechanical tunneling which would produce an "avalanche" (truly random) noise source. As this technique uses low power it does not require large electrical components to power the generator and at least 15V is needed to produce a suitable amount of noise.
 === Amplifier ===
@@ Line 43: / Line 43: @@
 The last component of the generator is the DC-DC converter which steps up the voltage of the input voltage into the noise source circuit. As mentioned before the noise source requires at least 15V of power and as the USB standard only allows up to a maximum of 5V then a DC-DC converter was required. There was a custom designed converter used using a DC-DC chip in conjunction with the appropriate power circuit but they kept failing. Ultimately a DC-DC module was implemented instead which allowed us to step up the voltage of 5B from the USB input to around 16-17V which was enough to power the noise source.
 == Software Components ==
 == Results ==
 == Future Work ==
 == Team Members ==
@@ Line 59: / Line 70: @@
 Dr. Andrew Allison
 Prof. Derek Abbott
 == References ==