Updated today to provide secure VNC access to the squeaksource.com image. Details are in box3 ~ssdotcom/README.
The squeaksource.com image allows VNC connections on display number 1 with a password of "Squeak01". However, for security reasons, this access can only be enabled by one of the box-admins with sudo privileges on box3.squeak.org.
How to connect to the image with VNC:
- Log on to box3.squeak.org and determine the PID of the squeakvm that is running the squeaksource.com image. Running /usr/bin/top is a quick way to do this.
- Send a SIGUSR2 signal to the VM process. For example, if the pid is 12345, then the command would be "sudo kill -SIGUSR2 12345".
- Within the next 60 seconds, use a VNC client on your local computer to connect to squeaksource.com:1 and log in with password "Squeak01".
Dave
On Mon, 30 Dec 2013, David T. Lewis wrote:
Updated today to provide secure VNC access to the squeaksource.com image. Details are in box3 ~ssdotcom/README.
The squeaksource.com image allows VNC connections on display number 1 with a password of "Squeak01". However, for security reasons, this access can only be enabled by one of the box-admins with sudo privileges on box3.squeak.org.
How to connect to the image with VNC:
- Log on to box3.squeak.org and determine the PID of the squeakvm that
is running the squeaksource.com image. Running /usr/bin/top is a quick way to do this.
- Send a SIGUSR2 signal to the VM process. For example, if the pid is
12345, then the command would be "sudo kill -SIGUSR2 12345".
- Within the next 60 seconds, use a VNC client on your local computer
to connect to squeaksource.com:1 and log in with password "Squeak01".
Isn't it easier and safer to tunnel the connection over ssh?
Levente
Dave
On Tue, Dec 31, 2013 at 05:52:16AM +0100, Levente Uzonyi wrote:
On Mon, 30 Dec 2013, David T. Lewis wrote:
Updated today to provide secure VNC access to the squeaksource.com image. Details are in box3 ~ssdotcom/README.
The squeaksource.com image allows VNC connections on display number 1 with a password of "Squeak01". However, for security reasons, this access can only be enabled by one of the box-admins with sudo privileges on box3.squeak.org.
How to connect to the image with VNC:
- Log on to box3.squeak.org and determine the PID of the squeakvm that
is running the squeaksource.com image. Running /usr/bin/top is a quick way to do this.
- Send a SIGUSR2 signal to the VM process. For example, if the pid is
12345, then the command would be "sudo kill -SIGUSR2 12345".
- Within the next 60 seconds, use a VNC client on your local computer
to connect to squeaksource.com:1 and log in with password "Squeak01".
Isn't it easier and safer to tunnel the connection over ssh?
To be honest, I don't know how to do that (tunnel the connection over ssh).
My goal was just to be able to announce the ssh password (Squeak01) publicly so that it would be possible for someone other than me to connect to the image if necessary.
Dave
On 31.12.2013, at 07:23, David T. Lewis lewis@mail.msen.com wrote:
On Tue, Dec 31, 2013 at 05:52:16AM +0100, Levente Uzonyi wrote:
On Mon, 30 Dec 2013, David T. Lewis wrote:
Updated today to provide secure VNC access to the squeaksource.com image. Details are in box3 ~ssdotcom/README.
The squeaksource.com image allows VNC connections on display number 1 with a password of "Squeak01". However, for security reasons, this access can only be enabled by one of the box-admins with sudo privileges on box3.squeak.org.
How to connect to the image with VNC:
- Log on to box3.squeak.org and determine the PID of the squeakvm that
is running the squeaksource.com image. Running /usr/bin/top is a quick way to do this.
- Send a SIGUSR2 signal to the VM process. For example, if the pid is
12345, then the command would be "sudo kill -SIGUSR2 12345".
- Within the next 60 seconds, use a VNC client on your local computer
to connect to squeaksource.com:1 and log in with password "Squeak01".
Isn't it easier and safer to tunnel the connection over ssh?
To be honest, I don't know how to do that (tunnel the connection over ssh).
My goal was just to be able to announce the ssh password (Squeak01) publicly so that it would be possible for someone other than me to connect to the image if necessary.
ssh box3.squeak.org -lusername -L5901:localhost:5901
and then vnc to localhost:1
Best -Tobias
We really should have a page on the wiki that describes all the ways the Squeak can be run so the UI can be viewed and operated, and the pros / cons of each approach.
This something we all face today, not just box-admins.
On Tue, Dec 31, 2013 at 12:23 AM, David T. Lewis lewis@mail.msen.com wrote:
On Tue, Dec 31, 2013 at 05:52:16AM +0100, Levente Uzonyi wrote:
On Mon, 30 Dec 2013, David T. Lewis wrote:
Updated today to provide secure VNC access to the squeaksource.com image. Details are in box3 ~ssdotcom/README.
The squeaksource.com image allows VNC connections on display number 1 with a password of "Squeak01". However, for security reasons, this access can only be enabled by one of the box-admins with sudo privileges on box3.squeak.org.
How to connect to the image with VNC:
- Log on to box3.squeak.org and determine the PID of the squeakvm that
is running the squeaksource.com image. Running /usr/bin/top is a quick way to do this.
- Send a SIGUSR2 signal to the VM process. For example, if the pid is
12345, then the command would be "sudo kill -SIGUSR2 12345".
- Within the next 60 seconds, use a VNC client on your local computer
to connect to squeaksource.com:1 and log in with password "Squeak01".
Isn't it easier and safer to tunnel the connection over ssh?
To be honest, I don't know how to do that (tunnel the connection over ssh).
My goal was just to be able to announce the ssh password (Squeak01) publicly so that it would be possible for someone other than me to connect to the image if necessary.
Dave
box-admins@lists.squeakfoundation.org
-
Chris Muller -
David T. Lewis -
Levente Uzonyi -
Tobias Pape