Hi there,
I am working on a user library that will be distributed under the terms of BSD license (probably 2-clause one). The library uses some code from net80211 and need to use wpa control interface for 802.1X and WPA/WPA2 related stuff.
My questions are;
1 ) Since the work in the user library would be "derivate work" based on net80211 code, say something from ieee80211_ioctl.c, the license for my file should look like something given below, is that correct?
License of ieee80211_ioctl.c
License in my file should be ?
2 ) There is also something from ifieee80211.c which has a long license statement...
From ifieee80211.c
And I should have something like ?
It is worth mentioning that, by "derivate work", I mean some wrappers around low-level ioctl(2) calls and helper functions.
3 ) Thankfully, wpa control interface is distributed under the terms of BSD license. My library needs to be compiled against wpa_ctrl.c and wpa_ctrl.h as I have to use some routines defined in this API.
Since base system does not have this API as an external library that I can link against, I am considering distributing these two files with my source code. Is that OK to include wpa_ctrl.c and wpa_ctrl.h in my source code, for instance in a folder called ext (for external), and distribute? Llicense for wpa control interface will be distibuted in its own directory.
Thanks
I am working on a user library that will be distributed under the terms of BSD license (probably 2-clause one). The library uses some code from net80211 and need to use wpa control interface for 802.1X and WPA/WPA2 related stuff.
My questions are;
1 ) Since the work in the user library would be "derivate work" based on net80211 code, say something from ieee80211_ioctl.c, the license for my file should look like something given below, is that correct?
License of ieee80211_ioctl.c
Code:
/*-
* Copyright (c) 2001 Atsushi Onoe
* Copyright (c) 2002-2009 Sam Leffler, Errno Consulting
* All rights reserved.
* ... reset of the BSD license clause
Code:
/*-
* Copyright (c) 2001 Atsushi Onoe
* Copyright (c) 2002-2009 Sam Leffler, Errno Consulting
* Copyright (c) 2016 Fehmi Noyan ISI
* All rights reserved.
* ... reset of the BSD license clauseFrom ifieee80211.c
Code:
/*
* Copyright 2001 The Aerospace Corporation. All rights reserved.
*
* ... rest of the BSD license
*/
/*
* Copyright (c) 1997, 1998, 2000 The NetBSD Foundation, Inc.
* All rights reserved.
*
* This code is derived from software contributed to The NetBSD Foundation
* by Jason R. Thorpe of the Numerical Aerospace Simulation Facility,
* NASA Ames Research Center.
* ... rest of the BSD license
*/
Code:
/*
* Copyright 2016 Fehmi Noyan ISI. All rights reserved.
*
* ... rest of the BSD license
*/
/*
* Copyright 2001 The Aerospace Corporation. All rights reserved.
*
* ... rest of the BSD license
*/
/*
* Copyright (c) 1997, 1998, 2000 The NetBSD Foundation, Inc.
* All rights reserved.
*
* This code is derived from software contributed to The NetBSD Foundation
* by Jason R. Thorpe of the Numerical Aerospace Simulation Facility,
* NASA Ames Research Center.
* ... rest of the BSD license
*/3 ) Thankfully, wpa control interface is distributed under the terms of BSD license. My library needs to be compiled against wpa_ctrl.c and wpa_ctrl.h as I have to use some routines defined in this API.
Since base system does not have this API as an external library that I can link against, I am considering distributing these two files with my source code. Is that OK to include wpa_ctrl.c and wpa_ctrl.h in my source code, for instance in a folder called ext (for external), and distribute? Llicense for wpa control interface will be distibuted in its own directory.
Thanks