Open GoogleCodeExporter opened 9 years ago
Hi :),
The cookie hijacker currently does not support WPA, it only supports WEP and
Open Networks (Networks without any key). Thats the reason why it is not
detecting any packet.
Original comment by savioboy...@gmail.com
on 24 Dec 2012 at 12:03
I entered a wep key to my router and the cookie hijacker program still does not
work. when I start cookie hijacker wlan01 put in monitor mode I select passive
mode, insert the wep key, the first light turns yellow, the second light blinks
four times and turns yellow, the third light remains red. I do not understand
where wrong and how can I fix probblena. I know an operating system on which
cookie hijacker has been tested and is working with version 1.8 and with what
type of wireless card has been tested? There is a detailed guide on how to make
cookie hijacker? thanks Nico
Original comment by nmand...@gmail.com
on 24 Dec 2012 at 1:38
there are some YouTube video tutorials that demonstrate how the cookie
hijackers passive mode works, Here are some of the tutorials:
https://www.youtube.com/watch?v=Bi-8JRNpMqo
https://www.youtube.com/watch?v=lCaOeXQiTZs
Original comment by savioboy...@gmail.com
on 26 Dec 2012 at 8:41
I'm getting a doubt. It 'possible that my card alpha model GE-RT3070 is not
compatible with cookie hijacker?
Original comment by nmand...@gmail.com
on 27 Dec 2012 at 7:43
P.S. when I close coockie hijaker I get an error window that says "Could not
start ksmserver. Check your installation" and backtrack restarts. Could this be
the problem?
Original comment by nmand...@gmail.com
on 27 Dec 2012 at 6:37
NO thats not the problem, infact i thought i had fixed that problem when
shutting down cookie hijacker (i'll work on the shutdown issue) .. If the card
is successfully placed on monitor mode when you are using it, then i don't
think the problem is with your card. The program actually hops through the
channels when it is working, You may sometimes have to leave the program to run
for sometime before it gets the packets in passive mode, especially if there is
not heavy traffic on the network.
Original comment by savioboy...@gmail.com
on 27 Dec 2012 at 8:26
the probble me raises doubts are as follows: the second led to coockie hijaker
(sniffing status) only blinks 4 times remain yellow, while the third led
(coockie detecnion) remains red and does not blink as in the video tutorial.
P.S. excuse my insistence but I saw that the program is very nice and I would
love to make it work :-). regards Nico
Original comment by nmand...@gmail.com
on 27 Dec 2012 at 9:43
I hope in the operation of this software. Despite my best efforts I could not
get it to work. I am very disappointed because I asked for help from those who
created cookie hijackers and I was not given a valid help. I entered the world
of Linux with enthusiasm but no one helps me .... I think I've met all the
requirements that cookie hijackers demands. I hope that some people give me
help in the enterprise. thanks
Original comment by nmand...@gmail.com
on 3 Jan 2013 at 3:31
The issue's tab is for reporting bugs, not all reports are fixed immediately,
so sometimes you have to be patient.
I have worked on the program and added a channel selection option.
Try the program again using the new function to lock on a specific channel.
Original comment by saviob...@rocketmail.com
on 13 Jan 2013 at 6:24
cookie hijacker does not work.
I connect to my wifi network, I start hijaker cookies, you disconnect from my
wifi network, I connect again back to my wifi network I start the attack,
position it passive mode, channel 6 I put my network, I enter the password, I
go on Start sniffing the cookie detection buffer LED remains red. We hope that
you can solve this probblema. If you need further information let me know.
regards Nicola
Original comment by nmand...@gmail.com
on 14 Jan 2013 at 8:10
Is the target channel using WEP or WPA Encryption?
Original comment by saviob...@rocketmail.com
on 14 Jan 2013 at 10:07
wep key and use channel 6.
Original comment by nmand...@gmail.com
on 14 Jan 2013 at 12:02
Original issue reported on code.google.com by
nmand...@gmail.com
on 24 Dec 2012 at 9:45