-
Notifications
You must be signed in to change notification settings - Fork 114
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
enhancement: add docs for headless=false #60
Comments
thypon
added a commit
to doyensec/burp-rest-api
that referenced
this issue
Oct 30, 2018
Solves: vmware#37 Solves: vmware#60 Sponsored-by: doyensec <https://doyensec.com/>
thypon
added a commit
to doyensec/burp-rest-api
that referenced
this issue
Oct 30, 2018
Solves: vmware#37 Solves: vmware#60 Sponsored-by: doyensec <https://doyensec.com/>
thypon
added a commit
to doyensec/burp-rest-api
that referenced
this issue
Oct 31, 2018
Solves: vmware#37 Solves: vmware#60 Sponsored-by: doyensec <https://doyensec.com/>
thypon
added a commit
to doyensec/burp-rest-api
that referenced
this issue
Oct 31, 2018
Solves: vmware#37 Solves: vmware#60 Reviewed-by: Luca Carettoni <luca@doyensec.com> Sponsored-by: doyensec <https://doyensec.com/>
Included this issue/question in https://github.com/vmware/burp-rest-api/blob/master/FAQ.md |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi!
It took a little while, but I have X11 forwarding working from my osx laptop to an ec2 instance.
If desired, i can create a PR to the docs. Steps:
I followed http://www.brianlinkletter.com/how-to-run-gui-applications-xfce-on-an-amazon-aws-cloud-server-instance/
My ssh X11 forwarding looked like this
mac> ssh -X -L 5901:localhost:5901 -i ~/path_to_privatekey ubuntu@ip -vv
After installing vncserver as per biranlinkletter, the main differences were
mac> open vnc://localhost:5901
This opened an Xterm on my mac, but I got display errors.
I solved this by setting
AWS> export DISPLAY=localhost:1
Probably the most robust way to find out the Display port running vncserver is to check the
:600N entry below. N is the port, in my case, 1.
ubuntu@ip-172-31-17-158:~$ netstat -plan | grep LISTEN
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
tcp 0 0 0.0.0.0:6001 0.0.0.0:* LISTEN 2124/Xvnc4
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN -
tcp6 0 0 :::5901 :::* LISTEN 2124/Xvnc4
tcp6 0 0 127.0.0.1:8080 :::* LISTEN 3525/java
tcp6 0 0 :::22 :::* LISTEN -
The text was updated successfully, but these errors were encountered: