Nelson Shaw Design Project
From CSSEMediaWiki
(Difference between revisions)
Nelson Shaw (Talk | contribs) (New page: Nelson Shaw's Design Project) |
Nelson Shaw (Talk | contribs) |
||
| Line 1: | Line 1: | ||
| − | + | = Trojan Project = | |
| + | |||
| + | As part of the COSC429 Information Warfare course, development of a Trojan module is required. | ||
| + | |||
| + | The software should have command and remote modules, which are connected together via sockets. | ||
| + | Functionality such as screen capture, key log capture and remote file browsing is required. | ||
| + | |||
| + | A more formal description is shown below. | ||
| + | |||
| + | = Design Study = | ||
| + | |||
| + | == Requirements == | ||
| + | # Secure - Components and communication of software should be secure and unable to modify | ||
| + | # Maintainability - Easy to add new functionality (e.g. Multiple remote modules) | ||
| + | # Extensible - Add additional software components easily (e.g. Software to deliver remote module onto target system) | ||
| + | |||
| + | == Constraints == | ||
| + | Remote and control module communication, processing speed and associated overhead costs. | ||
| + | |||
| + | == Initial Design == | ||
| + | First design will go here. | ||
| + | |||
| + | === Description of Classes === | ||
| + | Class Command... | ||
| + | Class Remote... | ||
| + | |||
| + | == Design Critique == | ||
| + | Criticism of design goes here. | ||
| + | |||
| + | == Design Improvements == | ||
| + | Possible improvements. | ||
| + | |||
| + | Thanks to [[User: James Ashford]] for the project page template. | ||
Revision as of 23:26, 21 July 2010
Contents |
Trojan Project
As part of the COSC429 Information Warfare course, development of a Trojan module is required.
The software should have command and remote modules, which are connected together via sockets. Functionality such as screen capture, key log capture and remote file browsing is required.
A more formal description is shown below.
Design Study
Requirements
- Secure - Components and communication of software should be secure and unable to modify
- Maintainability - Easy to add new functionality (e.g. Multiple remote modules)
- Extensible - Add additional software components easily (e.g. Software to deliver remote module onto target system)
Constraints
Remote and control module communication, processing speed and associated overhead costs.
Initial Design
First design will go here.
Description of Classes
Class Command... Class Remote...
Design Critique
Criticism of design goes here.
Design Improvements
Possible improvements.
Thanks to User: James Ashford for the project page template.
