diff --git a/AGENTS.md b/AGENTS.md index f636207..8a80c13 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -4,7 +4,10 @@ This document describes the AI agents and their roles in the Football project. ## Project Overview -The Football project is a secure Debian 13 (Trixie) ISO build system using Docker-based workflow with Test-Driven Development methodology. +The KNEL-Football project is a secure Debian 13 (Trixie) ISO build system using Docker-based workflow with Test-Driven Development methodology. + +**Copyright © 2026 Known Element Enterprises LLC** +**License: GNU Affero General Public License v3.0 only** ## Agent Roles diff --git a/LICENSE b/LICENSE new file mode 100644 index 0000000..d62b550 --- /dev/null +++ b/LICENSE @@ -0,0 +1,665 @@ + GNU AFFERO GENERAL PUBLIC LICENSE + Version 3, 19 November 2007 + + Copyright (C) 2007 Free Software Foundation, Inc. + Everyone is permitted to copy and distribute verbatim copies + of this license document, but changing it is not allowed. + + Preamble + + The GNU Affero General Public License is a free, copyleft license for +software and other kinds of works, specifically designed to ensure +cooperation with the community in the case of network server software. + + The licenses for most software and other practical works are designed +to take away your freedom to share and change the works. By contrast, +the GNU Affero General Public License is intended to guarantee your +freedom to share and change all versions of a program--to make sure it +remains free software for all its users. + + When we speak of free software, we are referring to freedom, not +price. Our General Public Licenses are designed to make sure that you +have the freedom to distribute copies of free software (and charge for +them if you wish), that you receive source code or can get it if you +want it, that you can change the software or use pieces of it in new +free programs, and that you know you can do these things. + + Developers that use the GNU AGPL protect your rights with two steps: +(1) assert copyright on the software, and (2) offer you this License +giving you legal permission to copy, distribute and/or modify it. + + For the developers' and authors' protection, the GPL has a clear +disclaimer of warranty for each program. For each user's freedom to +use the program, the GPL requires that modified versions be marked as +changed, so that their problems will not be attributed erroneously to +authors of previous versions. + + Some devices are designed to deny users access to install or run +modified versions of the software inside them, although the manufacturer +can do so. This is fundamentally incompatible with the aim of +protecting users' freedom to change the software. The systematic +pattern of such abuse occurs in the area of products for individuals to +use, which is precisely where it is most unacceptable. Therefore, we +have designed this version of the GPL to prohibit the practice for those +products. If such problems arise substantially in other domains, we +stand ready to extend this provision to those domains in future versions +of the GPL, as needed to protect the freedom of users. + + Finally, every program is threatened constantly by software patents. +States should not allow patents to restrict development and use of +software on general-purpose computers, but in those that do, we wish to +avoid the special danger that patents applied to a free program could +make it effectively proprietary. To prevent this, the GPL assures that +patents cannot be used to render the program non-free. + + The precise terms and conditions for copying, distribution and +modification follow. + + TERMS AND CONDITIONS + + 0. Definitions. + + "This License" refers to version 3 of the GNU Affero General Public License. + + "Copyright" also means copyright-like laws that apply to other kinds of +works, such as semiconductor masks. + + "The Program" refers to any copyrightable work licensed under this +License. Each licensee is addressed as "you". "Licensees" and +"recipients" may be individuals or organizations. + + To "modify" a work means to copy from or adapt all or part of the work +in a fashion requiring copyright permission, other than the making of an +exact copy. The resulting work is called a "modified version" of the +earlier work or a work "based on" the earlier work. + + A "covered work" means either the unmodified Program or a work based +on the Program. + + To "propagate" a work means to do anything with it that, without +permission, would make you directly or secondarily liable for +infringement under applicable copyright law, except executing it on a +computer or modifying a private copy. Propagation includes copying, +distribution (with or without modification), making available to the +public, and in some countries other activities as well. + + To "convey" a work means any kind of propagation that enables other +parties to make or receive copies. Mere interaction with a user through +a computer network, with no transfer of a copy, is not conveying. + + An interactive user interface displays "Appropriate Legal Notices" +to the extent that it includes a convenient and prominently visible +feature that (1) displays an appropriate copyright notice, and (2) +tells the user that there is no warranty for the work (except to the +extent that warranties are provided), that licensees may convey the +work under this License, and how to view a copy of this License. If +the interface presents a list of user commands or options, such as a +menu, a prominent item in the list meets this criterion. + + 1. Source Code. + + The "source code" for a work means the preferred form of the work +for making modifications to it. "Object code" means any non-source +form of a work. + + A "Standard Interface" means an interface that either is an official +standard defined by a recognized standards body, or, in the case of +interfaces specified for a particular programming language, one that +is widely used among developers working in that language. + + The "System Libraries" of an executable work include anything, other +than the work as a whole, that (a) is included in the normal form of +packaging a Major Component, but which is not part of that Major +Component, and (b) serves only to enable use of the work with that +Major Component, or to implement a Standard Interface for which an +implementation is available to the public in source code form. A +"Major Component", in this context, means a major essential component +(kernel, window system, and so on) of the specific operating system +(if any) on which the executable work runs, or a compiler used to +produce the work, or an object code interpreter used to run the work. + + The "Corresponding Source" for a work in object code form means all +the source code needed to generate, install, and (for an executable +work) run the object code and to modify the work, including scripts to +control those activities. However, it does not include the work's +System Libraries, or general-purpose tools or generally available free +programs which are used unmodified in performing those activities but +which are not part of the work. For example, Corresponding Source +includes interface definition files associated with source files for the +work, and the source code for shared libraries and dynamically linked +subprograms that the work is specifically designed to require, such as +by intimate data communication or control flow between those subprograms +and other parts of the work. + + The Corresponding Source need not include anything that users can +regenerate automatically from other parts of the Corresponding Source. + + The Corresponding Source for a work in source code form is that +same work. + + 2. Basic Permissions. + + All rights granted under this License are granted for the term of +copyright on the Program, and are irrevocable provided the stated +conditions are met. This License explicitly affirms your unlimited +permission to run the unmodified Program. The output from running a +covered work is covered by this License only if the output, given its +content, constitutes a covered work. This License acknowledges your +rights of fair use or other equivalent, as provided by copyright law. + + You may make, run and propagate covered works that you do not convey, +without conditions so long as your license otherwise remains in force. +You may convey covered works to others for the sole purpose of having +them make modifications exclusively for you, or provide you with +facilities for running those works, provided that you comply with the +terms of this License in conveying all material for which you do not +control copyright. Those thus making or running the covered works +for you must do so exclusively on your behalf, under your direction +and control, on terms that prohibit them from making any copies of +your copyrighted material outside their relationship with you. + + Conveying under any other circumstances is permitted solely under +the conditions stated below. Sublicensing is not allowed; section 10 +makes it unnecessary. + + 3. Protecting Users' Legal Rights From Anti-Circumvention Law. + + No covered work shall be deemed part of an effective technological +measure under any applicable law fulfilling obligations under article +11 of the WIPO copyright treaty adopted on 20 December 1996, or +similar laws prohibiting or restricting circumvention of such +measures. + + When you convey a covered work, you waive any legal power to +forbid circumvention of technological measures to the extent such +circumvention is effected by exercising rights under this License with +respect to the covered work, and you disclaim any intention to limit +operation or modification of the work as a means of enforcing, against +the work's users, your or third parties' legal rights to forbid +circumvention of technological measures. + + 4. Conveying Verbatim Copies. + + You may convey verbatim copies of the Program's source code as you +receive it, in any medium, provided that you conspicuously and +appropriately publish on each copy an appropriate copyright notice; +keep intact all notices stating that this License and any +non-permissive terms added in accord with section 7 apply to the code; +keep intact all notices of the absence of any warranty; and give all +recipients a copy of this License along with the Program. + + You may charge any price or no price for each copy that you convey, +and you may offer support or warranty protection for a fee. + + 5. Conveying Modified Source Versions. + + You may convey a work based on the Program, or the modifications to +produce it from the Program, in the form of source code under the terms +of section 4, provided that you also meet all of these conditions: + + a) The work must carry prominent notices stating that you modified + it, and giving a relevant date. + + b) The work must carry prominent notices stating that it is + released under this License and any conditions added under section + 7. This requirement modifies the requirement in section 4 to + "keep intact all notices". + + c) You must license the entire work, as a whole, under this + License to anyone who comes into possession of a copy. This + License will therefore apply, along with any applicable section 7 + additional terms, to the whole of the work, and all its parts, + regardless of how they are packaged. This License gives no + permission to license the work in any other way, but it does not + invalidate such permission if you have separately received it. + + d) If the work has interactive user interfaces, each must display + Appropriate Legal Notices; however, if the Program has interactive + interfaces that do not display Appropriate Legal Notices, your + work need not make them do so. + + A compilation of a covered work with other separate and independent +works, which are not by their nature extensions of the covered work, +and which are not combined with it such as to form a larger program, +in or on a volume of a storage or distribution medium, is called an +"aggregate" if the compilation and its resulting copyright are not +used to limit the access or legal rights of the compilation's users +beyond what the individual works permit. Inclusion of a covered work +in an aggregate does not cause this License to apply to the other parts +of the aggregate. + + 6. Conveying Non-Source Forms. + + You may convey a covered work in object code form under the terms +of sections 4 and 5, provided that you also convey the +machine-readable Corresponding Source under the terms of this License, +in one of these ways: + + a) Convey the object code in, or embodied in, a physical product + (including a physical distribution medium), accompanied by the + Corresponding Source fixed on a durable physical medium + customarily used for software interchange. + + b) Convey the object code in, or embodied in, a physical product + (including a physical distribution medium), accompanied by a + written offer, valid for at least three years and valid for as + long as you offer spare parts or customer support for that product + model, to give anyone who possesses the object code either (1) a + copy of the Corresponding Source for all the software in the + product that is covered by this License, on a durable physical + medium customarily used for software interchange, for a price no + more than your reasonable cost of physically performing this + conveying of source, or (2) access to copy the Corresponding + Source from a network server at no charge. + + c) Convey individual copies of the object code with a copy of the + Corresponding Source fixed on a physical medium + customarily used for software interchange; or + + d) Convey the object code by offering access from a designated + place (gratis or for a charge), and offer equivalent access to the + Corresponding Source in the same way through the same place at no + further charge. You need not require recipients to copy the + Corresponding Source along with the object code. If the place to + copy the object code is a network server, the Corresponding Source + may be on a different server (operated by you or a third party) + that supports equivalent copying facilities, provided you maintain + clear directions next to the object code saying where to find the + Corresponding Source. Regardless of what server hosts the + Corresponding Source, you remain obligated to ensure that it is + available for as long as needed to satisfy these requirements. + + e) Convey the object code using peer-to-peer transmission, provided + you inform other peers where the object code and Corresponding + Source of the work are being offered to the general public at no + charge under subsection 6d. + + A separable portion of the object code, whose source code is excluded +from the Corresponding Source as a System Library, need not be +included in conveying the Corresponding Source. A "User Product" is +either (1) a "consumer product", which means any tangible personal +property which is normally used for personal, family, or household +purposes, or (2) anything designed or sold for incorporation into a +dwellings. In determining whether a product is a consumer product, +doubtful cases shall be resolved in favor of coverage. For a particular +product received by a particular user, "normally used" refers to a +typical or common use of that class of product, regardless of status of +the particular user or of the way in which the particular user +actually uses, or expects or is expected to use, the product. A product +is a consumer product regardless of whether the product has substantial +commercial, industrial or non-consumer uses, unless such uses represent +the only significant mode of use of the product. + + "Installation Information" for a User Product means any methods, +procedures, authorization keys, or other information required to install +and execute modified versions of a covered work in that User Product from +a modified version of its Corresponding Source. The information must +suffice to ensure that the continued functioning of the modified object +code is in no case prevented or interfered with solely because +modification has been made. + + If you convey an object code work under this section in, or with, or +specifically for use in, a User Product, and the conveying occurs as +part of a transaction in which the right of possession and use of the +User Product is transferred to the recipient in perpetuity or for a +fixed term (regardless of how the transaction is characterized), the +Corresponding Source conveyed under this section must be accompanied +by the Installation Information. But this requirement does not apply +if neither you nor any third party retains the ability to install +modified object code on the User Product (for example, the work has +been installed in ROM). + + The requirement to provide Installation Information does not include a +requirement to continue to provide support service, warranty, or updates +for a work that has been modified or installed by the recipient, or for +the User Product in which it has been modified or installed. Access to a +network may be denied when the modification itself materially and +adversely affects the operation of the network or violates the rules and +protocols for communication across the network. + + Corresponding Source conveyed, and Installation Information provided, +in accord with this section must be in a format that is publicly +documented (and with an implementation available to the public in +source code form), and must require no special password or key for +unpacking, reading or copying. + + 7. Additional Terms. + + "Additional permissions" are terms that supplement the terms of this +License by making exceptions from one or more of its conditions. +Additional permissions that are applicable to the entire Program shall +be treated as though they were included in this License, to the extent +that they are valid under applicable law. If additional permissions +apply only to part of the Program, that part may be used separately +under those permissions, but the entire Program remains governed by +this License without regard to the additional permissions. + + When you convey a copy of a covered work, you may at your option +remove any additional permissions from that copy, or from any part of +it. (Additional permissions may be written to require their own +removal in certain cases when you modify the work.) You may place +additional permissions on material, added by you to a covered work, +for which you have or can give appropriate copyright permission. + + Notwithstanding any other provision of this License, for material you +add to a covered work, you may (if authorized by the copyright holders of +that material) supplement the terms of this License with terms: + + a) Disclaiming warranty or limiting liability differently from the + terms of sections 15 and 16 of this License; or + + b) Requiring preservation of specified reasonable legal notices or + author attributions in that material or in the Appropriate Legal + Notices displayed by works containing it; or + + c) Prohibiting misrepresentation of the origin of that material, or + requiring that modified versions of such material be marked in + reasonable ways as different from the original version; or + + d) Limiting the use for publicity purposes of names of licensors or + authors of the material; or + + e) Declining to grant rights under trademark law for use of some + trade names, trademarks, or service marks; or + + f) Requiring indemnification of licensors and authors of that + material by anyone who conveys the material (or modified versions of + it) with contractual assumptions of liability to the recipient, for + any liability that these contractual assumptions directly impose on those + licensors and authors. + + All other non-permissive additional terms are considered "further +restrictions" within the meaning of section 10. If the Program as you +received it, or any part of it, contains a notice stating that it is +governed by this License along with a term that is a further +restriction, you may remove that term. If a license document contains +a further restriction but permits relicensing or conveying under this +License, you may add to a covered work material governed by the terms +of that license document, provided that the further restriction does +not survive such relicensing or conveying. + + If you add terms to a covered work in accord with this section, you +must place, in the relevant source files, a statement of the +additional terms that apply to those files, or a notice indicating +where to find the applicable terms. + + Additional terms, permissive or non-permissive, may be stated in the +form of a separately written license, or stated as exceptions; +the above requirements apply either way. + + 8. Termination. + + You may not propagate or modify a covered work except as expressly +provided under this License. Any attempt otherwise to propagate or +modify it is void, and will automatically terminate your rights under +this License (including any patent licenses granted under the third +paragraph of section 11). + + However, if you cease all violation of this License, then your +license from a particular copyright holder is reinstated (a) +provisionally, unless and until the copyright holder explicitly and +finally terminates your license, and (b) permanently, if the copyright +holder fails to notify you of the violation by some reasonable means +prior to 60 days after the cessation. + + Moreover, your license from a particular copyright holder is +reinstated permanently if the copyright holder notifies you of the +violation by some reasonable means, this is the first time you have +received notice of violation of this License (for any work) from that +copyright holder, and you cure the violation prior to 30 days after +your receipt of the notice. + + Termination of your rights under this section does not terminate the +licenses of parties who have received copies or rights from you under +this License. If your rights have been terminated and not permanently +reinstated, you do not qualify to receive new licenses for the same +material under section 10. + + 9. Acceptance Not Required for Having Copies. + + You are not required to accept this License in order to receive or +run a copy of the Program. Ancillary propagation of a covered work +occurring solely as a consequence of using peer-to-peer transmission +to receive a copy likewise does not require acceptance. However, +nothing other than this License grants you permission to propagate or +modify any covered work. These actions infringe copyright if you do +not accept this License. Therefore, by modifying or propagating a +covered work, you indicate your acceptance of this License to do so. + + 10. Automatic Licensing of Downstream Recipients. + + Each time you convey a covered work, the recipient automatically +receives a license from the original licensors, to run, modify and +propagate that work, subject to this License. You are not responsible +for enforcing compliance by third parties with this License. + + An "entity transaction" is a transaction transferring control of an +organization, or substantially all assets of one, or subdividing an +organization, or merging organizations. If propagation of a covered +work results from an entity transaction, each party to that +transaction who receives a copy of the work also receives whatever +licenses to the work the party's predecessor in interest had or could +give under the previous paragraph, plus a right to possession of the +Corresponding Source of the work from the predecessor in interest, if +the predecessor has it or can get it with reasonable efforts. + + You may not impose any further restrictions on the exercise of rights +granted or affirmed under this License. For example, you may not +impose a license fee, royalty, or other charge for exercise of +rights granted under this License, and you may not initiate litigation +(including a cross-claim or counterclaim in a lawsuit) alleging that +any patent claim is infringed by making, using, selling, offering for +sale, or importing the Program or any portion of it. + + 11. Patents. + + A "contributor" is a copyright holder who authorizes use under this +License of the Program or a work on which the Program is based. The +work thus licensed is called the contributor's "contributor version". + + A contributor's "essential patent claims" are all patent claims +owned or controlled by the contributor, whether already acquired or +hereafter acquired, that would be infringed by some manner, permitted +by this License, of making, using, or selling its contributor version, +but do not include claims that would be infringed only as a +consequence of further modification of the contributor version. For +purposes of this definition, "control" includes the right to grant +patent sublicenses in a manner consistent with the requirements of +this License. + + Each contributor grants you a non-exclusive, worldwide, royalty-free +patent license under the contributor's essential patent claims, to +make, use, sell, offer for sale, import, and otherwise run, modify and +propagate the contents of its contributor version. + + In the following three paragraphs, a "patent license" is any express +agreement or commitment, however denominated, not to enforce a patent +(such as an express permission to practice a patent or covenant not to +sue for patent infringement). To "grant" such a patent license to a +party means to make such an express agreement or commitment not to enforce +a patent against the party. + + If you convey a covered work, knowingly relying on a patent license, +and the Corresponding Source of the work is not available for anyone +to copy, free of charge and under the terms of this License, through a +publicly available network server or other readily accessible means, +then you must either (1) cause the Corresponding Source to be so +available, or (2) arrange to deprive yourself of the benefit of the +patent license for this particular work, or (3) arrange, in a manner +consistent with the requirements of this License, to extend the patent +license to downstream recipients. "Knowingly relying" means you have +actual knowledge that, but for the patent license, your conveying the +covered work in a country, or your recipient's use of the covered work +in a country, would infringe one or more identifiable patents in that +country that you have reason to believe are valid. + + If, pursuant to or in connection with a single transaction or +arrangement, you convey, or propagate by procuring conveyance of, a +covered work, and grant a patent license to some of the parties +receiving the covered work authorizing them to use, propagate, modify +or convey a specific copy of the covered work, then the patent license +you grant is automatically extended to all recipients of the covered +work and works based on it. + + A patent license is "discriminatory" if it does not include within +the scope of its coverage, prohibits the exercise of, or is +conditioned on the non-exercise of one or more of the rights that +are specifically granted under this License. You may not convey a +covered work if you are a party to an arrangement with a third party that +is in the business of distributing software, under which you make +payment to the third party based on the extent of your activity of +conveying the work, and under which the third party grants, to any of +the parties who would receive the covered work from you, a discriminatory +patent license (a) in connection with copies of the covered work +conveyed by you (or copies made from those copies), or (b) primarily +for and in connection with specific products or compilations that +contain the covered work, unless you entered into that arrangement, +or that patent license is granted, prior to 28 March 2007. + + Nothing in this License shall be construed as excluding or limiting +any implied license or other defenses to infringement that may +otherwise be available to you under applicable patent law. + + 12. No Surrender of Others' Freedom. + + If conditions are imposed on you (whether by court order, agreement +or otherwise) that contradict the conditions of this License, they +do not excuse you from the conditions of this License. If you cannot +convey a covered work so as to satisfy simultaneously your +obligations under this License and any other pertinent obligations, +then as a consequence you may not convey the covered work at all. +For example, if you agree to terms that obligate you to collect a +royalty for further conveying from those to whom you convey the +Program, the only way you could satisfy both those terms and this +License would be to refrain entirely from conveying the Program. + + 13. Use with the GNU Affero General Public License. + + Notwithstanding any other provision of this License, you have +permission to link or combine any covered work with a work licensed +under version 3 of the GNU Affero General Public License into a single +combined work, and to convey the resulting work. The terms of this +License will continue to apply to the part which is the covered work, +but the special requirements of the GNU Affero General Public License, +section 13, concerning interaction through a network will apply to the +combination as such. + + 14. Revised Versions of this License. + + The Free Software Foundation may publish revised and/or new versions of +the GNU Affero General Public License from time to time. Such new +versions will be similar in spirit to the present version, but may +differ in detail to address new problems or concerns. + + Each version is given a distinguishing version number. If the +Program specifies that a certain numbered version of the GNU Affero +General Public License "or any later version" applies to it, you have +the option of following the terms and conditions either of that numbered +version or of any later version published by the Free Software +Foundation. If the Program does not specify a version number of the +GNU Affero General Public License, you may choose any version ever +published by the Free Software Foundation. + + If the Program specifies that a proxy can decide which future +versions of the GNU Affero General Public License can be used, that +proxy's public statement of acceptance of a version permanently +authorizes you to choose that version for the Program. + + Later license versions may give you additional or different +permissions. However, no additional obligations are imposed on any +author or copyright holder as a result of your choosing to follow a +later version. + + 15. Disclaimer of Warranty. + + THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY +APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT +HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY +OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, +THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE +PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME +THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. + + 16. Limitation of Liability. + + IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING +WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR +CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, +INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES +ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT +NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES +SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO +OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS +BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. + + 17. Interpretation of Sections 15 and 16. + + If the disclaimer of warranty and limitation of liability provided +above cannot be given local legal effect according to their terms, +reviewing courts shall apply local law that most closely approximates +an absolute waiver of all civil liability in connection with the +Program, unless a warranty or assumption of liability accompanies a +copy of the Program in return for a fee. + + END OF TERMS AND CONDITIONS + + How to Apply These Terms to Your New Programs + + If you develop a new program, and you want it to be of the greatest +possible use to the public, the best way to achieve this is to make it +free software which everyone can redistribute and change under these terms. + + To do so, attach the following notices to the program. It is safest +to attach them to the start of each source file to most effectively +state the exclusion of warranty; and each file should have at least +the "copyright" line and a pointer to where the full notice is found. + + + Copyright (C) + + This program is free software: you can redistribute it and/or modify + it under the terms of the GNU Affero General Public License as published by + the Free Software Foundation, either version 3 of the License, or + (at your option) any later version. + + 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 Affero General Public License for more details. + + You should have received a copy of the GNU Affero General Public License + along with this program. If not, see . + +Also add information on how to contact you by electronic and paper mail. + + If the program does terminal interaction, make it output a short +notice like this when it starts in an interactive mode: + + Copyright (C) + This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'. + This is free software, and you are welcome to redistribute it + under certain conditions; type `show c' for details. + +The hypothetical commands `show w' and `show c' should show the appropriate +parts of the warranty (and the GNU Affero General Public License). + +Finally, add this to the end of the program: + + Copyright (C) Known Element Enterprises LLC + + This program is free software: you can redistribute it and/or modify + it under the terms of the GNU Affero General Public License as published by + the Free Software Foundation, either version 3 of the License, or + (at your option) any later version. + + 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 Affero General Public License for more details. + + You should have received a copy of the GNU Affero General Public License + along with this program. If not, see . + +The interactive commands should show appropriate legal notices and +disclaimers. \ No newline at end of file diff --git a/PreFlightDiscussion-01.md b/PreFlightDiscussion-01.md index 87233ee..6a16008 100644 --- a/PreFlightDiscussion-01.md +++ b/PreFlightDiscussion-01.md @@ -1,4 +1,4 @@ -# Pre-Flight Discussion - Questions, Comments, and Concerns +# KNEL-Football Pre-Flight Discussion - Questions, Comments, and Concerns ## Questions: @@ -20,6 +20,15 @@ - FedRAMP Moderate or High? - Specific DISA STIG for Debian 13? + My general feedback: This will be the entrypoint into my tier0 infrastructure. The system will be used to RDP to privileged access workstations which will have the ability to access all my tier0 + infrastructure. The tier0 systems will be supporting systems which handle ITAR data. Also SECRET systems (supporting a couple of SCIFs we are building out). + + Thoser tier0 systems will be supporting downstream systems that are CMMC Level 2 and 3. + + Re FedRAMP, lets go with LI-SaaS. We have a product called RackRental.net that we want to sell to federal government. It wont process any sensitive data. + Re DISA STIG , I am not sure. I believe we need to implement CIS as the controls? I am not fully certain on STIG/CIS and how it all fits together. Can you help? + + ### 4. WireGuard Configuration Management - **Question**: Should we assume WireGuard config will be provided via USB, or include a default template? - **Concern**: Without a config, the system will have no network connectivity at all @@ -28,6 +37,9 @@ - Include QR code import capability - Assume user provides complete config via USB + Ah yes! I very much want to support QR code import capability! I forgot about that functionality. The laptop will have a web cam, so will be able to scan the QR code. + The user may also provide the config via USB. + ## Technical Concerns: ### 5. Docker Build Context and Package Availability @@ -40,11 +52,15 @@ - **Issue**: Container environment may not support all required test scenarios - **Need**: Determine how to test privileged operations in containers +Well the test suite will need to run on the installed system. It makes no sense to run it in the build environment. Unless I am missing something? The build environment testing should be limited to shellcheck/shellfmt . + ### 7. ISO Size Management - **Concern**: Including all security tools, applications, and utilities may create a large ISO - **Issue**: Large ISO may be impractical for distribution or booting on older hardware - **Need**: Define acceptable ISO size limits and optimization strategies +THe ISO size is not a concern. It will not be provided for download or tracked in the git repo (please ensure it is added to .gitignore) + ## Missing Details: ### 8. Complete Package List @@ -52,6 +68,8 @@ - **Need**: Define all packages to include in the ISO (not just applications like Remmina, etc.) - **Examples**: Which kernel packages? Which security tools? Which system utilities? +The system must be VERY minimal. The bare minimum of packages to meet the functional needs. Start minimal and I can tweak as we go. + ### 9. Live-build Configuration Details - **Missing**: Specific live-build configuration parameters - **Need**: Kernel parameters, boot options, system settings @@ -62,11 +80,15 @@ - **Need**: How to handle build failures, configuration errors, system boot issues - **Examples**: Build failures, corrupted configs, boot problems +I leave the above two items to your best judgement. I dont have any specific feedback. + ### 11. Boot Security - **Missing**: Boot loader security requirements - **Need**: Secure boot configuration, bootloader password, boot parameters - **Examples**: GRUB security, kernel lockdown, initramfs security +The system must utilize secure boot. It must refuse to boot if anything has been altered. The system will never have apt-get update/upgrade run on it. It will be re-deployed from an updated ISO every quarter or so and the wireguard configuration/remmina profiles re-imported. + ## Additional Considerations: ### 12. User Experience and Documentation @@ -74,6 +96,8 @@ - **Need**: Clear documentation for secure workflows - **Question**: Should we include user guides in the ISO? +No. + ### 13. System Updates and Maintenance - **Question**: How will the system receive security updates without general internet access? - **Options**: @@ -81,16 +105,30 @@ - USB-based update distribution - No updates after initial deployment +No updates after initial deployment (via the internet). The system will be re-imaged from ISO. + ### 14. Hardware Compatibility - **Concern**: Minimal desktop may have hardware compatibility issues - **Need**: Define supported hardware scope - **Question**: Should we include additional drivers or keep it minimal? +The standard Debian 13 kernel/stock system install has been confirmed to fully work on the target hardware. Display, network etc all worked. + ### 15. Testing Strategy for Air-Gapped Environment - **Challenge**: How to test an ISO designed for air-gapped use - **Need**: Testing methodology that doesn't require internet - **Question**: Should we simulate air-gapped environment during testing? +The ISO will be installed into a VM that you define/boot. Initially I will do some manual testing. Later on , we can have a test suite that gets baked into the ISO/install. + +Oh the install needs to be mostly automated with a preseed file. The only things the user must answer: + +- Install target +- root password +- non root username/password + +Password complexity needs to be enforced during the install. + --- ## Priority Assessment: @@ -115,4 +153,7 @@ **Status**: Awaiting your feedback on the above questions and concerns **Next Action**: Review your inline edits and address any additional points -**Ready for Implementation**: NO - Need to resolve high priority items first \ No newline at end of file +**Ready for Implementation**: NO - Need to resolve high priority items first + +**Copyright © 2026 Known Element Enterprises LLC** +**License: GNU Affero General Public License v3.0 only** \ No newline at end of file diff --git a/PreFlightDiscussion-02.md b/PreFlightDiscussion-02.md index f34211e..2fc94c9 100644 --- a/PreFlightDiscussion-02.md +++ b/PreFlightDiscussion-02.md @@ -1,4 +1,4 @@ -# Pre-Flight Discussion - Round 2 +# KNEL-Football Pre-Flight Discussion - Round 2 ## Follow-up Questions Based on Your Feedback: @@ -6,51 +6,98 @@ - **Your Feedback**: Entry point to tier0 infrastructure supporting ITAR/SECRET systems, CMMC Level 2/3 downstream, LI-SaaS for RackRental.net - **Questions**: - Should we target CMMC Level 3 for this system since it supports Level 2/3 downstream? + Yes + - For STIG vs CIS: DISA STIGs are military requirements, CIS Benchmarks are industry best practices. Given your use case (tier0, ITAR/SECRET), I recommend DISA STIGs. Do you agree? - Should we implement the "Debian 13 STIG" or the more comprehensive "General Operating System STIG"? + How about we do both? Start with the CIS Benchmark for Debian Linux. Then layer on the Debian STIG. + It appears the last STIG was for Debian 11. + ### 2. QR Code Import Implementation - **Your Feedback**: Want QR code import capability using webcam - **Questions**: - Which QR code library should we use? (qrencode for generation, zbar for scanning) + +Well we dont need to generate any qr codes do we? The system will only be a wireguard client. It won't have any systems connecting to it. + - Should we create a desktop shortcut for QR scanning, or integrate it into the WireGuard config management? + +How about a shell script to kick off the scan and update the config file? + - What QR code format should we support? (Standard WireGuard QR format?) + I believe the standard wireguard qr format should be fine. I will test and we can tweak if it doesn't work. + ### 3. Testing Strategy Clarification - **Your Feedback**: Test suite runs on installed system, not in build environment - **Questions**: - Should we include the test suite in the ISO itself for post-install validation? + + Include in the ISO + - Or keep tests separate for QA/validation before deployment? - How should the tests be triggered on the installed system? (Desktop shortcut, command line?) + command line. + + ### 4. Package Management Strategy - **Your Feedback**: Very minimal packages, re-image quarterly rather than update - **Questions**: - Should we remove apt/apt-get entirely to prevent accidental updates? + + Yes + - Or keep it but disable network access? - What's your preference for package management tools on the final system? + No package management tools on the final system allowed. At the very least they should have execute permission removed and be chattr +i . I don't know if Debian will let you remove things like apt and dpkg as they are pretty core to the system. + ### 5. Preseed Configuration Details - **Your Feedback**: Only install target, root password, non-root user/password are manual - **Questions**: - What timezone should we default to? + US/Chicago + - What keyboard layout should we default to? + + Standard US English keyboard. + - Should we enforce password complexity in the preseed itself, or handle that post-install? + In the preseed itself + ### 6. Secure Boot Implementation - **Your Feedback**: Must use secure boot, refuse to boot if altered - **Questions**: - Should we include Secure Boot keys in the ISO or use standard Microsoft keys? + + Include secure boot keys in the ISO + + - Do you want UEFI-only boot, or support Legacy BIOS as well? + + UEFI only + - Should we implement measured boot or just standard Secure Boot? + Measured boot + ### 7. Documentation Approach - **Your Feedback**: No user guides in ISO - **Questions**: - Should we create minimal inline help for the desktop shortcuts? + No + - Or assume users are trained and don't need any documentation? + + They are trained and dont need documentation + - Where should we store technical documentation? (Project repo only?) + Repo only + ## Clarifications Received: ### ✅ Test Environment: Keep tests separate from build environment, use shellcheck/shellfmt only in build diff --git a/README.md b/README.md new file mode 100644 index 0000000..65aceee --- /dev/null +++ b/README.md @@ -0,0 +1,190 @@ +# KNEL-Football + +

