Permalink
Cannot retrieve contributors at this time
Name already in use
A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?
ECM16/README.md
Go to fileThis commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
47 lines (35 sloc)
2.22 KB
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# ECM-16 - Code of Conduct | |
ECM-16 is available for students who study on the BSc./MSci. Ethical Hacking and Cyber Security course | |
to work on university or personal projects. | |
The room contains specialised machines, that run the Kali Linux operating system. Some of the tools and | |
software available on these machines can be dangerous, and it is expected that students will use these | |
tools in an ethical manner. | |
There are a few rules to follow when using this room: | |
1. Show respect for persons and property within the University's community. | |
2. Behave in a way that does not interfere with proper function or activities of the University and to | |
the lab. | |
3. Monitors, keyboards, and mice are **not** to be removed from this room. | |
4. **DO NOT** remove networking cables or power cables from the PCs. | |
5. **DO NOT** move the tables or equipment unless authorised to do so. | |
6. Though this room will not primarily be used for teaching, there may be times when it will be used for | |
teaching or assessment. Therefore, if this is the case, please leave the room and in a timely manner. | |
Any problems with the equipment in the room, raise an issue on this GitHub repository. Provide the computer | |
name, found on the front of the PC. | |
## Raising an Issue with the Lab | |
To raise an issue with the lab, you must use the issue tracker. This can be found under the **Issues** tab | |
on this GitHub repository. When raising an issue, use the following template: | |
```text | |
PC: CUEH-XX | |
Issue: Provide a short description about the problem encountered. | |
Resolution: Provide a short description on how this problem can be solved. If you do not know, then just enter | |
N/A. | |
``` | |
## Require Additional Software? | |
If you require some software to be installed on the machines in the lab, you must use the issue tracker. This | |
can be found under the **Issues** tab on this GitHub repository. When raising an issue, use the following | |
template: | |
```text | |
Software Name: Provide the name of the software. | |
Justification: Provide a short justification as to why you require the software to be installed. | |
``` | |
**Note**: The course team reserve the right to decline any request to install software on the machines. |