DOCSLIB.ORG

Wireless Authentication

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Wireless Authentication Wireless Authentication Network Startup Resource Center www.nsrc.org These materials are licensed under the Creative Commons Attribution-NonCommercial 4.0 International license (http://creativecommons.org/licenses/by-nc/4.0/) Overview Define authentication Strengths and weaknesses of captive portals How captive portals work What is Authentication? Verifying the claim that an entity is allowed to act on behalf of a given known identity More simply: • Is this person/device who they say they are? • Can they prove it • for example, with password, signature? • In our case, the entity is the software, acting on behalf of the user controlling the computer. Why Is Auth So Complicated? I am on a computer. Am I its owner? • Device is not the same as person. I am a network administrator • Should I have access to the finance system? I am connecting to the network from home • Should I have access to all my work resources? I am a printer • Should I be able to scp files to the network? Authentication Core Concepts These are all different concepts: • Confidentiality • Access Control • Authorization • Authentication Confidentiality Ensure that only those who should have access to information can indeed do so (usually encryption) Access Control Access control is the mechanisms by which rights & restrictions are controlled & enforced Authorization Authorization defines what an entity (a user, a device) is authorized (allowed), to access • Which networks (ACLs/filters) • Which systems, which files ? (FS ACLs, permissions) • When can they do that (time policies) ? • Can they run an application or access a service ? Authentication We want to know: WHO, WHERE(*), WHEN • Which entity? • What AP did they associate with? • When did they log on ? • What IP number did they have? PSK (Pre-Shared Key) cannot tell us this. • Keys can be shared between users & devices. • We can’t know who, where, or when. Authentication Solutions We recommended two ways to do this: • Captive portal • 802.1X (EAPoL and EAP-TTLS) (Preferred) Your choice depends on: • The size of your organization • The maturity of your IT systems • Your human resources • Available user stores, databases • For example, Active Directory or LDAP Captive Portals: Positive • Popular (public areas, airports, hotels…) • Flexible • Self-explanatory (web page), can enforce AUP (Acceptable Use Policy) validation • Relatively easy to implement Captive Portals: Negative • Not transparent • Requires user to interact with the network using a web browser • Not standardized (different looks, different credentials, …) • Requires regular re-authentication (disruptive) Captive Portals: Negative • Breaks SSL by Man-In-The-Middle (MITM) • Makes assumption about client configuration (e.g. user-specified DNS resolver) • Often unreliable and fragile • Easy to hijaCk authentiCated session Captive Portals: Solutions Many vendors and open source projects • CoovaChilli • WiFidog • M0n0wall, pfSense • zeroshell Many networking vendors offer captive portals • Aptilo, Aruba, Cisco, HP, Mikrotik, Ubiquiti Captive Portals: Redirection Any of the following methods can be used: • HTTP silent redirection • HTTP 30x redirect • IP hijacking • DNS hijacking • Certain URLs may be allowed • e.g. Information, help, use policies pages Captive Portals: OS support Operating System (OS) requests well-known URL • If success, then user has Internet! ! • If failure, launch minimal browser to allow authentication with captive portal If you interfere with this process bad things can happen Don’t whitelist domains so OS thinks it has connectivity Use a 302 redirect to a valid HTTPS website to collect credentials Captive Portals: Components A captive portal ,aka Universal Access Method (UAM) needs the following: Network Access Controller (CoovaChilli, Unifi controller) RADIUS Server (Freeradius) Authentication Store (AD, LDAP, DB, or text file) Captive Portals: NAC Has two network interfaces: LAN • Offers DHCP lease to all wireless clients • Blocks all HTTPS traffic before auth to avoid cert mismatch • Web server+TLS to request authentication from clients • Captive web portal offers valid SSL certificate (LetsEncrypt!) WAN • Provides Internet connectivity to authenticated clients Facilitates authentication session between client and RADIUS Server Prevents unauthenticated clients from using the network Captive Portals: RADIUS Server Remote Authentication Dial-In User Service Provides Authentication, Authorization, and Accounting Attribute-Value pairs allow for flexibility Can talk to a variety of auth stores RFCs 2865, 2868, 5080 Captive Portals: RADIUS Server Authorization conversation looks like: Client submits credentials to NAC by HTTPS web form NAC sends Access Request message to RADIUS Server by RADIUS protocol RADIUS Server checks credentials by PAP/CHAP/EAP against auth store RADIUS Server replies to NAC with one of: Access Accept Access Reject Access Challenge RADIUS reply might also specify attributes like VLAN, bandwidth limit, dwell time, etc. for Access Accept Captive Portals: Authentication Store Common choices • Active Directory • LDAP • SQL db • ASCII text file Best to reuse an existing credential store if available Vouchers are common in hotels and coffee shops APIs can be used for 3rd party payment services like PayPal, HotSpotSystem, etc. Captive Portal: Sample Session Client requests DHCP address from NAC Client OS detects captive portal and requests HTTP URL NAC intercepts URL and 302 redirects to HTTPS login page Client submits credentials to captive web portal RADIUS server is queried for authorization NAC approves/denies network access based on RADIUS response Captive Portal: Diagram NAC RADIUS Filters / ACLs HTTP server Server Auth application Authentication Store Client Questions?.
Load more

Recommended publications
  • Campus Networking Best Practices Session 5: Wireless
    Campus Networking Best Practices Session 5: Wireless LAN Hervey Allen Dale Smith NSRC & University of Oregon University of Oregon & NSRC [email protected] [email protected] Wireless LAN • Provide wireless network across your campus that has the following characteristics: – Authentication – only allow your users – Roaming – allow users to start up in one section of your network, then move to another location – Runs on your campus network Firewall/ Border Traffic Shaper Router Wireless REN switch Authentication Core Gateway Router Core Servers Network Access Control (NAC) Enterprise Identity Management • Processes and Documentation of users. – Now you must deal with this. – What to use as the back-end user store? • LDAP • Active Directory • Kerberos • Other? – Will this play nice with future use? • email, student/staff information, resource access, ... Identity Management Cont. • An example of such a project can be seen here: – http://ccadmin.uoregon.edu/idm/ • This is a retrofit on to an already retrofitted system. • Learn from others and try to avoid this situation if possible. A Wireless Captive Portal The Wireless Captive Portal • Previous example was very simple. • A Captive Portal is your chance to: – Explain your Acceptable Use Policies – Decide if you must authenticate, or – Allow users on your network and monitor for problems instead (alternate solution). – Anything else? Branding? What's Happening? • remember our initial network diagrams...? • Do you think our hotel built their own solution? • Probably not... Commercial Solutions • Aruba http://www.arubanetworks.com/ • Bradford Networks – http://www.bradfordnetworks.com/ • Cisco NAC Appliance (Clean Access) – http://www.cisco.com/en/US/products/ps6128/ • Cisco Wireless LAN Controllers – http://www.cisco.com/en/US/products/hw/wireless/ • Enterasys http://www.enterasys.com/ • Vernier http://www.verniernetworks.com Open Source Solutions • CoovaChilli (morphed from Chillispot) – http://coova.org/wiki/index.php/CoovaChilli – Uses RADIUS for access and accounting.
    [Show full text]
  • Introduzione Al Mondo Freebsd
    Introduzione al mondo FreeBSD Corso avanzato Netstudent Netstudent http://netstudent.polito.it E.Richiardone [email protected] maggio 2009 CC-by http://creativecommons.org/licenses/by/2.5/it/ The FreeBSD project - 1 ·EÁ un progetto software open in parte finanziato ·Lo scopo eÁ mantenere e sviluppare il sistema operativo FreeBSD ·Nasce su CDROM come FreeBSD 1.0 nel 1993 ·Deriva da un patchkit per 386BSD, eredita codice da UNIX versione Berkeley 1977 ·Per problemi legali subisce un rallentamento, release 2.0 nel 1995 con codice royalty-free ·Dalla release 5.0 (2003) assume la struttura che ha oggi ·Disponibile per x86 32 e 64bit, ia64, MIPS, ppc, sparc... ·La mascotte (Beastie) nasce nel 1984 The FreeBSD project - 2 ·Erede di 4.4BSD (eÁ la stessa gente...) ·Sistema stabile; sviluppo uniforme; codice molto chiaro, ordinato e ben commentato ·Documentazione ufficiale ben curata ·Licenza molto permissiva, spesso attrae aziende per progetti commerciali: ·saltuariamente esterni collaborano con implementazioni ex-novo (i.e. Intel, GEOM, atheros, NDISwrapper, ZFS) ·a volte no (i.e. Windows NT) ·Semplificazione di molte caratteristiche tradizionali UNIX Di cosa si tratta Il progetto FreeBSD include: ·Un sistema base ·Bootloader, kernel, moduli, librerie di base, comandi e utility di base, servizi tradizionali ·Sorgenti completi in /usr/src (~500MB) ·EÁ giaÁ abbastanza completo (i.e. ipfw, ppp, bind, ...) ·Un sistema di gestione per software aggiuntivo ·Ports e packages ·Documentazione, canali di assistenza, strumenti di sviluppo ·i.e. Handbook,
    [Show full text]
  • M0n0wall and PPTP Preface
    M0n0wall and PPTP December 8, 2003 Version 1.0 Francisco Artes [email protected] Preface: ............................................................................................................................... 1 Audience: ............................................................................................................................ 1 Assumptions:....................................................................................................................... 2 Subnetting and VLAN routing:........................................................................................... 2 Setup of m0n0wall software: .............................................................................................. 3 PPTP User Setup:................................................................................................................5 PPTP Firewall Rules:.......................................................................................................... 6 Example of filtered PPTP Rules: .................................................................................... 9 Setting up a PPTP Client on Windows XP™:................................................................... 11 Testing our PPTP Connection in Windows ™: ............................................................ 14 Some things I have found not to work over the PPTP Connection: ................................. 17 Preface: This document is intended to outline several different PPTP VPN type setups, it includes a how-to on setting up a
    [Show full text]
  • List of BSD Operating Systems
    FreeBSD-based SNo Name Description A lightweight operating system that aims to bring the flexibility and philosophy of Arch 1 ArchBSD Linux to BSD-based operating systems. 2 AskoziaPBX Discontinued 3 BSDBox 4 BSDeviant 5 BSDLive 6 Bzerk CD 7 DragonFly BSD Originally forked from FreeBSD 4.8, now developed in a different direction 8 ClosedBSD DesktopBSD is a discontinued desktop-oriented FreeBSD variant using K Desktop 9 DesktopBSD Environment 3.5. 10 EclipseBSD Formerly DamnSmallBSD; a small live FreeBSD environment geared toward developers and 11 Evoke system administrators. 12 FenestrOS BSD 13 FreeBSDLive FreeBSD 14 LiveCD 15 FreeNAS 16 FreeSBIE A "portable system administrator toolkit". It generally contains software for hardware tests, 17 Frenzy Live CD file system check, security check and network setup and analysis. Debian 18 GNU/kFreeBSD 19 Ging Gentoo/*BSD subproject to port Gentoo features such as Portage to the FreeBSD operating 20 Gentoo/FreeBSD system GhostBSD is a Unix-derivative, desktop-oriented operating system based on FreeBSD. It aims to be easy to install, ready-to-use and easy to use. Its goal is to combine the stability 21 GhostBSD and security of FreeBSD with pre-installed Gnome, Mate, Xfce, LXDE or Openbox graphical user interface. 22 GuLIC-BSD 23 HamFreeSBIE 24 HeX IronPort 25 security appliances AsyncOS 26 JunOS For Juniper routers A LiveCD or USB stick-based modular toolkit, including an anonymous surfing capability using Tor. The author also made NetBSD LiveUSB - MaheshaNetBSD, and DragonFlyBSD 27 MaheshaBSD LiveUSB - MaheshaDragonFlyBSD. A LiveCD can be made from all these USB distributions by running the /makeiso script in the root directory.
    [Show full text]
  • How to Accelerate Your Internet
    How To Accelerate Your Internet A practical guide to Bandwidth Management and Optimisation using Open Source Software How To Accelerate Your Internet For more information about this project, visit us online at http://bwmo.net/ Editor: Flickenger R. Associate Editors: Belcher M., Canessa E., Zennaro M. Publishers: INASP/ICTP © 2006, BMO Book Sprint Team First edition: October 2006 ISBN: 0-9778093-1-5 Many designations used by manufacturers and vendors to distinguish their products are claimed as trademarks. Where those designations appear in this book, and the authors were aware of a trademark claim, the designations have been printed in all caps or initial caps. All other trademarks are property of their respective owners. The authors and publisher have taken due care in preparation of this book, but make no expressed or implied warranty of any kind and assume no responsibil- ity for errors or omissions. No liability is assumed for incidental or consequen- tial damages in connection with or arising out of the use of the information con- tained herein. This work is released under the Creative Commons Attribution-ShareAlike 2.5 license. For more details regarding your rights to use and redistribute this work, see http://creativecommons.org/licenses/by-sa/2.5/ Contents Preface ix About This Book xi Introduction 1 Bandwidth, throughput, latency, and speed.............................................................................. 2 Not enough to go around........................................................................................................
    [Show full text]
  • Introduzione Al Mondo Freebsd Corso Avanzato
    Introduzione al mondo FreeBSD corso Avanzato •Struttura •Installazione •Configurazione •I ports •Gestione •Netstudent http://netstudent.polito.it •E.Richiardone [email protected] •Novembre 2012 •CC-by http://creativecommons.org/licenses/by/3.0/it/ The FreeBSD project - 1 • E` un progetto software open • Lo scopo e` mantenere e sviluppare il sistema operativo FreeBSD • Nasce su CDROM come FreeBSD 1.0 nel 1993 • Deriva da un patchkit per 386BSD, eredita codice da UNIX versione Berkeley 1977 • Per problemi legali subisce un rallentamento, release 2.0 nel 1995 con codice royalty-free • Dalla release 4.0 (2000) assume la struttura che ha oggi • Disponibile per x86 32 e 64bit, ia64, MIPS, ppc, sparc... • La mascotte (Beastie) nasce nel 1984 The FreeBSD project - 2 • Erede di 4.4BSD (e` la stessa gente...) • Sistema stabile; sviluppo uniforme; codice molto chiaro, ordinato e ben commentato • Documentazione ufficiale ben curata • Licenza molto permissiva, spesso attrae aziende per progetti commerciali: • saltuariamente progetti collaborano con implementazioni ex-novo (i.e. Intel, GEOM, NDISwrapper, ZFS, GNU/Linux emulation) • Semplificazione di molte caratteristiche tradizionali UNIX Di cosa si tratta Il progetto FreeBSD include: • Un sistema base • Bootloader, kernel, moduli, librerie di base, comandi e utility di base, servizi tradizionali • Sorgenti completi in /usr/src (~500MB) • E` gia` completo (i.e. ipfw, ppp, bind, ...) • Un sistema di gestione per software aggiuntivo • Ports e packages • Documentazione, canali di assistenza, strumenti
    [Show full text]
  • Pare-Feu : Architecture Et Déploiement V1.0
    Pare-feu : architecture et déploiement V1.0 Pare-feu : Architecture et déploiement V 1.0 Stéphane DUFOUR (Architecte système et sécurité) - 1 - Pare-feu : architecture et déploiement V1.0 Table des matières PARE-FEU : ARCHITECTURE ET DEPLOIEMENT ..............................................................................................................................0 TABLE DES MATIERES...................................................................................................................................................................2 INTRODUCTION ...........................................................................................................................................................................4 CONCEPTS DE BASE......................................................................................................................................................................5 RAPPEL SECURITE .................................................................................................................................................................................5 Les fondamentaux ......................................................................................................................................................................5 Les menaces ................................................................................................................................................................................6 Best practice .............................................................................................................................................................................16
    [Show full text]
  • The Open Source Firewall in Practice
    OPNsense The open source fi rewall in practice Table of contents 1. How companies can benefit from OPNsense 3| 2. What makes OPNsense unique? 4| 2.1 The OPNsense Business Edition 3. A closer look at OPNsense 5| 3.1 Intrusion and malware detection 6| 3.2 Virtual Private Networking (VPN) 3.3 High availability 7| 3.4 Traffic analysis and traffic shaping 3.5 Further features in the core system 3.6 Plugins 8| 4. Hardware for OPNsense 8| 5. Using OPNsense 8| 5.1 Example customer A: 9| An SME specializing in the production of technical ropes 5.2 Example customer B: An SME consulting firm in the social sector 6. Plugins for OPNsense 9| 7. Transparent development model 10| 8. Plugins in an example scenario 10| 8.1 Centralized WLAN protection with the FreeRADIUS plugin 10| 8.2 Securing an Exchange Server with the Postfix plugin 14| 8.3 Monitoring with the Telegraf plugin 18| 8.4 NUT plugin for UPS integration 21| Summary 22| thomas-krenn.com | 3 OPNsense The open source fi rewall in practice Comprehensive IT security and fl exibly expandable plugins. IT managers regularly see the IT they manage intrusion detection & prevention, VPN, two- exposed to new threats. Having the latest fi rewall factor authentication and high availability. In this is no longer suffi cient. It is much more important e-book, we present OPNsense as an alternative to be able to react fl exibly to security risks. The to commercial fi rewall solutions. Our focus is on open source fi rewall OPNsense is a digital platform practical use cases in the SME context and on how that offers many additional features such as functionality can be expanded via plugins.
    [Show full text]
  • Automated Policy Enforcement in Software Defined Networking and Network Function Virtualization Environment
    Master of Science in Computer Engineering Master Degree Thesis Automated Policy Enforcement in Software Defined Networking and Network Function Virtualization Environment Supervisors prof. Riccardo Sisto prof. Fulvio Valenza dott. Daniele Bringhenti Candidate Antonio Amoroso Academic Year 2020-2021 This work is subject to the Creative Commons Licence Summary The increasing spreading of the amount of exchanging data and the dynamic de- ployment of applications and services lead to an evolution of the traditional network technology. One possible solution is based on virtualization, in particular, exploit- ing the Network Function Virtualization (NFV) parading. It is an architectural approach which aim is to decouple the network functions and the hardware ap- pliances, making possible the deployment of network service on general-purpose servers, achieving flexibility during the design of a particular service. A problem that arises is the service design that usually is performed manually, and this can lead to errors, especially if the service under analysis is related to security functions, such as firewalls. In order to avoid these errors, an automated approach should be used. In this context, it is possible to use a policy-based model that can be refined and translated. Because of this consideration, this thesis focussed on security inside NFV, in particular, analyzing packet filter behavior and it contributed to the translation from a medium language policy to a low-level configuration taking care of different firewall languages used in different scenarios. Moreover, it contributed tothede- velopment of VEREFOO (VErified REFinement and Optimized Orchestration), a framework that aims to provide a Security Automation approach as a solution to the problem highlighted before.
    [Show full text]
  • Kansalaisen Mikrotuen Palomuurijärjestelmä
    Opinnäytetyö (AMK) Tietojenkäsittelyn koulutusohjelma Tietoliikenne 2012 Tero Mäkelä KANSALAISEN MIKROTUEN PALOMUURIJÄRJESTELMÄ OPINNÄYTETYÖ (AMK) | TIIVISTELMÄ Turun ammattikorkeakoulu Tietojenkäsittelyn koulutusohjelma | Tietoliikenne Marraskuu 2012 | 59 sivua Esko Vainikka Tero Mäkelä KANSALAISEN MIKROTUEN PALOMUURIJÄRJESTELMÄ Opinnäytetyön tavoitteena on luoda Kansalaisen mikrotuelle palomuurijärjestelmä, jolla saadaan jaettua asiakas- ja työntekijälaitteet omiin verkkoihin. Rajatussa asiakasverkossa laitteet voidaan huoltaa turvallisesti vaikuttamatta muiden laitteiden tietoturvallisuuteen haitallisesti. Lisäksi luodaan palomuurijärjestelmän käyttöohjeet. Palomuurijärjestelmän luomisprosessia tarkastellaan järjestelmäkehityksen elinkaarimallin avulla. Palomuurin ja RAID-tekniikoiden toiminta pyritään selvittämään perusominaisuuksien ja toimintaperiaatteiden osalta. Järjestelmän alkuunpanossa selvitetään palomuurin vaatimusmäärittelyt, jonka jälkeen hankitaan tarvittavat laitekomponentit ja selvitetään Kansalaisen mikrotuen verkon rakenne. Tämän jälkeen suoritetaan palomuurijärjestelmien vertailu, jonka perusteella valitaan käyttöön tuleva palomuurijärjestelmä. Lopuksi järjestelmä asennetaan ja asetetaan asetukset vaatimusmäärittelyn mukaisesti. Järjestelmä saatiin otettua käyttöön useista järjestelmän asennuksen aikana syntyneistä vastoinkäymisistä huolimatta. Järjestelmä saatiin vastaamaan vaatimusmäärittelyjä muuten, paitsi välityspalvelimen osalta. ASIASANAT: Palomuurit, RAID, Kansalaisen mikrotuki, pfSense BACHELOR´S THESIS |
    [Show full text]
  • Pfsense Tutorial Slides (Application/Pdf
    pfSense Tutorial BSDCan 2008 From zero to hero with pfSense May 13, 2008 Chris Buechler <[email protected]> Scott Ullrich <[email protected]> History of pfSense Started as a work project 13 years ago when we needed a internal firewall Originally Linux, switched to FreeBSD 2.2 Evolution of this path shrunk the firewall down to a Soekris size Moatware was started Met Chris Buechler during this time Sell a number of products Sales guy moves to Florida Moatware fails Chris and myself debate starting over fresh pfSense is forked from m0n0wall roughly 4 years ago Still going strong today pfSense Overview Customized FreeBSD distribution tailored for use as a firewall and router. pfSense has many base features and can be extended with the package system including one touch installations of popular 3rd party packages such as SpamD (spam filter) and Squid (web caching). Includes many features found in commercial products such as Cisco PIX, Sonicwall, Watchguard, etc. Many support avenues available, mailing lists, forum and commercial support. Has the best price on the planet.... Free! pfSense Platforms Live CD Full Install Embedded Developers pfSense Stable Versions 1.0 - October 4, 2006 * 1.0.1 - October 20, 2006 * 1.2 - RELENG_1_2 - February 25, 2008 Downloaded more than 500,000 times to date * Not branched in CVS pfSense Development Versions Current Development Versions 1.3-ALPHA - RELENG_1 2.0-ALPHA-ALPHA-ALPHA - HEAD Snapshots are built every two hours available at http://snapshots.pfsense.org Bonus for attendees - 1.3 snapshots
    [Show full text]
  • Laboratorio 5 “Soluciones Libres”
    Laboratorio 5 “Soluciones Libres” 3.1 3.1.1 Describa las características principales de OpenWRT R. OpenWrt es una distribución de Linux basada en firmware usada para dispositivos empotrados tales como routers personales. El soporte originalmente fue limitado al modelo Linksys WRT54G, pero desde su rápida expansión se ha incluido soporte para otros fabricantes y dispositivos, incluidos el Netgear, D- Link, ASUS y algunos otros. El router más popular sigue siendo el Linksys WRT54G y el ASUS WL500G. OpenWrt utiliza principalmente una interfaz de línea de comando, pero también dispone de una interfaz WEB en constante mejora. El soporte técnico es provisto como en la mayoría de los proyectos de Software Libre, a través de foros y su canal IRC. 3.1.2 Describa los procedimientos para flashear un router con OpenWRT R. Conectamos el PC al router mediante un cable a cualquiera de los puertos LAN del router. El router nos servirá una IP por DHCP. Los dispositivos TP-LINK utilizan la subred 192.168.0.0/24, la IP del router será la192.168.0.1, y la que nos asigne a nuestro PC será cualquier IP dentro de ese rango. Ya podemos acceder al panel de administración, vía web, a través de esta dirección: http://192.168.0.1, con el usuario admin, contraseña admin. Accedemos ahora al menú System tools, subapartado Firmware Upgrade. Del selector de archivos subimos el firmware de OpenWRT que hemos descargado antes, y apretamos el boton deUpgrade Firmware. Tardará unos 5 minutos en completar el proceso. Ya tenemos OpenWRT en nuestro router.
    [Show full text]