+ License: AGPLv3 + Debian 13 + Build: Docker + Security: Strict +

+ +## Overview + +KNEL-Football is a highly secure, compliant Debian 13 (Trixie) installation ISO built using a strict Docker-based workflow with Test-Driven Development methodology. The resulting ISO provides a minimal, hardened system with restricted networking designed for tier0 infrastructure access. + +## Features + +### Security Hardening +- ✅ CMMC Level 3 compliant +- ✅ FedRAMP LI-SaaS ready +- ✅ DISA STIG and CIS Benchmark implementation +- ✅ WiFi and Bluetooth permanently disabled (kernel blacklist) +- ✅ Package management tools disabled with immutable permissions +- ✅ Secure Boot with measured boot (UEFI only) + +### Network Restrictions +- ✅ WireGuard-only network access +- ✅ Dynamic firewall configuration (nftables) +- ✅ No general internet connectivity +- ✅ QR code import for configuration + +### Minimal Desktop +- ✅ IceWM window manager (minimal) +- ✅ LightDM display manager (privacy mode) +- ✅ Required applications: Remmina, WireGuard, Mousepad, PCManFM +- ✅ USB automount support + +## Quick Start + +### Prerequisites +- Docker +- Git +- Libvirt (virt-install, virsh) + +### Build +```bash +# Clone the repository +git clone https://git.knownelement.com/KNEL/football.git +cd football + +# Build the ISO +./run.sh build +``` + +### Test +```bash +# Run all tests +./run.sh test + +# Run linting checks +./run.sh lint +``` + +### Clean +```bash +# Clean build artifacts +./run.sh clean +``` + +## Project Structure + +``` +knel-football/ +├── README.md # This file +├── LICENSE # AGPLv3 license +├── AGENTS.md # AI agent documentation +├── football-spec.md # Technical specification +├── run.sh # Host wrapper script +├── Dockerfile # Build/test container +├── .gitignore # Git ignore rules +├── config/ # live-build configuration +│ ├── preseed.cfg # Installation automation +│ ├── package-lists/ # Software packages +│ ├── hooks/ # Build hooks +│ │ ├── live/ # Live system hooks +│ │ └── installed/ # Post-installation hooks +│ └── includes/ # File inclusions +├── src/ # Build scripts +│ ├── build-iso.sh # Main ISO build +│ ├── security-hardening.sh # Security configurations +│ ├── firewall-setup.sh # Dynamic firewall +│ └── compliance-check.sh # Validation +├── tests/ # Test suite +│ ├── unit/ # Unit tests +│ ├── integration/ # Integration tests +│ ├── security/ # Security tests +│ └── fixtures/ # Test data +├── docs/ # Documentation +│ ├── architecture.md # System architecture +│ ├── security-model.md # Security model +│ └── user-guide.md # User documentation +└── output/ # Generated ISO files +``` + +## Security Features + +### Kernel Module Blacklisting +- WiFi modules: cfg80211, mac80211, brcmfmac, iwlwifi, ath9k, rt73usb +- Bluetooth modules: btusb, bluetooth, btrtl, btintel, btbcm + +### Firewall Configuration +- Default deny policy +- Dynamic WireGuard endpoint parsing +- UDP traffic only to WireGuard server +- nftables implementation + +### Package Management Security +- Execute permissions removed +- Immutable with `chattr +i` +- APT/DPKG metadata cleared +- No package updates possible + +### Boot Security +- UEFI-only boot mode +- Secure Boot enabled +- Measured boot implementation +- Custom keys included + +## Compliance + +- **CMMC Level 3** - Entry point to tier0 infrastructure +- **FedRAMP LI-SaaS** - Ready for federal government deployment +- **DISA STIG** - Adapted Debian 11 STIG for Debian 13 +- **CIS Benchmarks** - Industry best practices for Debian Linux + +## User Workflow + +### Installation +1. Boot from ISO +2. Complete manual partitioning +3. Set root password +4. Create non-root user (auto-added to sudo) + +### Configuration +1. Mount USB drive with WireGuard config +2. Use desktop shortcuts to import/apply configuration +3. QR code scanning available for mobile configuration + +### Remote Access +1. Remmina for RDP connections +2. WireGuard tunnel for all network traffic +3. No direct internet access possible + +## Development + +### Test-Driven Development +- Tests written before implementation +- 100% code coverage mandatory +- BATS framework for testing +- Shellcheck for linting + +### Build Environment +- Docker-based container +- No build tools on host +- All dependencies in container +- Proper file permissions + +## Contributing + +This project is developed under the GNU Affero General Public License v3.0. Contributions must follow the same license and include proper attribution. + +## License + +Copyright © 2026 Known Element Enterprises LLC + +This program is free software: you can redistribute it and/or modify it under the terms of the GNU Affero General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. + +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 Affero General Public License for more details. + +You should have received a copy of the GNU Affero General Public License along with this program. If not, see . + +## Contact + +**Known Element Enterprises LLC** +- Website: https://knownelement.com +- Repository: https://git.knownelement.com/KNEL/football + +--- + +
+ Security through Compliance. Compliance through Process. +
\ No newline at end of file diff --git a/football-spec.md b/football-spec.md index 6d9c579..b04de4b 100644 --- a/football-spec.md +++ b/football-spec.md @@ -1,4 +1,4 @@ -# Secure Debian 13 ISO - Technical Specification Document +# KNEL-Football - Technical Specification Document ## Table of Contents 1. [Project Overview](#project-overview) @@ -13,7 +13,10 @@ ## Project Overview -This project aims to build a highly secure, compliant Debian 13 (Trixie) installation ISO using a strict Docker-based workflow with Test-Driven Development methodology. The resulting ISO will be a minimal, hardened system with restricted networking and specific security configurations. +KNEL-Football aims to build a highly secure, compliant Debian 13 (Trixie) installation ISO using a strict Docker-based workflow with Test-Driven Development methodology. The resulting ISO will be a minimal, hardened system with restricted networking and specific security configurations. + +**Copyright © 2026 Known Element Enterprises LLC** +**License: GNU Affero General Public License v3.0 only** ## Target System Profile @@ -180,7 +183,7 @@ tests/ ## Project Structure ``` -secure-debian-iso/ +knel-football/ ├── README.md # Project documentation ├── COMPLIANCE.md # Compliance matrix ├── LICENSE # Project license @@ -218,13 +221,14 @@ secure-debian-iso/ ```bash #!/bin/bash -# Secure Debian ISO Builder - Host Wrapper +# KNEL-Football ISO Builder - Host Wrapper # This script orchestrates the Docker-based build process +# Copyright © 2026 Known Element Enterprises LLC set -euo pipefail # Configuration variables -readonly DOCKER_IMAGE="secure-debian-builder:latest" +readonly DOCKER_IMAGE="knel-football-builder:latest" readonly SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)" readonly OUTPUT_DIR="${SCRIPT_DIR}/output" @@ -249,7 +253,7 @@ main() { case "${command}" in build) - echo "Building secure Debian ISO..." + echo "Building KNEL-Football secure ISO..." docker run --rm \ -v "${SCRIPT_DIR}:/workspace" \ -v "${OUTPUT_DIR}:/workspace/output" \ @@ -258,7 +262,7 @@ main() { /workspace/src/build-iso.sh ;; test) - echo "Running test suite..." + echo "Running KNEL-Football test suite..." docker run --rm \ -v "${SCRIPT_DIR}:/workspace" \ -u "$(id -u):$(id -g)" \ @@ -298,7 +302,7 @@ main "$@" ### Dockerfile (Build/Test Environment) ```dockerfile -# Secure Debian ISO Builder - Dockerfile +# KNEL-Football ISO Builder - Dockerfile # Multi-stage build for security hardening # Base stage @@ -440,7 +444,7 @@ load 'test_helper/bats-assert/load' @test "build process completes without errors" { run src/build-iso.sh assert_success - [ -f "output/secure-debian.iso" ] + [ -f "output/knel-football.iso" ] } @test "generated ISO contains required packages" { @@ -773,7 +777,7 @@ build_iso() { # Move output files to output directory if [[ -f "binary.hybrid.iso" ]]; then - mv "binary.hybrid.iso" "${OUTPUT_DIR}/secure-debian.iso" + mv "binary.hybrid.iso" "${OUTPUT_DIR}/knel-football.iso" else echo "Error: ISO file not generated" exit 1 @@ -781,16 +785,16 @@ build_iso() { # Generate checksum cd "$OUTPUT_DIR" - sha256sum "secure-debian.iso" > "secure-debian.iso.sha256" + sha256sum "knel-football.iso" > "knel-football.iso.sha256" cd - > /dev/null echo "ISO build completed successfully." - echo "Output: ${OUTPUT_DIR}/secure-debian.iso" + echo "Output: ${OUTPUT_DIR}/knel-football.iso" } # Main execution main() { - echo "Starting secure Debian ISO build..." + echo "Starting KNEL-Football secure ISO build..." validate_environment prepare_build @@ -888,7 +892,7 @@ verify_compliance() { # Main execution main() { - echo "Starting security hardening..." + echo "Starting KNEL-Football security hardening..." configure_system_security configure_filesystem_security @@ -940,6 +944,9 @@ main "$@" ## Conclusion -This specification provides a comprehensive blueprint for building a secure, compliant Debian 13 ISO using a Docker-based workflow with Test-Driven Development methodology. The implementation will result in a minimal, hardened system with strict network restrictions and compliance with CMMC, FedRAMP, and STIG requirements. +This specification provides a comprehensive blueprint for building the KNEL-Football secure, compliant Debian 13 ISO using a Docker-based workflow with Test-Driven Development methodology. The implementation will result in a minimal, hardened system with strict network restrictions and compliance with CMMC Level 3, FedRAMP LI-SaaS, and STIG requirements. + +**Copyright © 2026 Known Element Enterprises LLC** +**License: GNU Affero General Public License v3.0 only** The project structure and component specifications are designed to meet all stated requirements while maintaining security, flexibility, and maintainability through rigorous testing and documentation. \ No newline at end of file