Closed shezzski closed 6 years ago
Thank you :bowtie:
I would like to investigate further. Usually if a git connection on tcp/9418 does not succeed it should fall back to tcp/443. At least all git calls do not default to type .g8 which does not support fallback.
Hi,
Thanks for prompt reply! I performed some testing today and when TCP port 9418 is not allowed outbound from T-Pot the installation script terminates itself at:
" ## Installing wetty. "
When the script terminates you a left with a vanilla Ubuntu login prompt, so if a user starts the script and does not supervise it there is no indication of a script failure when the return to the machine.
I just would like to add that UDP port 123 outbound is also required for NTP during and after the installation.
Sorry cannot confirm, the installer runs npm install https://github.com/t3chn0m4g3/wetty -g
, which (at least according to tcpdump) defaults to tcp/443
.
Maybe something else hangs. Please try the command in debug mode npm install https://github.com/t3chn0m4g3/wetty -g -d
. You can increase the debug with -dd
or even -ddd
.
Update documentation for NTP.
Hi,
I downloaded the latest TPOT v16.10, followed your instructions for Standard TPOT install and ran VBOX with networking set to bridge however when trying to connect to web console I get no response.
Netstat via CLI show no open listening port on 64297 and when booting TPOT I see the following CLI logon. Would you be able to assist as I am very interested to test the tool?
Any help would be greatly appreciated.
Thanks.
Please use 16.10.1 ISO from here https://github.com/dtag-dev-sec/tpotce/releases/tag/16.10.1 leathal911 notifications@github.com schrieb am Di. 22. Aug. 2017 um 21:20:
Hi,
I downloaded the latest TPOT v16.10, followed your instructions for Standard TPOT install and ran VBOX with networking set to bridge however when trying to connect to web console I get no response.
Netstat via CLI show no open listening port on 64297 and when booting TPOT I see the following CLI logon. Would you be able to assist as I am very interested to test the tool?
[image: tpot_console] https://user-images.githubusercontent.com/31256160/29583245-c29ba796-877f-11e7-9e27-f36954c36f0d.jpg
Thanks.
— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub https://github.com/dtag-dev-sec/tpotce/issues/108#issuecomment-324125846, or mute the thread https://github.com/notifications/unsubscribe-auth/AEHk9KoETFNioMNGJ7kqvNRU2X3rXk5Tks5sayoWgaJpZM4NlEKE .
Thank you very much!
Much appreciated.
On Tue, Aug 22, 2017 at 9:43 PM, Marco Ochse notifications@github.com wrote:
Please use 16.10.1 ISO from here https://github.com/dtag-dev-sec/tpotce/releases/tag/16.10.1 leathal911 notifications@github.com schrieb am Di. 22. Aug. 2017 um 21:20:
Hi,
I downloaded the latest TPOT v16.10, followed your instructions for Standard TPOT install and ran VBOX with networking set to bridge however when trying to connect to web console I get no response.
Netstat via CLI show no open listening port on 64297 and when booting TPOT I see the following CLI logon. Would you be able to assist as I am very interested to test the tool?
[image: tpot_console] https://user-images.githubusercontent.com/31256160/29583245-c29ba796- 877f-11e7-9e27-f36954c36f0d.jpg
Thanks.
— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub https://github.com/dtag-dev-sec/tpotce/issues/108# issuecomment-324125846, or mute the thread https://github.com/notifications/unsubscribe-auth/ AEHk9KoETFNioMNGJ7kqvNRU2X3rXk5Tks5sayoWgaJpZM4NlEKE .
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/dtag-dev-sec/tpotce/issues/108#issuecomment-324131118, or mute the thread https://github.com/notifications/unsubscribe-auth/AdzuYNdD9lWPOBNLoQim-kRzTTnbfdXIks5say9JgaJpZM4NlEKE .
-- Regards, Chad
Also I have noticed that the self generated template here on GitHub has some spelling mistakes, which you can see below
So...... my "Documentation update" issue/suggestion is to do with the installation process. The documentation does advise that HTTP/HTTPS outgoing from T-Pot is required, but I did not see mention of TCP port 9418 that is required during installation for Git.
I feel that this would be nice to add somewhere in the documentation, which is quite great already, to save your time in the future with other "installation problems" with security paranoid users with locked down firewalls.
Good luck on the project and I look forward to testing it out with real traffic.
BR.