Update Activity-ICMPv6_RA_with_Scapy prompt.adoc

See merge request CCTC/public!185

Update_Activity-Scapy_for_ARP.adoc

See merge request CCTC/public!184

Resolve "Raw Sockets Activity"

Closes #16

See merge request CCTC/public!183

Resolve "Nix1-Net3 Telnet service configuration + start fails"

Closes #12 and #13

See merge request CCTC/public!182

Added new prompt for proposed activity regarding ARP over raw socket programming. Solution to be sent seperately as I only have access to public repo.

Resolve "Missing CONTRIBUTING.md"

Closes #14

See merge request CCTC/public!181

I had to change the nix1_net3 configuration so that it uses the
template in my branch rather than the template in the master branch.
This commit simply reverts the template back to the master script.

Once this branch is merged to master, it will then obviously point
to the fixed shell script.

apt-get upgrade has been moved from after the pkg_array installation loop
to before this because it just makes more sense.

Tinkering with the pkg_array install process. Fixed the main issue where
the presense of linux-headers-($uname -r) was breaking things. I'm pretty
sure whoever wrote it meant for it to be $(uname -r), but I'm just
removing it entirely for now because I'm pretty sure its not necessary
to update the kernel headers.

Once the basic installation of services and packages works, I'll mess
with the telnetd service and have it use systemctl instead of xinetd.

This is my initial draft of how I envision the schoolhouse should use GitLab and
version control in general. This document is tailored specifically to the CCTC
repository.

Some future improvements could be:
  - Code style standards
  - Code of conduct (aka "no asshole policy")
  - Merge request standards

This document should always be seen as a working document. It
should also be mandatory reading for any new instructors or
contributers to the repository.

This document serves as a working standard for how to use git
professionally in the CCTC repository. This document should serve as
a starting point for any future GitLab version control standards used
by the schoolhouse.

A lot of external resources are referenced in order to provide more
in-depth reading on various topics. These should be discussed for
their merit and whether, for example, a rebase-based approach is
better than a merge-based approach to handling changes and conflicts
during the standard git feature branch workflow process.

Cybbh reveal fixes resolved

See merge request CCTC/public!180

Update prompt.adoc

See merge request CCTC/public!177

stephen.e.griffing byod

See merge request CCTC/public!178

Update Movement_redirection_data_xfr.html

See merge request CCTC/public!175

Update CCTC_Master.yaml

See merge request CCTC/public!174