Open GoogleCodeExporter opened 8 years ago
I haven't used it, but it's worth looking in to when I get a chance.
Original comment by cheff...@tacnetsol.com
on 3 Jan 2012 at 5:19
In aircrack suite you just have to support address like 127.0.0.1:12345 instead
of capture interface. If you'll implement it, i advise you to add a URI schema
to address, like airserv://127.0.0.1:12345.
Original comment by xpeh.o...@googlemail.com
on 3 Jan 2012 at 5:22
If you do it, it will be really nice, then i can try it on Windows without need
to install linups as main OS. Could you then write a manual how to complile
that thing on windows?
Original comment by xpeh.o...@googlemail.com
on 3 Jan 2012 at 5:25
Currently talking with the aircrack-ng team to get Reaver integrated into the
aircrack-ng suite. Support for airserv will likely be added as part of this
process, though I can't give you any kind of a timeline right now.
Original comment by cheff...@tacnetsol.com
on 4 Jan 2012 at 2:58
Thanks! I've noticed that there is no format description for airserv format
(opensource is so opensource, huh?). Documentation is not just information,
it's like an agreement that certifies, that things described in it most likely
would not be changed, and other things can be changed.
I tried to use newer aircrack suite with older airserv and noticed that they
don't work together and even there is no error message. Seems, they simply
changed the protocol so that it's impossible to determine what protocol version
is used by the server. (Open source don't care about binary compability). If
you already contacted them, could you ask them
1) that they document their airserv protocol
2) that they add some kind of version information, so in case they change this
protocol client programs have a chance to notice that?
Original comment by xpeh.o...@googlemail.com
on 5 Jan 2012 at 6:01
Original issue reported on code.google.com by
xpeh.o...@googlemail.com
on 3 Jan 2012 at 5:04