From 6f50de798bc23b58913a84ebf192b3b23df72764 Mon Sep 17 00:00:00 2001 From: Peter Date: Wed, 16 Oct 2024 21:13:17 +0200 Subject: [PATCH] initial commit --- .gitignore | 1 + LICENSE | 661 +++++++++++++++++++++++++++ README.md | 7 + all.yml | 5 + ansible.cfg | 10 + group_vars/all/applications.yml | 35 ++ group_vars/all/firewall.yml | 7 + group_vars/all/ppm.yml | 1 + group_vars/all/rootuser.yml | 3 + inventory | 3 + roles/baseline/handlers/main.yml | 8 + roles/baseline/tasks/firewall.yml | 16 + roles/baseline/tasks/main.yml | 11 + roles/baseline/tasks/packages.yml | 47 ++ roles/baseline/tasks/rootuser.yml | 27 ++ roles/baseline/templates/firewall.j2 | 78 ++++ roles/baseline/templates/mosh.j2 | 6 + roles/ppm/handlers/main.yml | 3 + roles/ppm/tasks/copyappdef.yml | 43 ++ roles/ppm/tasks/main.yml | 19 + roles/ppm/tasks/oneapp.yml | 36 ++ roles/ppm/tasks/ppminstall.yml | 37 ++ roles/ppm/templates/ppmfirewall.j2 | 15 + run | 3 + 24 files changed, 1082 insertions(+) create mode 100644 .gitignore create mode 100644 LICENSE create mode 100644 README.md create mode 100644 all.yml create mode 100644 ansible.cfg create mode 100644 group_vars/all/applications.yml create mode 100644 group_vars/all/firewall.yml create mode 100644 group_vars/all/ppm.yml create mode 100644 group_vars/all/rootuser.yml create mode 100644 inventory create mode 100644 roles/baseline/handlers/main.yml create mode 100644 roles/baseline/tasks/firewall.yml create mode 100644 roles/baseline/tasks/main.yml create mode 100644 roles/baseline/tasks/packages.yml create mode 100644 roles/baseline/tasks/rootuser.yml create mode 100644 roles/baseline/templates/firewall.j2 create mode 100644 roles/baseline/templates/mosh.j2 create mode 100644 roles/ppm/handlers/main.yml create mode 100644 roles/ppm/tasks/copyappdef.yml create mode 100644 roles/ppm/tasks/main.yml create mode 100644 roles/ppm/tasks/oneapp.yml create mode 100644 roles/ppm/tasks/ppminstall.yml create mode 100644 roles/ppm/templates/ppmfirewall.j2 create mode 100755 run diff --git a/.gitignore b/.gitignore new file mode 100644 index 0000000..1cc3a2f --- /dev/null +++ b/.gitignore @@ -0,0 +1 @@ +passwords diff --git a/LICENSE b/LICENSE new file mode 100644 index 0000000..be3f7b2 --- /dev/null +++ b/LICENSE @@ -0,0 +1,661 @@ + 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, +our General Public Licenses are 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 our General Public Licenses protect your rights +with two steps: (1) assert copyright on the software, and (2) offer +you this License which gives you legal permission to copy, distribute +and/or modify the software. + + A secondary benefit of defending all users' freedom is that +improvements made in alternate versions of the program, if they +receive widespread use, become available for other developers to +incorporate. Many developers of free software are heartened and +encouraged by the resulting cooperation. However, in the case of +software used on network servers, this result may fail to come about. +The GNU General Public License permits making a modified version and +letting the public access it on a server without ever releasing its +source code to the public. + + The GNU Affero General Public License is designed specifically to +ensure that, in such cases, the modified source code becomes available +to the community. It requires the operator of a network server to +provide the source code of the modified version running there to the +users of that server. Therefore, public use of a modified version, on +a publicly accessible server, gives the public access to the source +code of the modified version. + + An older license, called the Affero General Public License and +published by Affero, was designed to accomplish similar goals. This is +a different license, not a version of the Affero GPL, but Affero has +released a new version of the Affero GPL which permits relicensing under +this license. + + 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 it. + + 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 + written offer to provide the Corresponding Source. This + alternative is allowed only occasionally and noncommercially, and + only if you received the object code with such an offer, in accord + with subsection 6b. + + 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 object code work. + + 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 dwelling. 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 the 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 the +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 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 was 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 it 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. Remote Network Interaction; Use with the GNU General Public License. + + Notwithstanding any other provision of this License, if you modify the +Program, your modified version must prominently offer all users +interacting with it remotely through a computer network (if your version +supports such interaction) an opportunity to receive the Corresponding +Source of your version by providing access to the Corresponding Source +from a network server at no charge, through some standard or customary +means of facilitating copying of software. This Corresponding Source +shall include the Corresponding Source for any work covered by version 3 +of the GNU General Public License that is incorporated pursuant to the +following paragraph. + + 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 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 work with which it is combined will remain governed by version +3 of the GNU General Public License. + + 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 your software can interact with users remotely through a computer +network, you should also make sure that it provides a way for users to +get its source. For example, if your program is a web application, its +interface could display a "Source" link that leads users to an archive +of the code. There are many ways you could offer source, and different +solutions will be better for different programs; see section 13 for the +specific requirements. + + You should also get your employer (if you work as a programmer) or school, +if any, to sign a "copyright disclaimer" for the program, if necessary. +For more information on this, and how to apply and follow the GNU AGPL, see +. diff --git a/README.md b/README.md new file mode 100644 index 0000000..00877d8 --- /dev/null +++ b/README.md @@ -0,0 +1,7 @@ +This is how I set up ppm.pfoe.be + +This repository is currently created to serve +as an inspiration for creating your own ansible playbook to set up ppm + +At this moment it is not intended to be used as is/it is a work in progress + diff --git a/all.yml b/all.yml new file mode 100644 index 0000000..1519f04 --- /dev/null +++ b/all.yml @@ -0,0 +1,5 @@ +- name: Perform ppm server ansible playbook + hosts: all + roles: + - baseline + - ppm diff --git a/ansible.cfg b/ansible.cfg new file mode 100644 index 0000000..87040d1 --- /dev/null +++ b/ansible.cfg @@ -0,0 +1,10 @@ +[defaults] +inventory=inventory +retry_files_enabled = False +remote_user = root +ansible_managed = DO NOT MODIFY: this file is managed by ansible! +deperaction_warnings = True +display_skipped_hosts = True + +stdout_callback = yaml +stderr_callback = yaml diff --git a/group_vars/all/applications.yml b/group_vars/all/applications.yml new file mode 100644 index 0000000..90ddcc4 --- /dev/null +++ b/group_vars/all/applications.yml @@ -0,0 +1,35 @@ +ppm_apps: + - on_server: ppm.pfoe.be + user: git + chicken_egg_appdefinition: ../forgejo/ + appconfig: + code: + type: localfiles + directory: forgejo + restic: + url: "{{ lookup('file', 'passwords/ppm-forgejo-url') }}" + password: "{{ lookup('file', 'passwords/ppm-forgejo-password') }}" + backupname: "{{ lookup('file', 'passwords/ppm-forgejo-name') }}" + config: + publicurl: ppm.pfoe.be + + - on_server: ppm.pfoe.be + user: nginx + chicken_egg_appdefinition: ../nginx/ + firewall_redirect: + - from: 8080 + to: 80 + - from: 8443 + to: 443 + appconfig: + code: + type: localfiles + directory: nginx + + - on_server: ppm.pfoe.be + user: runner + chicken_egg_appdefinition: ../forgejo-runner/ + appconfig: + code: + type: localfiles + directory: forgejo-runner diff --git a/group_vars/all/firewall.yml b/group_vars/all/firewall.yml new file mode 100644 index 0000000..b2a76b1 --- /dev/null +++ b/group_vars/all/firewall.yml @@ -0,0 +1,7 @@ +# I prefer not to share the list of admins in a public repo, so refer to passwords... +# The format for the ssh ranges is as follows: +# - name: The name that is in a comment in the generated file. Not used anywhere else +# type: ipv4 # or ipv6 +# range: 10.10.10.10/32 # The range, MUST be a valid range, not an ip address, ie there must be a / and the netmask + +firewall_ssh_ranges: "{{ lookup('file', 'passwords/firewall_ssh_ranges.yml') | from_yaml }}" diff --git a/group_vars/all/ppm.yml b/group_vars/all/ppm.yml new file mode 100644 index 0000000..b540407 --- /dev/null +++ b/group_vars/all/ppm.yml @@ -0,0 +1 @@ +ppm_binary: "{{ lookup('pipe', 'pwd') }}/../ppm/out/ppm" diff --git a/group_vars/all/rootuser.yml b/group_vars/all/rootuser.yml new file mode 100644 index 0000000..5fa38f4 --- /dev/null +++ b/group_vars/all/rootuser.yml @@ -0,0 +1,3 @@ +root_password: "{{ lookup('file', 'passwords/root_password_hashed') }}" +# ssh keys are public, but I prefer not to share the list of admins in a public repo +root_sshkeys: "{{ lookup('file', 'passwords/root_sshkeys.yml') | from_yaml }}" diff --git a/inventory b/inventory new file mode 100644 index 0000000..9af821e --- /dev/null +++ b/inventory @@ -0,0 +1,3 @@ +[ppmserver] +ppm.pfoe.be + diff --git a/roles/baseline/handlers/main.yml b/roles/baseline/handlers/main.yml new file mode 100644 index 0000000..5ceb761 --- /dev/null +++ b/roles/baseline/handlers/main.yml @@ -0,0 +1,8 @@ +- name: Restart firewall + ansible.builtin.command: /etc/network/if-pre-up.d/firewall + changed_when: true + +- name: Restart sshd + ansible.builtin.systemd: + name: ssh + state: restarted diff --git a/roles/baseline/tasks/firewall.yml b/roles/baseline/tasks/firewall.yml new file mode 100644 index 0000000..e5ad359 --- /dev/null +++ b/roles/baseline/tasks/firewall.yml @@ -0,0 +1,16 @@ +- name: Directory for firewall parts + ansible.builtin.file: + group: root + owner: root + name: /etc/firewall.d/ + mode: "0700" + state: directory + +- name: Firewall template + ansible.builtin.template: + dest: /etc/network/if-pre-up.d/firewall + group: root + owner: root + mode: "0755" + src: firewall.j2 + notify: Restart firewall diff --git a/roles/baseline/tasks/main.yml b/roles/baseline/tasks/main.yml new file mode 100644 index 0000000..3b3a112 --- /dev/null +++ b/roles/baseline/tasks/main.yml @@ -0,0 +1,11 @@ +- name: Manage apt packages + ansible.builtin.import_tasks: packages.yml + +- name: Manage global firewall + ansible.builtin.import_tasks: firewall.yml + +- name: Manage root user + ansible.builtin.import_tasks: rootuser.yml + +- name: Ensure handlers have ran + ansible.builtin.meta: flush_handlers diff --git a/roles/baseline/tasks/packages.yml b/roles/baseline/tasks/packages.yml new file mode 100644 index 0000000..88dfd11 --- /dev/null +++ b/roles/baseline/tasks/packages.yml @@ -0,0 +1,47 @@ +- name: Keep apt repository list uptodate + ansible.builtin.apt: + update_cache: true + cache_valid_time: 3600 + # Even if we "changed it", it's merely a cache, so ignore + changed_when: false + +- name: Update system packages to lates + ansible.builtin.apt: + upgrade: dist + +- name: Remove unused packages + ansible.builtin.apt: + autoremove: true + +# The following is a list of utilities that I personally use +# to make my life easier. It is opiniated and not needed... +- name: Install utilities to make life easier + ansible.builtin.apt: + pkg: + - apt-dater + - mosh + - mc + - vim + - curl + - jq + - host + - telnet + - screen + - tmux + - tcpdump + - sqlite3 + - bash-completion + - mtr-tiny + - iotop + - iftop + - htop + - ncdu + +- name: Firewall for mosh + ansible.builtin.template: + dest: /etc/firewall.d/mosh + group: root + owner: root + mode: "0755" + src: mosh.j2 + notify: Restart firewall diff --git a/roles/baseline/tasks/rootuser.yml b/roles/baseline/tasks/rootuser.yml new file mode 100644 index 0000000..854a42c --- /dev/null +++ b/roles/baseline/tasks/rootuser.yml @@ -0,0 +1,27 @@ +- name: Set root password + ansible.builtin.user: + name: root + password: "{{ root_password }}" + +- name: Ensure ssh directory for root + ansible.builtin.file: + state: directory + path: /root/.ssh + owner: root + group: root + mode: "0700" + +- name: Set authorized keys for root + ansible.builtin.copy: + content: "{{ root_sshkeys | join('\n') }}" + dest: /root/.ssh/authorized_keys + owner: root + group: root + mode: "0600" + +- name: Only allow root ssh + ansible.builtin.lineinfile: + dest: /etc/ssh/sshd_config + line: "PermitRootLogin prohibit-password" + regexp: "^PermitRootLogin " + notify: Restart sshd diff --git a/roles/baseline/templates/firewall.j2 b/roles/baseline/templates/firewall.j2 new file mode 100644 index 0000000..dac129b --- /dev/null +++ b/roles/baseline/templates/firewall.j2 @@ -0,0 +1,78 @@ +#!/bin/bash +# {{ ansible_managed }} + +# IPv4: +iptables -F +iptables -X +iptables -t mangle -F +iptables -t mangle -X +iptables -t nat -F +iptables -t nat -X + +iptables -P INPUT ACCEPT +iptables -P OUTPUT ACCEPT +iptables -P FORWARD ACCEPT + +iptables -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT +iptables -A INPUT -m state --state INVALID -j DROP +iptables -A INPUT -i lo -j ACCEPT +iptables -A INPUT -m limit --limit 1/s --limit-burst 2 -p icmp --icmp-type echo-request -j ACCEPT +iptables -A INPUT -p icmp --icmp-type echo-request -j DROP +iptables -A INPUT -p icmp -j ACCEPT + +{% for range in firewall_ssh_ranges %} +{%if range.type=="ipv4" %} +iptables -A INPUT -p tcp --dport 22 -s {{range.range}} -j ACCEPT # {{range.name}} +{%endif%} +{%endfor%} + +iptables -A OUTPUT -m state --state ESTABLISHED,RELATED -j ACCEPT +iptables -A OUTPUT -m state --state INVALID -j DROP + +# IPv6: +ip6tables -F +ip6tables -X +ip6tables -t mangle -F +ip6tables -t mangle -X +ip6tables -t nat -F +ip6tables -t nat -X + +ip6tables -P INPUT ACCEPT +ip6tables -P OUTPUT ACCEPT +ip6tables -P FORWARD ACCEPT + +ip6tables -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT +ip6tables -A INPUT -m state --state INVALID -j DROP +ip6tables -A INPUT -i lo -j ACCEPT +ip6tables -A INPUT -m limit --limit 1/s --limit-burst 2 -p icmpv6 --icmpv6-type echo-request -j ACCEPT +ip6tables -A INPUT -p icmpv6 --icmpv6-type echo-request -j DROP +ip6tables -A INPUT -p icmpv6 -j ACCEPT + +{% for range in firewall_ssh_ranges %} +{%if range.type=="ipv6" %} +ip6tables -A INPUT -p tcp --dport 22 -s {{range.range}} -j ACCEPT # {{range.name}} +{%endif%} +{%endfor%} + +ip6tables -A OUTPUT -m state --state ESTABLISHED,RELATED -j ACCEPT +ip6tables -A OUTPUT -m state --state INVALID -j DROP + + +# Disable all forwarding +echo 0 > /proc/sys/net/ipv4/ip_forward +echo 0 > /proc/sys/net/ipv6/conf/all/forwarding + +# Customisation: +{# we use run-parts as it guarantees order and ignores backups etc. We use --list as it would otherwise run them concurently, causing iptables to exit with EAGAIN as changing the firewall is not possible by 2 prococesses #} +for i in $(run-parts --list /etc/firewall.d/) +do + $i +done + +# Finish off with a block +iptables -A INPUT -j REJECT +ip6tables -A INPUT -j REJECT +iptables -A FORWARD -j REJECT +ip6tables -A FORWARD -j REJECT + +# {{ansible_managed}} diff --git a/roles/baseline/templates/mosh.j2 b/roles/baseline/templates/mosh.j2 new file mode 100644 index 0000000..379a7ba --- /dev/null +++ b/roles/baseline/templates/mosh.j2 @@ -0,0 +1,6 @@ +#!/bin/sh +# {{ansible_managed}} +# Firewall to allow mosh sessions + +ip6tables -A INPUT -p udp --match multiport --dports 60001:60020 -j ACCEPT +iptables -A INPUT -p udp --match multiport --dports 60001:60020 -j ACCEPT diff --git a/roles/ppm/handlers/main.yml b/roles/ppm/handlers/main.yml new file mode 100644 index 0000000..f64b418 --- /dev/null +++ b/roles/ppm/handlers/main.yml @@ -0,0 +1,3 @@ +- name: Restart firewall + ansible.builtin.command: /etc/network/if-pre-up.d/firewall + changed_when: true diff --git a/roles/ppm/tasks/copyappdef.yml b/roles/ppm/tasks/copyappdef.yml new file mode 100644 index 0000000..695f5ab --- /dev/null +++ b/roles/ppm/tasks/copyappdef.yml @@ -0,0 +1,43 @@ +# The chicken-egg should not be used. I use ppm to setup ppm.pfoe.be +# so I cannot clone the appdefinition using git. So this chicken-egg +# makes it possible to install apps when I'm still installing ppm.pfoe.be +# However, it's easier to just git clone directly from the source. +# You will need a local copy of the git repository to use this + +- name: Create temporary build directory + ansible.builtin.tempfile: + state: directory + suffix: build + register: temp_dir + delegate_to: localhost + become: false + +- name: Create a .tar.gz archive from the chicken-egg directory + community.general.archive: + dest: "{{ temp_dir.path }}/appdef.tar.gz" + path: "{{ ppm_app.chicken_egg_appdefinition }}" + mode: "0600" + delegate_to: localhost + become: false + +- name: Create directory + ansible.builtin.file: + path: "{{ ppm_app_user.home }}/appdefinition" + state: directory + mode: "0755" + owner: "{{ ppm_app_user.name }}" + group: "{{ ppm_app_user.group }}" + +- name: Unzip the files to server + ansible.builtin.unarchive: + src: "{{ temp_dir.path }}/appdef.tar.gz" + dest: "{{ ppm_app_user.home }}/appdefinition" + owner: "{{ ppm_app_user.name }}" + group: "{{ ppm_app_user.group }}" + +- name: Remove temp dir + ansible.builtin.file: + path: "{{ temp_dir.path }}" + state: absent + delegate_to: localhost + become: false diff --git a/roles/ppm/tasks/main.yml b/roles/ppm/tasks/main.yml new file mode 100644 index 0000000..b6acf32 --- /dev/null +++ b/roles/ppm/tasks/main.yml @@ -0,0 +1,19 @@ +- name: Install PPM program as root + ansible.builtin.import_tasks: ppminstall.yml + +- name: Go over all projects for this server + ansible.builtin.include_tasks: oneapp.yml + loop: "{{ ppm_apps }}" + loop_control: + loop_var: ppm_app + label: "{{ ppm_app.user }}" + when: ppm_app.on_server == inventory_hostname + +- name: Configure firewall options + ansible.builtin.template: + dest: /etc/firewall.d/ppmfirewall + group: root + owner: root + mode: "0755" + src: ppmfirewall.j2 + notify: Restart firewall diff --git a/roles/ppm/tasks/oneapp.yml b/roles/ppm/tasks/oneapp.yml new file mode 100644 index 0000000..77e4dc9 --- /dev/null +++ b/roles/ppm/tasks/oneapp.yml @@ -0,0 +1,36 @@ +- name: "Create user ({{ ppm_app.user }})" + ansible.builtin.user: + name: "{{ ppm_app.user }}" + shell: /bin/bash + register: ppm_app_user + +# Enabling linger will make systemd start the user-systemd for this user at bootup time +# Enabling this will allow us to run programs automatically and independently of any user login +- name: "Linger user ({{ ppm_app.user }})" + ansible.builtin.command: + cmd: "loginctl enable-linger {{ ppm_app_user.name }}" + creates: "/var/lib/systemd/linger/{{ ppm_app_user.name }}" + +- name: "Ensure we have a XDG_RUNTIME_DIR variable ({{ ppm_app.user }})" + ansible.builtin.lineinfile: + dest: "{{ ppm_app_user.home }}/.bashrc" + state: present + line: "export XDG_RUNTIME_DIR=/run/user/$(id -u)" + regexp: ^export XDG_RUNTIME_DIR= + +- name: "Place configuration ({{ ppm_app.user }})" + ansible.builtin.copy: + content: "{{ ppm_app.appconfig | dict2items | selectattr('key', 'ne', 'code') | items2dict | to_nice_yaml }}" + dest: "{{ ppm_app_user.home }}/config.yml" + owner: "{{ ppm_app_user.name }}" + group: "{{ ppm_app_user.group }}" + mode: "0600" + +- name: "See if app definition exists ({{ ppm_app.user }})" + ansible.builtin.stat: + path: "{{ ppm_app_user.home }}/appdefinition" + register: appdefinition + +- name: "Bootstrap the app definition ({{ ppm_app.user }})" + ansible.builtin.include_tasks: copyappdef.yml + when: ppm_app.chicken_egg_appdefinition is defined and not appdefinition.stat.exists diff --git a/roles/ppm/tasks/ppminstall.yml b/roles/ppm/tasks/ppminstall.yml new file mode 100644 index 0000000..3619992 --- /dev/null +++ b/roles/ppm/tasks/ppminstall.yml @@ -0,0 +1,37 @@ +- name: Install ppm dependencies + ansible.builtin.apt: + pkg: + # We hard depend on podman, as this is the workhorse of most apps + # We also depend on podman unshare in ppm itself + - podman + # Required for rootless operation + - uidmap + # Use the newer network backend instead of the default CNI backend + - netavark + # Required for rootless networking + - slirp4netns + # podman-compose is also used in many apps we can install + - podman-compose + # Restic is currently the only supported backup system + - restic + # The python dependencies of ppm are baked in. However, jsonschema is + # not pure python, so it must be installed from system package + - python3-jsonschema + # Git is required for checking out the app definitions + - git + +- name: Create state directory + ansible.builtin.file: + state: directory + owner: root + group: root + mode: "1777" + path: /home/.ppmstate + +- name: Copy ppm + ansible.builtin.copy: + src: "{{ ppm_binary }}" + dest: /usr/local/bin/ppm + owner: root + group: root + mode: "0755" diff --git a/roles/ppm/templates/ppmfirewall.j2 b/roles/ppm/templates/ppmfirewall.j2 new file mode 100644 index 0000000..efee383 --- /dev/null +++ b/roles/ppm/templates/ppmfirewall.j2 @@ -0,0 +1,15 @@ +#!/bin/bash + +# PPM Firewal, written by ansible + +{% for ppm_app in ppm_apps %} +# Firewall for {{ ppm_app.user }} +{% for redirect in ppm_app.firewall_redirect | default([]) %} +# Redirect {{ redirect.from }} to {{ redirect.to }} +iptables -A INPUT -p tcp --dport {{ redirect.from }} -j ACCEPT +ip6tables -A INPUT -p tcp --dport {{ redirect.from }} -j ACCEPT +iptables -t nat -A PREROUTING -p tcp --dport {{ redirect.to }} -j REDIRECT --to-ports {{ redirect.from }} +ip6tables -t nat -A PREROUTING -p tcp --dport {{ redirect.to }} -j REDIRECT --to-ports {{ redirect.from }} +{% endfor %} + +{% endfor %} diff --git a/run b/run new file mode 100755 index 0000000..e26716e --- /dev/null +++ b/run @@ -0,0 +1,3 @@ +#!/bin/sh + +ansible-playbook --diff all.yml "$@"