) , ( 4 k IV RC C P Å =
John attack, remeber attackers usually try to take advantage of everything in it's current state, alot of times these objects & software are shipped "loose" out_of_the_pkg. It's up to you on how fuctional & secure you want it to be. It's up to you to apply the policies so kindly provided by our GOV the NSA ect.....They have unclassified and released several PDF's that are available via google,digital libraries & whatnot.
Try to apply these standards,policies & proceedures to your wireless connection, I mean what does the DoD know about security? It's made public for a reason.
EXAMPLE: Of some recommendations & policies made by the NSA & our GOV ect.....
These recommendations include:
· Mutual Authentication
· Layer two encrypted tunnel
· Strong cryptographic integrity verification
Without these features, not only is a WLAN vulnerable, but the entire information
infrastructure of which it is a part is at risk. We also recommend per-packet
authentication although we would not go so far as to make it a requirement.
http://www.itoc.usma.edu/Documents/ITOC_TR-2003-101_(G6).pdf
http://www.fwuf.gov/slides/may02slides/wiltshire.pdf
http://iase.disa.mil/policy.html
http://www.sessionware.com/Download/...egy_011603.pdf
https://infosec.navy.mil/Documents/d...e=dodd&tab=dod
The more you read john the better, I'd rather give you a more advance answer than just telling you yes or no & giving you a answer that I feel that is to your level of knowledge. John, sometimes I think your a troll probe or another member, but rather than judging you here, I'll give you "benifit of the doubt" & provide you some helpfull info.
