cozybit / hostap-sae Goto Github PK
View Code? Open in Web Editor NEWthis is a temporary fork of wpa_supplicant which adds support for SAE mesh security
Home Page: o11s.org
License: GNU General Public License v2.0
this is a temporary fork of wpa_supplicant which adds support for SAE mesh security
Home Page: o11s.org
License: GNU General Public License v2.0
wpa_supplicant and hostapd -------------------------- Copyright (c) 2002-2011, Jouni Malinen <[email protected]> and contributors All Rights Reserved. These programs are dual-licensed under both the GPL version 2 and BSD license (the one with advertisement clause removed). Either license may be used at your option. This package may include either wpa_supplicant, hostapd, or both. See README file respective subdirectories (wpa_supplicant/README or hostapd/README) for more details. Source code files were moved around in v0.6.x releases and compared to earlier releases, the programs are now built by first going to a subdirectory (wpa_supplicant or hostapd) and creating build configuration (.config) and running 'make' there (for Linux/BSD/cygwin builds). License ------- GPL v2: This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License version 2 as published by the Free Software Foundation. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA (this copy of the license is in COPYING file) Alternatively, this software may be distributed, used, and modified under the terms of BSD license: Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. Neither the name(s) of the above-listed copyright holder(s) nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Why selected interface and explicit specification of interface, result in different reporting? For example, if I configure a network providing '-i wlan0' I can only see it via list_networks with -i wlan0 explicitly given on the command line. Whereas, if I let wpa_cli discover the interface (p2p-dev-wlan0), I get nothing from list_networks, even though there is a defined network under wlan0. Only what is created under selected/discovered interface is show by default?
Should list_networks with no explicit interface not show all networks defined? I see p2p-dev-wlan0 as the 'same' interface as wlan0. So was expecting $ wpa_cli -i wlan0 list_networks to show my configured network, but also that wpa_cli list_networks (selected dev-p2p-wlan0) shows something not nothing.
The resulting wpa_supplicant.conf file is the same for either situation but clearly the wpa_cli internally knows or believes there is a difference between, p2p-dev-wlan0 and wlan0, should not the conf file or even the wpa_cli note this somehow? Or some way?
I do not know, if this is the right repository, but I saw, that wpa_cli only reports "OK" or "FAIL". This is not so ideal, because you do not know, what went wrong. Would be good, if the messages could be more verbose (maybe with extra option?).
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.