64 bytes from 10.10.10.184: icmp_seq=275 ttl=127 time=1824 ms
64 bytes from 10.10.10.184: icmp_seq=276 ttl=127 time=883 ms
64 bytes from 10.10.10.184: icmp_seq=277 ttl=127 time=867 ms
64 bytes from 10.10.10.184: icmp_seq=278 ttl=127 time=1050 ms
64 bytes from 10.10.10.184: icmp_seq=279 ttl=127 time=230 ms
64 bytes from 10.10.10.184: icmp_seq=280 ttl=127 time=1720 ms
64 bytes from 10.10.10.184: icmp_seq=281 ttl=127 time=1898 ms
64 bytes from 10.10.10.184: icmp_seq=282 ttl=127 time=2074 ms
64 bytes from 10.10.10.184: icmp_seq=283 ttl=127 time=1074 ms
PLEASE DO NOT MAKE ANY DENIAL OF SERVICE
I am getting error 403 to login on console.
I know the config file allows one specific host.
How can I bypass this configuration to log in?
Thx!
Type your comment> @fcmunhoz said:
I am getting error 403 to login on console.
I know the config file allows one specific host.
How can I bypass this configuration to log in?
Thx!
Youâve gotta use what is available to you.
Check the ports and think about what those ports can offer.
If you know the allowed host⌠this shouldnât take long to figure out.
Type your comment> @PrivacyMonk3y said:
Type your comment> @fcmunhoz said:
I am getting error 403 to login on console.
I know the config file allows one specific host.
How can I bypass this configuration to log in?
Thx!
Youâve gotta use what is available to you.
Check the ports and think about what those ports can offer.
If you know the allowed host⌠this shouldnât take long to figure out.
I tried a port tunnel and I didnât even
Stop messing some s***** and setup on rootâŚ
The major reason why encountering 403 is the laziness of reading.
I read it but still canât login so @foxlox was sad.
Why the exploit cant work after login? Because I was a lazy reader again.
@Gearcapitan
lol wtf is that link, nope! 
Type your comment> @PrivacyMonk3y said:
@Gearcapitan
lol wtf is that link, nope!
a screenshot
Seem to be stuck. I see that a sensitive file was left laying around but a certain traveling trick doesnât seem to be able to grab the file securely or insecurely. Any suggestions?
Type your comment> @aut0exec said:
Seem to be stuck. I see that a sensitive file was left laying around but a certain traveling trick doesnât seem to be able to grab the file securely or insecurely. Any suggestions?
You might not be doing something right with this.
Check your syntex and make sure youâre not missing something.
Type your comment> @fleitner said:
Type your comment> @StanleyJobson said:
Type your comment> @fleitner said:
hmmm, whenever I try to tunnel to some web page to be of an allowed host, I get a PR_END_OF_FILE_ERROR in my browser.
Can anyone give me a hint on whether Iâm on the right track to root, and if I do something stupidly wrong with my tunneling?
I get this error too, even though Iâm using the same method as before when I had it working. Sometimes it works, sometimes it doesnât - I really canât give you an explanation unfortunately. I think this may be a weird Windows SSH thing?
I still donât know that the error message actually means, but try doing some different way of tunneling. I can now get to the page with a more local address - after telling my firefox to allow it.
The new issue is that somebody hammers and reverts this box like there is a reward out for it.
I narrowed this down. You receive this error when someone has hung the web service by hitting âReloadâ - so you will have to reset the box. No two ways about it.
I used EU VPN. the box keeps going down and very unstable. 
Type your comment> @PrivacyMonk3y said:
Type your comment> @aut0exec said:
Seem to be stuck. I see that a sensitive file was left laying around but a certain traveling trick doesnât seem to be able to grab the file securely or insecurely. Any suggestions?
You might not be doing something right with this.
Check your syntex and make sure youâre not missing something.
Checked and tried a few other things but even MS*T is failing⌠Any suggested sites to read up on this technique?
Got Root, after fighting the machine, but truth be told. it was FireFox, not really the machine.
Once I swapped over to Chromium, everything became better.
User: Easy, read whatâs available, then find what you need using pre-existing methods.
Root: Youâll probably need tunnel vision and Chromium, skip FireFox!!!
Got user: Searching Exploitdb + reading C********.txt will give you what you want. Then you can save your time by using hydra
Thanks for the box, even though the lag and people modifying scripts took away most of the fun 
Please add your own script, donât mess with othersâ stuff 
Guess iâll add some hints
User: CVE will help in looking at what others left.
Root: Use what you already have to give yourself access to another service. You donât need to wait, use the Console to call your script.
huft, finally rooted. for others who still trying to get to root, please stop restarting the box or the service for the sake of others. you donât need that.
any nudge for getting user creds⌠I m using nv**** exploit