[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANO7a6ztC7ryW2aLje3XbDOwejH88uWSPoV=iJrh90SKiMg-LA@mail.gmail.com>
Date: Mon, 19 Mar 2012 20:17:31 +0530
From: Dhiru Kholia <dhiru.kholia@...il.com>
To: john-dev@...ts.openwall.com
Subject: Re: VNC Pcap's for cracking
On Mon, Mar 19, 2012 at 7:57 PM, Rich Rumble <richrumble@...il.com> wrote:
> Very nice! Sorry about the mislabel, I was doing so much that day
> I may have forgotten to reset it properly and or label it right. Great
> test of the module though :)
> I can't wait to see it in jumbo or the main branch!
I have just committed a new version of vncpcap2john which is able to
crack 3.7 and 3.8 protocols (both TightVNC and RealVNC supported). I
have tested it with your pcap files and it works fine.
There is something strange about 05-vnc-openwall-3.3.pcap and
06-vnc-openwall-3.3.pcap. For 05-vnc-openwall-3.3.pcap, VNC server is
at 192.168.1.10 and client is at 192.168.1.123. Then why is the
authentication challenge being sent form 192.168.1.123 to 192.168.1.10
(see wireshark). Shouldn't it be the other way round? (rest of the
pcap files are *correct* though). Any ideas?
--
Cheers,
Dhiru
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
