Re: new meterpreter vnc plugin

[Robin Wood <dninja () gmail com>]

2010/1/12  <egypt () metasploit com>:
> It should work just like before ('run vnc -i -t' is the same as the
> vnc_oneport behaviour).  Is there anything in the log?  4545 is
> actually the stager port, not the vnc port.  You can try to use a
> multi/handler manually with that as the LPORT, but if the
> automatically-started handler isn't running (or isn't working) then
> that may not help.  Is port 5900 open?  That's the default VNCPORT
> option which should be tunnelled through whichever connection started
> the session (the tunnel through meterpreter if you specified -t,
> reverse_tcp if you didn't).

I'll give it another try tomorrow but I know 5900 wasn't open locally
as I checked. I connected to 4545 with netcat and got a load of data
so there was a connection there. Should I have started a handler? The
way I was expecting it to work is the same as the old one, just run it
then connect locally.

I didn't specify -t, is it better to do it that way?

Robin


> egypt
>
> On Tue, Jan 12, 2010 at 8:35 AM, Robin Wood <dninja () gmail com> wrote:
> > Hi
> > I've been using the vnc_oneport and just done a svn up to find it was
> > replaced with a new vnc plugin. I tried that and it connected and gave
> > me a local port of 4545 to connect to. I tried connecting and got an
> > error from my vnc client saying it isn't a valid vnc server. Do I have
> > to do anything special to use this new plugin?
> >
> > Robin
> > _______________________________________________
> > https://mail.metasploit.com/mailman/listinfo/framework
_______________________________________________
https://mail.metasploit.com/mailman/listinfo/framework