[SLL] VNC issue
Paul Franz
paul at eucleides.com
Wed Mar 11 06:43:13 PDT 2009
On Wed, March 11, 2009 2:13 am, John Aldrich wrote:
> On Tuesday 10 March 2009, Paul Franz wrote:
> [snip]
>>
>> So, that works snazzy except I want the screen to fill the client's wide
>> screen and would be nice to have tab completion in terminal screens.
>> Sound even comes through, it's cool.
>>
> here's how I start it up... I SSH into my box, then run a script as
> follows:
> vncserver -depth 16bpp -geometry 1152x864
Do you know how to find what it is using without passing depth and geometry?
Don't you specify :n ?
I have been using numbers like 10,11,12 so when I access it for different instances
for say, different users like this:
http://server.tld:m where m=5800 + n
> Note you can pass color and geometry to the vncserver app on the command
> line. I came into this discussion late, so yo8u may already be doing this,
Hasn't been much response. People are probably too busy to respond as my questions
probably require too much typing to answer. In general, I spend a lot of time figuring
stuff out that amounts to "reinventing the wheel" when just asking might save a lot of
digging time.
> but unless you're running the Enterprise version of VNC, which has
> encryption built-in, you might want to consider tunneling your VNC session
> through SSH or something.
I've seen this mentioned but so far I have not figured out how to tunnel through SSH.
I might just try doing this:
https://server.tld:5810 since I do have Apache configured for SSL but I'm using only a
self signed certificate.
Any guidance? Also I haven't tried any stand alone vnc clients yet either.
> Much more secure, and you don't expose any
> passwords to sniffers, so no Man-in-the-Middle attacks possible. Remember,
> just 'cause you're paranoid doesn't mean they're NOT out to get you. :-)
I think I have vnc blocked on my firewall while I'm working out the details.
Thank you for your response. I certainly do appreciate your insight.
--
Paul Franz
425.440.9505 (O)
425.241.1618 (C)
More information about the linux-list
mailing list