30 likes | 134 Vues
This document explores the NoCat system for public/community wireless access and the 802.1x protocol used for private/corporate network access. It outlines the ease of client configuration with NoCat, which only requires a browser, but warns about potential security risks like IP and MAC spoofing due to clear-text communication. In contrast, 802.1x requires a special supplicant for client authentication and offers improved security through per-session keys, making it more resilient against sniffing and cracking attempts.
E N D
NoCAT and 802.1x Target (pengguna) : NoCat - Public/Community Wireless Access AP 802.1x - Private/Corporate Network Access
NoCat - Konfigurasi client sangat mudah, hanya membutuhkan browser. - Kurang aman karena masih dimungkinkan terjadinya spoofing IP dan MAC address. - Komunikasi untuk authentikasi menggunakan clear text.
802.1x - Client membutuhkan supplicant khusus untuk melakukan authentikasi dan perlu konfigurasi khusus. - Komunikasi antara client (supplicant ) dengan AP ( authenticator ) lebih aman, spoffing dapat di hindari karena menggunakan per-session keys. - Relatif aman dari sniffing dan cracker