Noah Dowd Robert Salembier Paul Southerington Education Software for Cryptographic Laboratory Developing KRYPTOS into open-source project I. Language, Platform, and Compiler Microsoft Visual C++ will be used on the Windows platform to make the educational software KRYPTOS into an open source project. Support for the OpenSSL library will also be added to KRYPTOS on Windows using the same language. II. Additional Software Required Concurrent Versions System (CVS) will be required in order to coordinate updates, patches, and submittals. Free versions are available from http://www.wincvs.org/ and http://www.cvshome.org/. The OpenSSL library will also be required, and it is available from http://www.openssl.org/. III. Input/Output Specification The functionality will not be changed from the original KRYPTOS software, with the exception of a few suggestions made by early users. The software will take the same inputs as it does currently and provide the same outputs. IV. Functionality A web site will be developed including the following: - KRYPTOS – in the native Windows version (a) Fully GPL compliant (b) Fully compliant with a currently Open Source Certified license - A mechanism to submit updates and patches and documentation that accompanies such items. - KRYPTOS user manual - KRYPTOS source code for Windows V. Procedures A license will be selected that complies with the guidelines established by the Open Source Institute. Fully document and modify the software so that it complies with the selected license and is GPL compliant. Establish a Concurrent Versions System that can coordinate updates and patches. Attempt to submit an update and a patch into the system. Launch the website: www.kryptos.org. Monitor the website and take critiques from classmates and visitors to the site.Noah Dowd Robert Salembier Paul Southerington VI. Testing The process shall be as follows: a) Updates will be configured and submitted; the process will then be evaluated b) OpenSSL support will be tested independently. c) OpenSSL support will be submitted through the open source process; the process will then be evaluated VI. Schedule 26 September 2004 First Draft Specification 3 October 2004 Final Project Specification submitted 6 October 2004 Initial source code review complete Web site name finalized 8 October 2004 Specific license chosen 13 October 2004 First Progress Report First run through of code for GPL compliance complete. Documentation of areas of places to amend complete First run through of commenting of code complete Documentation of areas to enhance complete Initial review of OpenSSL code and documentation 20 October 2004 First draft of website complete First draft comment correction complete Initial plan for updating / patching complete Initial plan for adding OpenSSL support 27 October 2004 Second draft of website complete First attempt at GPL compliance complete Rough implementation of updating / patching plan complete Partial OpenSSL code added/tested 3 November 2004 Second Progress Report Second iteration of updating / patching plan complete Partial OpenSSL code added/tested Full GPL Compliance 10 November 2004 Remaining OpenSSL code added/tested Evaluation of OpenSSL requirements to support UNIX port Third Progress Report 17 November 2004 Updating / patching plan complete Web site format finalized Final testing of OpenSSL support Initial test of update / patch process complete Open source update of OpenSSL support for Kryptos 24 November 2004 Final Progress Report Second test of update / patch process complete 1 December 2004 Web site launched with complete CVS systemNoah Dowd Robert Salembier Paul Southerington Project Report Complete Project Report Due 8 December 2004 Oral Presentation / Final Project Report submitted 11 December 2004 15 December 2004Noah Dowd Robert Salembier Paul Southerington VII. Possible Changes in Specification Depending on the layout and separation of the code the team may be able to develop the code to a state that allows for more than just the OpenSSL and Crypto++ Library to be integrated into the software. Additionally, if all items are completed the porting of the software from Windows to a Unix/Linux based system would be an additional goal. IX. Literature a) Open Source Initiative, www.opensource.org copyright 2004 under Open Software license 2.1. b) Frank Hecker, “Setting up shop: The business of Open-Source Software,” published May 1998, revised June 2000. c) David A. Wheeler, “Why Open Source Software / Free Software (OSS/FS)? Look at the Numbers!,” revised September 2004. d) David A. Wheeler, “Make Your Open Source Software GPL-Compatible. Or Else.,” revised September 2004. e) Karl Fogler and Moshe Bar, Open Source Development with CVS, 3rd Edition. Scottsdale, AZ: Paraglyph Press Inc., 2003. Available under GNU General Public License: http://cvsbook.red-bean.com/ f) Concurrent Versions System, www.cvshome.org copyright 2003. CollabNet, Inc. g) Bugzilla, www.bugzilla.org copyright 2004 under Mozilla Corporation. h) Open Source Software Institute, www.oss-institute.org copyright 2004. Hattiesburg, MS. i) A. Abusher, KRYPTOS software, April 2004. j) A. Abusher, KRYPTOS Manual, April 2004 k) Free Software Foundation, www.fsf.org, copyright 2004 Free Software Foundation. Boston, MA. l) Crypto++ Library m) OpenSSL Project, www.openssl.org copyright 2002. n) Andrew St. Laurent, Understanding Open Source and Free Software Licensing, O’Reilly & Associates, 2004 o) phpBB, Open source bulletin board package, copyright 2003 by phpBB Group p) Bruce Schneier, Applied Cryptography, John Wiley & Sons, 1996. q) John Viega, Matt Messier, Privar Chadra, Network Security with OpenSSL: Cryptography for Secure Communications, O’Reilly & Associates, June 2002. r) Eric Rescorla, SSL and TLS: Designing and Building Secure Systems, Addison-Wesley Publishing Co. October 2000. s) SSLeay Documentation (predecessor to OpenSSL) www.columbia.edu/~ariel/ssleay/ t) OpenSSL examples u) W. Richard Stevens, Advanced Programming in the UNIX Environment, Addison-Wesley Publishing Co. May
View Full Document
Unlocking...