This repository has been archived by the owner on Jan 27, 2025. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Documentation relating to resizing rectangles added - Documentation relating to fading images in and out added - Introduction to Wireshark added - Example file for Wireshark added
- Loading branch information
1 parent
d280912
commit 1763e0c
Showing
4 changed files
with
50 additions
and
1 deletion.
There are no files selected for viewing
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
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,30 @@ | ||
<?xml version = "1.0" encoding = "UTF-8" ?> | ||
<Computer id="wiresharkExample" name="Bitwise Test PC" type="4" icon="laptop" security="2" allowsDefaultBootModule="true"> | ||
|
||
<file path="bin" name="Wireshark.exe">#WIRESHARK_EXE#</file> | ||
|
||
<!-- Pre-Defined file - player can view this right away so long as they have admin permissions on the node --> | ||
<wiresharkCapture path="home" name="testcapture.pcap"> | ||
<pcap id="12" from="127.0.0.1" to="192.168.1.1" method="GET" protocol="TCP" secure="false">el horso</pcap> | ||
<pcap id="392" from="127.0.0.1" to="192.168.1.1" method="POST" protocol="TCP" secure="false">god damn you half-japanese girls | ||
do it to me every time | ||
oh the redhead said you shred the cello | ||
and i'm jell-o, baby</pcap> | ||
<pcap id="183" from="127.0.0.1" to="192.168.1.1" method="GET" protocol="TCP" secure="false">you just lost the game</pcap> | ||
<pcap id="420" from="127.0.0.1" to="192.168.1.1" method="GET" protocol="DNS" secure="false"></pcap> | ||
<pcap id="123" from="127.0.0.1" to="192.168.1.1" method="POST" protocol="SSL" secure="true">This is a secure file!</pcap> | ||
</wiresharkCapture> | ||
|
||
<!-- | ||
Secure packets are a bit funky. The player must have admin permissions on the computer that the file came from, and the file must be on the same computer. | ||
If the player does not have admin permissions or is on another computer then, the packet will state it is encrypted and cannot be viewed. | ||
It's a bit confusing, but it can add some new challenge. | ||
--> | ||
|
||
<!-- These are captured by passing the capture launch argument to the executable. --> | ||
<WiresharkEntries> | ||
<pcap id="1" from="127.0.0.1" to="1.1.1.1" method="PUT" protocol="TCP" secure="false">This node has been wiresharked!</pcap> | ||
<pcap id="45" from="127.0.0.1" to="2.2.2.2" method="POST" protocol="UDP" secure="true">This is a secure packet... hush!</pcap> | ||
</WiresharkEntries> | ||
|
||
</Computer> |
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.