Few findings in webtrack.pdf

[uthanda-raja]

1. The below document is empty. It's not showing any report template The lab report template is at: file:///root/Desktop/labtainer/trunk/labs/webtrack/docs/webtrack-report.docx -rw-r--r-- 1 1000 docker 4 Aug 1 2019 webtrack-report.docx

2. webtrack.pdf section 2.3 - welect Open a New Private Window. There is a typo. It should be select instead of welect.

3. Snapshot is not added to the PDF. Everywhere it's blank.

4. After closing the browser, how to re-open the browser again? Steps are not there in the pdf. I could not able to perform the lab exercise if I open the normal Firefox browser. The browser which is opening automatically is created specifically to perform this lab exercise?

[mfthomps]

Thank you for the reports. It looks like the manual's Latex build is broken. Should be easy to fix.

Per your item 4: type "firefox" in the lab window titled "ubuntu@browser". That will open the browser in that container. I don't recall specifically if that browser is configured differently for this exercise -- but in general we suggest running the browser from within the lab container rather than from the VM.

[uthanda-raja]

Thanks for your reply.

I've tried typing the firefox in the lab window titled "ubuntu@browser". But I got below error. It failed to open the firefox browser.

ubuntu@browser:~$ firefox [1]+ Done firefox > /dev/null 2>&1 No protocol specified Failed to connect to Mir: Failed to connect to server socket: No such file or directory Unable to init server: Could not connect: Connection refused Error: cannot open display: :0

As a workaround, I opened an extra window for "ubuntu@browser" using moreterm.py. So while opening the browser labtainer, it opened firefox too.

[mfthomps]

The Error: cannot open display: :0 error is odd. Typically you see that if the VM X11 socket gets corrupted. But the only way to fix that is usually a reboot of the VM. Since a second terminal (via moreterm.py) appears to have allowed the browser to open, I have to rule out that error. Which is to say I'm stumped. I'm curious if that is repeatable, i.e., try running the lab again and see if it happens.

Regarding the "empty template": yes, that can be confusing. Some of the labs include empty "report templates" that students are supposed to use when reporting on observations and such. It is just a convenient way to provide the student with a way to create a report, with a preset name.

Thanks again for the reports. There should be an update in the next day that fixes the typos and missing figures.

[uthanda-raja]

Thanks for your feedback, Mike.

I'm getting the same error always as below.

ubuntu@browser:~$ firefox No protocol specified Failed to connect to Mir: Failed to connect to server socket: No such file or directory Unable to init server: Could not connect: Connection refused Error: cannot open display: :0

[mfthomps]

Please run ls -l /tmp/.X11-unix/ on the VM. If you do not see a socket named "X0", reboot the VM. Sometimes the X11 socket on the VM gets corrupted.

[uthanda-raja]

I can see the socket named X0. Even after rebooting VM, I got the same error. root@kali:~/labtainer/labtainer-student# ls -l /tmp/.X11-unix/ total 0 srwxrwxrwx 1 Debian-gdm Debian-gdm 0 Feb 12 10:05 X0 srwxrwxrwx 1 root root 0 Feb 12 10:06 X1

[mfthomps]

A few questions to help me understand: Are you running from a Labtainer VM appliance, or did you install Labtainers on a VM of your own? When running the webtrack lab, you said that the failure occurs after exiting the browser and then trying to restart the browser? And you indicated that if you ran moreterm.py, the new terminal would open firefox successfully. Is that still true?

I see you are running as root? X permissions may differ between root and other users. What happens if you run as a normal user? And/or, does using "xhost +local" on the VM change things? For reference, my xhost output is:

xhost access control enabled, only authorized clients can connect LOCAL: SI:localuser:mike

Thanks, --Mike

[uthanda-raja]

Are you running from a Labtainer VM appliance, or did you install Labtainers on a VM of your own? - I've installed the Labtainer on kali linux by own. Not sure whether I answered your question correctly.

you said that the failure occurs after exiting the browser and then trying to restart the browser? - I've tried to open a new browser without exiting the old one as well as exiting the old browser, I got the same issue.

And you indicated that if you ran moreterm.py, the new terminal would open firefox successfully. Is that still true? - yes.

my xhost output:

root@kali:~/labtainer/labtainer-student# xhost access control enabled, only authorized clients can connect LOCAL: SI:localuser:root

Currently, I don't have a normal user to check. I will create a new one and check it.

Thanks Raja