Closed basoreeper3007 closed 4 months ago
@michaeljpigott
I went through your requests and made all necessary changes. Let me know if anything else is required.
Thanks!
Hi @basoreeper3007 can you please resolve the conflicts before I start the review.
@michaeljpigott Conflicts are resolved.
Hi @michaeljpigott,
I’ve committed the changes you requested. As for that error you have found, I have no clue why it happened. The inputs look fine, and from my experience with Netcat, the configured shell scope error generally occurs when it isn’t included in the tuari config file. When I get home ill jump on and test it out and see if i can reproduce the error.
Thanks!
Hi @basoreeper3007, no worries. Let me know how you go with reproducing the error.
Hey @michaeljpigott, I can't seem to get the error to occur, mine works fine. Could you maybe try using the sniffer again, and then read the file. If the error occurs again can you send me a screenshot of both your sniffer inputs and reader inputs?
It is all good @basoreeper3007, your screenshot is evidence that it is working.
Tool Description:
The TShark tool is a CLI version of Wireshark and is used to capture and analyze traffic from the terminal, or in this case, from the DDT.
Tool Features:
In its current state, the TShark tool within DDT has the following features:
Sniffer -Sniffs and Captures traffic flow on a given interface and writes it to an output file.
Reader -Reads the contents of the capture file by displaying its contents in the output box.
Future Developments:
This tool is a basic tool used for traffic capture and analysis. So far, I have implemented the features for capturing traffic and displaying the captured traffic. In the future, other students could research how to analyze traffic in the capture file using TShark and implement an "Analyze" feature.