Re: OT. Who knows about wifi sniffers and compiling code?

Bod43@xxxxxxxxxxxxx wrote:
On 13 Aug, 13:57, "Paul - xxx" <notcheckede...@xxxxxxxxxxx> wrote:
Bo...@xxxxxxxxxxxxx wrote:
On 13 Aug, 13:31, "Paul - xxx" <notcheckede...@xxxxxxxxxxx> wrote:
A neighbour is harder to keep out than passing traffic, he has a
long time to 'sniff' your wireless packets and make sense of it
all. I've found the best defence for me is using a combination of
the following.


of it, it isn't intuitive to use, still needs a ***-load of
experience to get the best out of it and barely helps 'Joe Bloggs'
crack anything.

IME, and YMMV, of course. ;)

I have never tried any of this but I use LAN ssniffers a lot
and I understnd that the ssid (even if hidden)
and for sure the mac are sent in
clear and that you WILL see them both if you have a sniffer.

My assumption would be that anyone who can
crack WEP will have no trouble with mac and ssid.
Maybe that's not exactly true?

My real point was meant to be similar, but slightly different in that many
people (from experience) have downloaded sniffers and such-like but don't
have the background knowledge, experience, or even brains, to work out how
to use them properly such that they can actually crack a system. The MAC
and SSID are not necessarily readily readable unless you have a sniffer
_and_ said knowledge/experience.

Mind, it doesn't take long to gain the knowledge, if you're a neighbour with
plenty time, intent on breaking in .... ;)

I guess that my concern is that the OP may
think that two out of three might be OK and would
not do the one he needs which is WPA.

I understand that at present WPA is uncrackable
except by exhaustive, dictionary and brute force,
password attacks and that for the present
the password space is big enough by quite a margin.

With WPA your mileage won't vary:-)

Fair comments. ;)

--
Paul - xxx


.