I'm not sure if you guys could help because I am using tightvnc on linux
mandrake 10.1. Anyway the problem is that when I turned on the firewall and
opened the ports vnc server uses, namely 5900 and 5800, I couldn't connect.
Keep in mind I was able to connect before. So, then I turned off
Adding on Robert's suggestion,
This seems to be required for the shell to start stuff in the :0.0
display.
At least, when I changed XAUTHORITY to point at ~/.Xauthority, I
found I
could then run stuff in :1, but not in :0.
Presumably your setup is different, but normally Fedora 3 running
Scott,
Unless I've missed a mail somewhere, Michael isn't using EchoVNC. It's most
likely that his server is either configured to only accept connections from
the local host, configured for a different port than 5900 or was unable to
listen for connections for some reason.
Cheers,
Wez @
Em Terga, 19 de Abril de 2005 06:54, o QUINN MCKINSEY escreveu:
I'm not sure if you guys could help because I am using tightvnc on linux
mandrake 10.1. Anyway the problem is that when I turned on the firewall
and opened the ports vnc server uses, namely 5900 and 5800, I couldn't
connect.
I'd like to know if anyone has any working examples of why an
unencrypted VNC session over the Internet is seen as such a horrible
security risk. I understand that unencrypted ANYTHING over the Internet
lends the chance for someone to decode the packets (assuming that they
capture every one of
This is a very interesting question to me. In my own case, I do have SSH
setup thru Cygwin (http://www.cygwin.com/) for my local network and I
use VNC thru that connection when I need to manage my own stuff
remotely. However, I have to admit that when I use VNC to aid remote
clients (which
-Original Message-
From: Dave Love [mailto:[EMAIL PROTECTED]
Sent: Monday, April 18, 2005 1:41 PM
To: Robert Echlin
Cc: vnc-list@realvnc.com
Subject: Re: X authentication
Robert Echlin [EMAIL PROTECTED] writes:
every copy of bash that I run generates a different XAUTHORITY
Wez:
Sorry for the confusion. I just meant for him to *try*
EchoVNC, to see what its GUI responds with. The expriment is the
equivalent of telnet localhost 5900, of course.
-Scott
On Tue, 19 Apr 2005, James Weatherall wrote:
Scott,
Unless I've missed a mail somewhere, Michael isn't using
Mike,
compare pricing to an X server package like eXceed or
Reflection/X and I'm sure you'll find the price very nice, indeed.
Especially considering that tring to run a typical X package over a WAN
or other slow network is damn near impossible! The free version works
fine - for the
hmmm..
It needed not be as complex as hacking the vncserver perl script.
vncserver script creates the cookie file and passes it to the Xvnc
server it launches as the auth parameter
Also, you can use vncserver to override this behaviour by passing your
own xauth file.
So if you could say
#
Steve Bostedor wrote:
[snip]
I've scoured the web out of this curiosity, looking for a tool to
put VNC packets together into something useful for a hacker. There's
nothing. Nada.
Fifth hit on Google for: vnc capture playback
http://users.tpg.com.au/bdgcvb/chaosreader.html
--
William Hooper
It doesn't see RFB on telent 127.0.0.1 5900?
are the VncOptions Set to listen on port 5900?
It does sound like something is blocking vnc from listening on this port.
Did you try this with anti-vir disabled, windows firewall disabled, etc?
--Angelo
On 4/19/05, James Weatherall [EMAIL
The problem with what you are doing is that vnc (on windows) only has
one desktop. THat means that even though multiple ppl can connect at
once they will all be controlling a single mouse, keyboard and screen.
So if you just made it vnc it would work as a single user remote
system. In order to
Dear all,
I would like to install VNC on a headless windows2000 professional
workstation. All access I have is telnet (which I can start with the
computer manager remotely) and browser access, i.e. I can drag and
drop programs on the other computer.
If I see this correctly, I'd need instructions
Uwe,
In order to have started the telnet daemon, you will also have Administrator
rights and access to the machine's file system using Windows File Sharing
and to its registry, so you can use those to install the VNC files to the
machine.
Alternatively, if you have VNC Enterprise Edition then
Hi Wez,
thank you for the quick response.
In order to have started the telnet daemon, you will also
have Administrator
rights and access to the machine's file system using
Windows File Sharing
and to its registry, so you can use those to install the
VNC files to the
machine.
Maybe I
[In a message on Tue, 19 Apr 2005 10:53:09 EDT,
William Hooper wrote:]
Steve Bostedor wrote:
[snip]
I've scoured the web out of this curiosity, looking for a tool to
put VNC packets together into something useful for a hacker. There's
nothing. Nada.
Fifth hit on Google for: vnc capture
Thank you for the reply, Alexander. I understand exactly what you're trying to
say. I'm not sure if you fully understand what I was saying and its probably
my fault for not making it clear enough.
You seemed to concentrate on how easy it is to do things with the VNC packets
once you've
Joshua, Please see my reply to Alexander. It addresses some of what you said
here. I disagree that VNC should be avoided completely, though. It's not THAT
insecure! I will go out on a limb and say that about 90% of the pop3 users in
the world use plain text passwords. Encrypted passwords
Your plan is pretty typical and is pretty much what I advise to my clients.
Keep it off when it's not being used and change the password often. On secured
local LANS, it's ok to leave it running 24/7 as long as the remote server has
the desktop locked or logged off. This is the REalVNC,
I am wondering why expose VNC over the internet in the first place, really.
It's my opinion that VNC is really only good for LAN's. Why not use VPN to
secure your connection to the remote network before starting VNC sessions?
It's much easier to set up on a LAN where you need VNC access to
21 matches
Mail list logo
