KNEL/football
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore: Remove obsolete files and root scripts

Browse Source 
- Remove .dockerignore, Dockerfile from root
- Remove LICENSE (moved to docs)
- Remove archive-docs/ directory
- Remove run.sh (moved to src/)
- Clean up obsolete configuration

💘 Generated with Crush

Assisted-by: GLM-4.6 via Crush <crush@charm.land>
This commit is contained in:
Charles N Wyble
2026-01-21 15:40:44 -05:00
parent 6d11ef8622
commit ff23e478e4
7 changed files with 0 additions and 2060 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
.dockerignore
View File

@@ -1,10 +0,0 @@
# Docker ignore patterns
.git
.gitignore
*.md
plan/
output/
.iso
.qcow2
.vmdk
*.log

58
Dockerfile
View File

@@ -1,58 +0,0 @@
# KNEL-Football ISO Builder - Dockerfile
# Multi-stage build for security hardening
# Base stage
FROM debian:13.3-slim AS base
# Set environment variables
ENV DEBIAN_FRONTEND=noninteractive
ENV LANG=C.UTF-8
# Install base dependencies
RUN apt-get update && apt-get install -y \
ca-certificates \
gnupg \
curl \
wget \
git \
&& apt-get clean && rm -rf /var/lib/apt/lists/*
# Builder stage
FROM base AS builder
# Install build dependencies
RUN apt-get update && apt-get install -y \
live-build \
debootstrap \
squashfs-tools \
xorriso \
grub-pc-bin \
grub-efi-amd64-bin \
mtools \
dosfstools \
&& apt-get clean && rm -rf /var/lib/apt/lists/*
# Install testing dependencies
RUN apt-get update && apt-get install -y \
bats \
shellcheck \
nftables \
iptables \
&& apt-get clean && rm -rf /var/lib/apt/lists/*
# Install additional security tools
RUN apt-get update && apt-get install -y \
auditd \
rsyslog \
&& apt-get clean && rm -rf /var/lib/apt/lists/*
# Create workspace directory
WORKDIR /workspace
# Set proper permissions
RUN groupadd -r builder && useradd -r -g builder builder
RUN chown -R builder:builder /workspace
USER builder
# Default command
CMD ["/bin/bash"]

665
LICENSE
View File

@@ -1,665 +0,0 @@
GNU AFFERO GENERAL PUBLIC LICENSE
Version 3, 19 November 2007
Copyright (C) 2007 Free Software Foundation, Inc. <https://fsf.org/>
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.
<one line to give the program's name and a brief idea of what it does.>
Copyright (C) <year> <name of author>
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 <https://www.gnu.org/licenses/>.
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:
<program> Copyright (C) <year> <name of author>
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) <year> 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 <https://www.gnu.org/licenses/>.
The interactive commands should show appropriate legal notices and
disclaimers.

805
archive-docs/AGENTS.md
View File

@@ -1,805 +0,0 @@
# AGENTS.md - Football Secure Access System
## Project Orientation
**Last Orientation**: 2025-01-20
### Related Documentation
For comprehensive functional requirements and artifact properties, see:
- `docs/FUNCTIONAL-REQUIREMENTS.md` - Complete functional requirements specification
- `docs/BUILD-DOCUMENTATION.md` - Build system documentation
- `docs/SECURITY-BASELINES.md` - Security hardening guide
- `COMMIT_CONVENTIONS.md` - Git commit message format and conventions
### Project Overview
Football is a minimal, hardened Debian 13 (trixie) system for secure remote access to privileged infrastructure. It enforces strict network controls where ALL traffic must pass through a WireGuard VPN tunnel, with direct network access completely blocked.
### Build Methodology
The project uses an **ISO-based installer approach**:
1. **Create Preseed**: Generate Debian installer automation file
2. **Download ISO**: Get Debian netinst ISO
3. **Inject Preseed**: Embed preseed configuration into ISO
4. **Build ISO**: Create custom football-installer.iso
5. **Deploy**: Boot ISO on bare metal or VM
6. **Automate Installer**: Preseed answers all questions except:
- Username/password creation
- Root password setting
- Target disk selection
The output is a **bootable ISO with embedded preseed configuration** that automates most of the Debian installation process.
### Key Design Decisions
- **ISO-based installer**: Uses standard Debian installer with preseed automation
- **Docker-based ISO build**: All ISO creation work done in containers
- **Preseed automation**: Automates all installation steps except user/disk selection
- **Minimal post-install configuration**: Security configs applied via late_command in preseed
- **Zero remote administration**: SSH, telnet, etc. completely disabled
- **WireGuard-only networking**: Direct network access blocked, all traffic through VPN
---
## Current Project Status
**Last Updated**: 2025-01-20
**Status**: ✅ READY TO BUILD
**Build Method**: ISO-based installer with preseed configuration
**Artifacts**:
1. `football-installer.iso` - Bootable ISO with embedded preseed (for bare metal and VM)
2. ISO boots in QEMU for automated testing
---
## Executive Summary
The Football Secure Access System is a minimal, hardened Debian 13 (trixie) system designed for Tier0 infrastructure protection. It provides secure remote access to privileged workstations via WireGuard VPN, with all direct network access blocked.
### Current Status
| Component | Status | Notes |
|-----------|--------|--------|
| Preseed Configuration | ✅ COMPLETE | config/preseed.cfg ready |
| ISO Build Script | ✅ COMPLETE | scripts/build-iso.sh operational |
| Security Scripts | ✅ COMPLETE | All security configs in place |
| Build System | ✅ COMPLETE | Docker-based ISO build working |
| First Boot Verification | ✅ COMPLETE | verify-system.sh ready |
| Documentation | ✅ COMPLETE | All documentation updated |
### Migration Summary
**Previous Approach**: Debootstrap-based build (manual image creation)
**Current Approach**: ISO-based installer with preseed automation
**Migration Date**: 2025-01-20
**Migration Reason**: More reliable, uses standard Debian installer
All obsolete debootstrap-related files and documentation have been removed.
---
## Project Architecture
### Purpose
**Football** is a minimal Debian system for secure remote access to high-security physical infrastructure (Tier0 protection).
### Deployment Targets
1. **Physical Hardware**: Dell laptops deployed in server rooms
2. **Virtual Machines**: QEMU-based VMs for testing and deployment
### Use Cases
- Secure remote RDP access to privileged workstations
- Controlled environment for system administration
- Tier0 infrastructure protection (CMMC Level 3, FedRAMP Moderate)
- Air-gapped system (WireGuard tunneling required)
---
## Security Model
### Core Principles
1. **Zero Direct Network Access**: All traffic routed through WireGuard VPN
2. **No Remote Administration**: SSH, telnet, etc. completely disabled
3. **Secure Boot Enforced**: UEFI with secure boot enabled
4. **Minimal Attack Surface**: Only IceWM and Remmina installed
5. **Local Console Only**: No remote administration capabilities
### Network Topology
```
┌─────────────────────────────────────────────────────────┐
│ Football System │
│ │
│ ┌─────────────────────────────────────────┐ │
│ │ Physical Interface (eth0) │ │
│ │ ├─ DHCP: Allowed (IP acquire)│ │
│ │ └─ WireGuard: ONLY (VPN) │ │
│ └─────────────────────────────────────────┘ │
│ │ │
│ ▼ │
│ ┌─────────────────────────────────────────┐ │
│ │ WireGuard Interface (wg0) │ │
│ │ └─ ALL outbound traffic │ │
│ └─────────────────────────────────────────┘ │
│ │ │
│ ▼ │
│ ┌─────────────────────────────────────────┐ │
│ │ VPN Endpoint (Server) │ │
│ │ → PAW Workstation │ │
│ └─────────────────────────────────────────┘ │
│ │
└─────────────────────────────────────────────────────────────────┘
```
### Firewall Rules
**Default Policy**: DROP ALL
**Specific Rules**:
- **INPUT**:
- ACCEPT on lo (loopback)
- ACCEPT from WireGuard endpoint (UDP port 51820)
- ACCEPT DHCP responses (UDP port 67)
- DROP everything else
- **OUTPUT**:
- ACCEPT to WireGuard endpoint (UDP port 51820)
- ACCEPT DHCP requests (UDP port 67)
- DROP everything else on eth0
- ACCEPT everything on wg0 (VPN interface)
- **FORWARD**: DROP
---
## Compliance Standards
### CIS Debian 13 Benchmark
**Version**: 3.0.0
**Overall Score**: 94.7% (180/190 controls)
**Applicable Controls**: 180 implemented
**Not Applicable**: 10 controls (not relevant to minimal system)
### CMMC Level 3
**Domain**: Controlled Unclassified Information (CUI)
**Practices Implemented**: 176/176 (100%)
**Maturity Level**: Level 3 (Optimized)
### FedRAMP Moderate
**Control Baseline**: Moderate
**Controls Implemented**: 325/325 (100%)
**Impact Level**: Moderate
**Sensitivity**: FIPS 140-2 (configurable)
### NIST SP 800-53 Moderate
**Security Controls**: 325/325 (100%)
**Privacy Controls**: All applicable
**Impact**: Moderate
### NIST SP 800-171
**Protecting CUI**: 110/110 practices (100%)
**Security Requirements**: All met
**Controls**: Comprehensive
---
## File Structure
```
football/
├── README.md # Project overview
├── COMPLIANCE.md # Compliance mapping
├── COMMIT_CONVENTIONS.md # Git commit conventions
├── AGENTS.md # This file - project orientation
├── LICENSE # License file
│
├── scripts/ # Build and test scripts
│ ├── build-iso.sh # ISO build script (main entry point)
│ ├── test-iso.sh # ISO testing script
│ └── verify-system.sh # System verification script
│
├── config/ # Configuration and scripts
│ ├── preseed.cfg # Debian installer preseed file
│ ├── preseed.sh # Preseed generation script
│ ├── harden.sh # Security hardening script
│ ├── packages.list # Packages to install
│ ├── secureboot.sh # Secure boot setup
│ ├── security-config.sh # Security configuration (passwords, auto-lock, USB, WiFi/BT)
│ ├── disable-wifi-bt.sh # Disable WiFi and Bluetooth
│ ├── setup-wireguard.sh # WireGuard client setup
│ ├── setup-wg-server.sh # WireGuard server setup
│ ├── football-first-boot.service # First-boot systemd service
│ └── wg-server-config-example.conf
│
├── tests/ # Test and verification scripts
│ ├── verify-compliance.sh # Verify configuration compliance
│ ├── compliance-test.sh # Full compliance test suite
│ └── test-iso.sh # ISO testing
│
├── docs/ # Documentation
│ ├── FUNCTIONAL-REQUIREMENTS.md # Functional requirements specification
│ ├── BUILD-DOCUMENTATION.md # Build system documentation
│ ├── SECURITY-BASELINES.md # Security hardening guide
│ ├── INCIDENT-RESPONSE.md # Incident response procedures
│ ├── SECURITY-POLICY.md # Security policies
│ └── TEST-EVIDENCE.md # Test documentation
│
├── keys/ # WireGuard keys
│ ├── private.key # Client private key
│ └── public.key # Client public key
│
├── output/ # Build output directory (empty, ready for builds)
│ └── football-installer.iso # Final ISO artifact (will be created)
│
├── logs/ # Build and test logs (ready for use)
│
└── .git/ # Git repository
```
---
## Configuration Files
### Security Configurations
All configuration files validated and ready:
#### 1. Preseed Configuration (preseed.cfg)
**Location**: `config/preseed.cfg`
**Purpose**: Automates Debian installer
**Key Settings**:
- Locale: en_US.UTF-8
- Timezone: UTC
- Keyboard: US
- Partitioning: Use entire disk with LVM
- User creation: Manual (prompted during install)
- Root password: Manual (prompted during install)
- Mirror: Default Debian mirror
- Packages: Minimal base system
- Late command: Applies all security configurations
**Status**: ✅ Validated
---
#### 2. Security Configuration (security-config.sh)
**Location**: `config/security-config.sh`
**Purpose**: Apply security configurations during install
**Key Features**:
- Password complexity enforcement (12 chars, mixed case, digits, special chars)
- Auto-lock after 1 minute idle
- USB drive mounting configuration
- Disable WiFi and Bluetooth modules
- Configure LightDM for secure login
**Status**: ✅ Validated
---
#### 3. WiFi and Bluetooth Disabling (disable-wifi-bt.sh)
**Location**: `config/disable-wifi-bt.sh`
**Purpose**: Disable all wireless capabilities
**Key Actions**:
- Blacklist WiFi kernel modules (iwlwifi, ath9k, brcmfmac, etc.)
- Blacklist Bluetooth kernel modules (btusb, bluetooth, etc.)
- Mask bluetooth service
- Remove bluez packages
**Status**: ✅ Validated
---
#### 4. WireGuard Configuration (setup-wireguard.sh)
**Location**: `config/setup-wireguard.sh`
**Purpose**: Configure WireGuard client
**Template**:
```ini
[Interface]
PrivateKey = <PRIVATE_KEY_PLACEHOLDER>
Address = 10.100.0.2/24
DNS = 8.8.8.8, 8.8.4.4
[Peer]
PublicKey = <SERVER_PUBLIC_KEY>
Endpoint = <ENDPOINT_IP>:<ENDPOINT_PORT>
AllowedIPs = 0.0.0.0/0
PersistentKeepalive = 25
```
**Status**: ✅ Template validated
---
#### 5. LightDM Configuration
**Location**: Applied by `config/security-config.sh`
**Purpose**: Secure display manager login
**Configuration**:
- `hide-users=true` - No username list displayed
- `show-manual-login=true` - Manual username entry only
- `allow-guest=false` - No guest sessions
- XDMCP disabled - No remote X sessions
**Status**: ✅ Validated
---
## Scripts
### Build Scripts
#### 1. build-iso.sh
**Purpose**: Build custom Football ISO from Debian netinst
**Location**: `scripts/build-iso.sh`
**Process**:
1. Check for required tools (xorriso, wget, etc.)
2. Download Debian 13.3.0 netinst ISO (if not cached)
3. Extract ISO to temporary directory
4. Inject preseed configuration
5. Inject custom scripts and configs
6. Repackage ISO as football-installer.iso
7. Copy to output directory
**Usage**:
```bash
./scripts/build-iso.sh
```
**Requirements**:
- Docker (recommended)
- wget
- xorriso
- Sufficient disk space (~4GB)
**Status**: ✅ COMPLETE and validated
---
#### 2. test-iso.sh
**Purpose**: Test built ISO in QEMU
**Location**: `scripts/test-iso.sh`
**Process**:
1. Check for QEMU tools
2. Start VM with ISO
3. Monitor boot for errors
4. Check for login prompt
5. Stop VM
**Usage**:
```bash
./scripts/test-iso.sh
```
**Requirements**:
- QEMU installed
- ISO built and present in output/
**Status**: ✅ COMPLETE and validated
---
#### 3. verify-system.sh
**Purpose**: Verify system meets functional requirements
**Location**: `scripts/verify-system.sh`
**Tests**:
- Boot sequence verification
- Login functionality
- LightDM secure configuration
- Password complexity enforcement
- Auto-lock functionality
- USB mounting capability
- WiFi/Bluetooth disabled
- WireGuard configuration template
- Network isolation (no direct access)
- System package verification
**Usage**:
```bash
./scripts/verify-system.sh
```
**Execution**:
- Runs automatically on first boot via systemd service
- Creates status file after successful run
- Prevents re-running on subsequent boots
**Status**: ✅ COMPLETE and validated
---
### Configuration Scripts
#### 1. preseed.sh
**Purpose**: Generate preseed configuration dynamically
**Location**: `config/preseed.sh`
**Status**: ✅ Validated
---
#### 2. harden.sh
**Purpose**: Apply CIS Benchmark security controls
**Location**: `config/harden.sh`
**Tasks**:
- Configure kernel parameters (sysctl)
- Set password policy (pwquality)
- Configure audit rules (auditd)
- Configure logging (rsyslog)
- Secure filesystems
- Configure PAM
- Harden kernel
- Configure firewall rules
- Remove unnecessary services
**Status**: ✅ Validated
---
#### 3. secureboot.sh
**Purpose**: Configure UEFI Secure Boot
**Location**: `config/secureboot.sh`
**Status**: ✅ Validated
---
#### 4. security-config.sh
**Purpose**: Apply all security configurations
**Location**: `config/security-config.sh`
**Features**:
1. Password complexity enforcement via PAM
2. Auto-lock configuration (xscreensaver, xautolock)
3. USB mounting configuration (polkit rules, udisks2)
4. WiFi/Bluetooth disabling
5. LightDM secure greeter configuration
**Status**: ✅ Validated
---
#### 5. disable-wifi-bt.sh
**Purpose**: Disable all wireless capabilities
**Location**: `config/disable-wifi-bt.sh`
**Blacklists**:
- WiFi: iwlwifi, ath9k, brcmfmac, rtlwifi, rt2800usb, ath5k, etc.
- Bluetooth: btusb, bluetooth, hidp, rfcomm, bnep, etc.
**Status**: ✅ Validated
---
#### 6. setup-wireguard.sh
**Purpose**: Configure WireGuard client
**Location**: `config/setup-wireguard.sh`
**Actions**:
- Install WireGuard packages
- Create configuration from template
- Set correct permissions
- Enable WireGuard service
**Status**: ✅ Template validated
---
#### 7. setup-wg-server.sh
**Purpose**: Set up WireGuard server endpoint
**Location**: `config/setup-wg-server.sh`
**Status**: ✅ Validated (for reference only)
---
## Deployment
### Virtual Machine Deployment
**Image**: `output/football-installer.iso`
**Boot Command**:
```bash
qemu-system-x86_64 \
-m 2048 \
-smp 2 \
-cdrom output/football-installer.iso \
-drive file=disk.qcow2,format=qcow2 \
-nographic
```
**Boot Requirements**:
- QEMU installed (for VM)
- 2GB RAM minimum
- UEFI support required
**Installation Process**:
1. Boot from ISO
2. Preseed automatically answers most questions
3. User creates username and password
4. User selects target disk
5. Installation completes automatically
6. System reboots
7. First-boot verification runs
**First Boot**:
1. System boots to LightDM login
2. User logs in with created credentials
3. IceWM starts
4. Verify-system.sh runs automatically
5. Results logged to /var/log/football-verify.log
6. Configure WireGuard endpoint (if needed)
7. Connect to VPN
8. Access remote RDP systems
---
### Physical Hardware Deployment
**Image**: `output/football-installer.iso`
**Write to USB/Disk**:
```bash
sudo dd if=output/football-installer.iso of=/dev/sdX bs=4M status=progress
```
**Boot Requirements**:
- UEFI BIOS required
- Secure Boot support
- Minimum 2GB RAM
- 8GB disk space
**First Boot**: Same as VM deployment
---
## Verification
### System Verification Checklist
**Boot Verification**:
- [ ] System boots without kernel panic
- [ ] GRUB loads correctly
- [ ] Kernel loads successfully
- [ ] systemd starts services
- [ ] LightDM starts
- [ ] Login prompt appears
- [ ] Username input works (manual entry)
- [ ] Password input works
**Security Verification**:
- [ ] SSH service disabled
- [ ] Telnet service disabled
- [ ] Firewall rules active
- [ ] WireGuard interface configured
- [ ] Direct network access blocked
- [ ] Only WireGuard traffic allowed
- [ ] WiFi modules blacklisted
- [ ] Bluetooth modules blacklisted
- [ ] Bluetooth service masked
**Functionality Verification**:
- [ ] WireGuard can connect
- [ ] Can reach PAW workstation
- [ ] Remmina is installed
- [ ] Remmina can connect to RDP
- [ ] System is stable
- [ ] Logs are being written
- [ ] USB drives mount correctly
- [ ] Auto-lock after 1 minute works
- [ ] Password complexity enforced
**Compliance Verification**:
- [ ] All CIS controls implemented
- [ ] All CMMC practices met
- [ ] All FedRAMP controls met
- [ ] All NIST controls met
- [ ] Compliance tests pass
---
## Build System
### ISO Build Process
The build system creates a custom Debian ISO with embedded preseed configuration and security scripts.
**Build Steps**:
1. **Download Debian ISO**:
- Downloads Debian 13.3.0 netinst ISO
- Caches ISO for faster subsequent builds
- Verifies ISO integrity
2. **Extract ISO**:
- Extracts ISO contents to temporary directory
- Preserves ISO structure
3. **Inject Preseed**:
- Copies preseed.cfg to ISO root
- Configures installer to use preseed
4. **Inject Scripts and Configs**:
- Copies all config/ scripts to ISO
- Copies verify-system.sh to ISO
- Sets correct permissions
5. **Repackage ISO**:
- Uses xorriso to create new ISO
- Preserves boot information
- Creates football-installer.iso
6. **Output**:
- Copies final ISO to output/ directory
- Cleans up temporary directories
- Reports build status
**Build Time**: 5-10 minutes (depending on network)
**Disk Space Required**: ~4GB temporary space
---
## Testing
### ISO Testing
**Purpose**: Verify ISO boots and installs correctly
**Test Process**:
1. Start VM with ISO
2. Monitor boot sequence
3. Verify installer starts
4. Check preseed is applied
5. Verify installation completes
6. Verify system boots
7. Verify login works
**Test Script**: `scripts/test-iso.sh`
---
### Compliance Testing
**Purpose**: Verify all compliance controls are implemented
**Test Script**: `tests/verify-compliance.sh` and `tests/compliance-test.sh`
**Tests**:
- CIS Debian 13 Benchmark
- CMMC Level 3 practices
- FedRAMP Moderate controls
- NIST SP 800-53 controls
- NIST SP 800-171 practices
---
### System Verification
**Purpose**: Verify functional requirements are met
**Test Script**: `scripts/verify-system.sh`
**Tests**:
- Boot sequence
- Login functionality
- Security configurations
- Network isolation
- Feature verification
---
## Troubleshooting
### Build Issues
**Issue**: Download fails
**Solution**: Check network connection, try manual download
**Issue**: ISO extraction fails
**Solution**: Ensure sufficient disk space, clean temporary directory
**Issue**: ISO won't boot
**Solution**: Verify integrity with checksum, check UEFI support
---
### Installation Issues
**Issue**: Preseed not applied
**Solution**: Verify preseed.cfg is in ISO root, check naming
**Issue**: Installation fails
**Solution**: Check logs, verify hardware compatibility, try without preseed
**Issue**: Won't boot after install
**Solution**: Check GRUB installation, verify UEFI settings
---
### Post-Installation Issues
**Issue**: Can't login
**Solution**: Verify username was created, check caps lock
**Issue**: WiFi not disabled
**Solution**: Check blacklist files, verify module names
**Issue**: Auto-lock not working
**Solution**: Check xscreensaver configuration, verify xautolock
**Issue**: USB not mounting
**Solution**: Verify user in correct groups, check polkit rules
**Issue**: WireGuard won't connect
**Solution**: Verify endpoint is reachable, check keys, verify configuration
---
## Contributing
When contributing to the Football project:
1. Follow commit conventions (see COMMIT_CONVENTIONS.md)
2. Test changes thoroughly
3. Update documentation
4. Verify compliance
5. Commit and push frequently
---
## License
See LICENSE file for details.
---
**End of AGENTS.md**

134
archive-docs/COMMIT_CONVENTIONS.md
View File

@@ -1,134 +0,0 @@
# Commit Conventions
## Format
All commits must follow conventional commit format:
```
<type>: <concise description>
[Optional detailed description with bullet points for larger changes]
[Optional sections like "Files Updated", "Files Added", etc.]
💘 Generated with Crush
Assisted-by: <model name> via Crush <crush@charm.land>
```
## Commit Types
- `feat:` - New feature or functionality
- `fix:` - Bug fix
- `docs:` - Documentation changes only
- `style:` - Code style changes (formatting, no logic changes)
- `refactor:` - Code refactoring (neither fix nor feature)
- `perf:` - Performance improvements
- `test:` - Adding or updating tests
- `chore:` - Maintenance tasks, build process changes, dependencies
- `ci:` - CI/CD configuration changes
## Description Rules
- Keep subject line under 72 characters
- Use imperative mood ("Add" not "Adds", "Update" not "Updates")
- Use sentence case, not title case
- Do not end with period
- Reference relevant issues in description if applicable
## Detailed Description
For larger commits, include:
- Bullet points explaining what was changed
- Sections for "Files Updated" and/or "Files Added"
- Reference to functional requirements or specifications
- Rationale for changes when not obvious
## Attribution
All commits must include these footer lines:
```
💘 Generated with Crush
Assisted-by: <model name> via Crush <crush@charm.land>
```
Examples:
- `Assisted-by: GLM-4.7 via Crush <crush@charm.land>`
- `Assisted-by: Gemini 2.5 Flash via Crush <crush@charm.land>`
## Examples
### Simple Commit
```
fix: Correct ISO mount permissions
Fixed mount permissions issue when building custom ISO.
💘 Generated with Crush
Assisted-by: GLM-4.7 via Crush <crush@charm.land>
```
### Feature Commit
```
feat: Add LightDM display manager for secure login
Implements minimal, secure login without username display:
1. **LightDM Installation**:
- Added lightdm and lightdm-gtk-greeter packages
- Enabled LightDM service by default
- Set default target to graphical
2. **Minimal and Secure Greeter**:
- Configured /etc/lightdm/lightdm.conf:
* hide-users=true (no username list displayed)
* show-manual-login=true (manual username entry only)
* allow-guest=false (no guest sessions)
- Greeter shows only username, password, login button
Files Updated:
- config/preseed.cfg (LightDM packages, enabled service)
- config/security-config.sh (LightDM configuration)
💘 Generated with Crush
Assisted-by: Gemini 2.5 Flash via Crush <crush@charm.land>
```
## Branching
- `main` - Production-ready code
- Feature branches: `feat/feature-name`
- Bugfix branches: `fix/bug-description`
- Refactor branches: `refactor/component-name`
## Push Frequency
**CRITICAL**: Commit and push frequently as work progresses.
- After each significant change
- Before switching tasks
- When pausing work
- Minimum: Every 5-10 minutes of active work
- Always push before closing conversation
## Verification
Before pushing, ensure:
```bash
git status # Working tree clean?
git log --oneline -3 # Commit message format correct?
```
## References
- [Conventional Commits](https://www.conventionalcommits.org/)
- [AGENTS.md](./AGENTS.md) - Project documentation
- [README.md](./README.md) - Project overview

311
archive-docs/README.md
View File

@@ -1,311 +0,0 @@
# Football - Minimal Debian Secure Access System
Fully self-contained, stripped-down, and locked-down Debian image intended for deployment onto physical access-only systems (Dell Laptop) called football-(x). Used for remote RDP access to high-security physical systems (highside) which are privileged access workstations in the KNEL server room.
## Overview
Football is a minimal Debian system designed for secure remote access to privileged infrastructure. It enforces strict network controls where **ALL traffic must pass through a WireGuard VPN tunnel**, with direct network access completely blocked.
**For complete functional requirements and artifact properties, see [docs/FUNCTIONAL-REQUIREMENTS.md](docs/FUNCTIONAL-REQUIREMENTS.md)**
## Architecture
### Security Model
- **Zero remote access**: No SSH, telnet, or any inbound services
- **WireGuard-only networking**: All traffic routed through mandatory VPN tunnel
- **Secure Boot enforced**: Kernel and bootloader signatures verified
- **Minimal attack surface**: Only IceWM and Remmina installed
- **Local console only**: No remote administration capabilities
### Network Configuration
```
Physical Interface (eth0)
├─ DHCP: Allowed (for IP acquisition)
└─ WireGuard: ONLY allowed connection to configured endpoint
└─ Endpoint: WG_ENDPOINT_IP:WG_ENDPOINT_PORT (configurable)
WireGuard Interface (wg0)
└─ ALL outbound traffic
└─ VPN endpoint → PAW (Privileged Access Workstation)
```
### Firewall Rules
- **INPUT**: DROP (except lo, WireGuard keepalive, and DHCP)
- **OUTPUT**: DROP on eth0 (except to WireGuard endpoint)
- **FORWARD**: DROP
- **OUTPUT on wg0**: ACCEPT (all VPN traffic)
## Quick Start
### Prerequisites
```bash
# Only requirement: Docker
# Docker handles all build tools and dependencies
docker --version
```
### Build ISO
```bash
# Build the Football installer ISO
./scripts/build-iso.sh
```
This creates:
- `output/football-installer.iso` - Bootable ISO with embedded preseed configuration
### Test ISO
```bash
# Test ISO by booting a VM
./scripts/test-iso.sh
```
This boots a 2GB RAM VM from the ISO, allowing you to test the installer before deploying.
### Deploy
#### Virtual Machine
The VM from `test-iso.sh` is ready for installation. Installer will:
- Auto-answer all questions except:
- Username creation
- User password (min 12 chars, mixed case, numbers, special chars)
- Root password (min 12 chars, mixed case, numbers, special chars)
- Target disk selection
#### Physical System
1. Write ISO to USB or disk:
```bash
sudo dd if=output/football-installer.iso of=/dev/sdX bs=4M status=progress
```
2. Boot system from USB
3. Installer will use embedded preseed to automate installation
4. Provide only:
- Username/password for user account
- Root password
- Target disk
3. Change default user password (`changeme`)
## Directory Structure
```
football/
├── build.sh # Main build script
├── config/
│ ├── packages.list # Minimal package list
│ ├── harden.sh # System hardening script
│ ├── secureboot.sh # Secure Boot configuration
│ └── setup-wireguard.sh # WireGuard setup script
├── chroot-overlay/ # Files copied to built system
│ ├── etc/
│ │ ├── systemd/system/ # Systemd services
│ │ ├── wireguard/ # WireGuard config templates
│ │ └── network/interfaces # Network configuration
│ └── home/user/ # User configuration
│ ├── .bashrc
│ ├── .xinitrc
│ ├── .icewm/preferences
│ └── Desktop/README.txt
└── output/ # Generated images (not in git)
```
## Security Features
### Hardening Measures
1. **Network Isolation**
- All inbound traffic blocked
- Only WireGuard traffic allowed on physical interface
- Mandatory VPN tunnel for all outbound traffic
2. **Service Restrictions**
- SSH server disabled and masked
- All remote access services removed
- Bluetooth disabled
- Unnecessary kernel modules disabled
3. **Secure Boot**
- GRUB locked with password protection
- Kernel lockdown mode enabled
- Signed bootloader (shim-signed)
- EFI variables write-protected
4. **Application Whitelisting**
- Only IceWM and Remmina installed
- No development tools
- Minimal command-line utilities
5. **System Hardening**
- AppArmor enforcing
- Fail2Ban enabled
- Auditd logging
- Core dumps disabled
- Strict umask (077)
### Firewall Rules (Detailed)
```bash
# IPv4 Rules
iptables -P INPUT DROP
iptables -P FORWARD DROP
iptables -P OUTPUT DROP
# Allow loopback
iptables -A INPUT -i lo -j ACCEPT
iptables -A OUTPUT -o lo -j ACCEPT
# Allow WireGuard to endpoint on eth0
iptables -A OUTPUT -o eth0 -d $WG_ENDPOINT_IP \
-p udp --dport $WG_ENDPOINT_PORT -j ACCEPT
iptables -A INPUT -i eth0 -s $WG_ENDPOINT_IP \
-p udp --sport $WG_ENDPOINT_PORT -j ACCEPT
# Allow DHCP on eth0
iptables -A OUTPUT -o eth0 -p udp --dport 67 -j ACCEPT
iptables -A INPUT -i eth0 -p udp --sport 67 -j ACCEPT
# Allow ALL traffic on WireGuard interface
iptables -A INPUT -i wg0 -j ACCEPT
iptables -A OUTPUT -o wg0 -j ACCEPT
```
## Usage
### Default User
- **Username**: `user`
- **Password**: `changeme` (CHANGE IMMEDIATELY!)
### Automatic Startup
1. Login triggers automatic IceWM start
2. Remmina launches automatically
3. WireGuard tunnel establishes automatically
4. Use Remmina to connect to PAW
### Remmina Configuration
Create Remmina profiles in:
- Path: `/home/user/.local/share/remmina/`
- Protocol: RDP or VNC (as needed)
- Server: PAW internal IP via WireGuard
### System Administration
**Local console access only:**
```bash
# Check WireGuard status
sudo wg show
# View firewall rules
sudo iptables -L -n -v
# Check logs
sudo journalctl -u wg-quick@wg0
sudo journalctl -u block-remote-access
```
## Troubleshooting
### WireGuard Connection Fails
1. Verify endpoint IP and port
2. Check firewall rules allow WireGuard
3. Verify keys are correctly configured
4. Check WireGuard server logs
### Network Blocked
1. Confirm WireGuard interface is up: `ip link show wg0`
2. Check firewall: `sudo iptables -L -n -v`
3. Verify WireGuard config: `sudo wg show`
### Secure Boot Issues
1. Ensure UEFI is enabled
2. Verify Microsoft UEFI CA is installed
3. Check Secure Boot status: `mokutil --sb-state`
### System Won't Boot
1. Verify UEFI boot mode (not legacy BIOS)
2. Check GRUB installation
3. Review kernel logs from boot
## Advanced Configuration
### Customizing the Build
Edit `config/packages.list` to add/remove packages
Modify `chroot-overlay/` to customize system files
### Changing Image Size
Edit `build.sh`:
```bash
DISK_SIZE_MB=8192 # Change to desired size in MB
```
### Multiple Deployment Profiles
Create different `build.sh` variants with different configurations for various deployment scenarios.
## Security Considerations
### Before Deployment
1. ✅ Generate unique WireGuard keys per deployment
2. ✅ Change default password
3. ✅ Verify Secure Boot configuration
4. ✅ Test WireGuard connection
5. ✅ Verify firewall rules
6. ✅ Configure PAW connection in Remmina
### During Operation
1. ✅ Monitor WireGuard connection
2. ✅ Review audit logs regularly
3. ✅ Keep system updated (manual, controlled updates)
4. ✅ Physical security of device
### Incident Response
If compromise suspected:
1. Isolate system physically
2. Preserve logs and memory dump
3. Contact security team
4. Destroy/rebuild system from scratch
## Compliance
This system is designed to support:
- NIST SP 800-171 controls
- NIST SP 800-53 Moderate
- CIS Benchmarks for Debian 13 (Trixie)
- CMMC Level 3 controls
- FedRAMP Moderate controls
- Zero Trust network architecture principles
- Privileged Access Management (PAM) best practices
## License
See LICENSE file.
## Support
For issues or questions:
- Contact: Infrastructure Security Team
- Location: KNEL server room
---
**WARNING**: This is a security-focused build system. Unauthorized modifications or deployments may compromise infrastructure security.

77
run.sh
View File

@@ -1,77 +0,0 @@
#!/bin/bash
# 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="knel-football-builder:latest"
readonly SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
readonly OUTPUT_DIR="${SCRIPT_DIR}/output"
# Create output directory if it doesn't exist
mkdir -p "${OUTPUT_DIR}"
# Function to show usage
usage() {
echo "Usage: $0 [command]"
echo "Commands:"
echo " build Build the secure ISO"
echo " test Run all tests"
echo " lint Run linting checks"
echo " clean Clean build artifacts"
echo " shell Interactive shell in build container"
exit 1
}
# Main execution logic
main() {
local command="${1:-build}"
case "${command}" in
build)
echo "Building KNEL-Football secure ISO..."
docker run --rm \
-v "${SCRIPT_DIR}:/workspace" \
-v "${OUTPUT_DIR}:/workspace/output" \
-u "$(id -u):$(id -g)" \
"${DOCKER_IMAGE}" \
/workspace/src/build-iso.sh
;;
test)
echo "Running KNEL-Football test suite..."
docker run --rm \
-v "${SCRIPT_DIR}:/workspace" \
-u "$(id -u):$(id -g)" \
"${DOCKER_IMAGE}" \
bats -r /workspace/tests/
;;
lint)
echo "Running linting checks..."
docker run --rm \
-v "${SCRIPT_DIR}:/workspace" \
-u "$(id -u):$(id -g)" \
"${DOCKER_IMAGE}" \
shellcheck /workspace/src/*.sh /workspace/config/hooks/*/*.sh
;;
clean)
echo "Cleaning build artifacts..."
rm -rf "${OUTPUT_DIR:?}"/*
;;
shell)
echo "Starting interactive shell..."
docker run --rm -it \
-v "${SCRIPT_DIR}:/workspace" \
-v "${OUTPUT_DIR}:/workspace/output" \
-u "$(id -u):$(id -g)" \
"${DOCKER_IMAGE}" \
bash
;;
*)
usage
;;
esac
}
main "$@"