[licence] specific licenses for backdoor-factory software

[phil at reseau-libre.net]

Hi,

I'm currently packaging "backdoor-factory" for the pkg-security team. 
The tool is already in kali.
The upstream sources are hosted here:
https://github.com/secretsquirrel/the-backdoor-factory

The main tool is based on the  following license file (LICENSE.txt) :
-------------------8<-------------------
Copyright (c) 2013-2016, Joshua Pitts
All rights reserved.

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 of the copyright holder 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 HOLDER 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.
-------------------8<-------------------

The upstream sources also contain a subdir (not required for the tool 
but existing in the upstream git repository), containing the tool aPlib 
(a compression library).
This tool is using the following license (looks like common license), 
file aPLib/readme.txt:

-------------------8<-------------------
[...]

License
-------

aPLib is freeware. If you use aPLib in a product, an acknowledgement 
would be
appreciated, e.g. by adding something like the following to the 
documentation:

     This product uses the aPLib compression library,
     Copyright (c) 1998-2014 Joergen Ibsen, All Rights Reserved.
     For more information, please visit: http://www.ibsensoftware.com/

You may not redistribute aPLib without all of the files.

You may not edit or reverse engineer any of the files (except the header 
files
and the decompression code, which you may edit as long as you do not 
remove
the copyright notice).

You may not sell aPLib, or any part of it, for money (except for 
charging for
the media).

     #ifndef COMMON_SENSE

     This software is provided "as is". In no event shall I, the author, 
be
     liable for any kind of loss or damage arising out of the use, abuse 
or
     the inability to use this software. USE IT ENTIRELY AT YOUR OWN 
RISK!

     This software comes without any kind of warranty, either expressed 
or
     implied, including, but not limited to the implied warranties of
     merchantability or fitness for any particular purpose.

     If you do not agree with these terms or if your jurisdiction does 
not
     allow the exclusion of warranty and liability as stated above you 
are
     NOT allowed to use this software at all.

     #else

     Bla bla bla .. the usual stuff - you know it anyway:

     If anything goes even remotely wrong - blame _yourself_, NOT me!

     #endif
-------------------8<-------------------

- Is the main software legaly acceptable for Debian ?
- Do i need to clean the upstream (deleting aPlib dir) making a dfsg 
package or the upstream can be kept in the source package untouched if 
the aPlib is not installed in the bin packages ?

Thanks a lot for your response,
-- 
Philippe THIERRY.