├── images └── web_interface.png ├── Application_template.md ├── Ideas.md ├── Contributer_guide.md ├── README.md └── LICENSE /images/web_interface.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/pappukumar35/Google-Summer-of-Code-2023/HEAD/images/web_interface.png -------------------------------------------------------------------------------- /Application_template.md: -------------------------------------------------------------------------------- 1 | # GSoC Application Template 2 | 3 | Please send this application by email to stratosphere@aic.fel.cvut.cz 4 | 5 | ## Your Background 6 | 7 | Your Name: 8 | 9 | Discord Username: 10 | 11 | Email Address: 12 | 13 | Primary Spoken Language: 14 | 15 | Project you're interested in: (Slips or AIP) 16 | 17 | Linkedin Profile: 18 | 19 | Github Profile: 20 | 21 | 22 | #### 1. Please describe your preferred coding languages and experience. 23 | 24 | #### 2. Please describe your background on the following topics: Security, Networks, Machine Learning 25 | 26 | #### 3. Please describe any previous open source development experience. 27 | 28 | (we expect most students to leave this section blank) 29 | 30 | #### 4. What school do you attend and what is your specialty/major at the school? 31 | 32 | #### 5. How many years have you attended there? 33 | 34 | #### 6. What city/country will you be spending this summer in? What's your timezone? 35 | 36 | #### 7. How much time do you expect to have for this project? 37 | 38 | #### 8. Please list all jobs, summer classes, vacations, exams, and/or other commitments that you'll need to work around during GSoC. 39 | 40 | #### 9. Have you participated in any previous Summer of Code project? If so please describe your project and your experience. 41 | 42 | #### 10. Have you applied for (or intend to apply for) any other GSoC 2023: projects? If so, which ones? 43 | 44 | #### 11. If you have a URL for your resume/CV, please list it here. 45 | 46 | #### 12. If you wish to list any personal/blog URLs, do so here. 47 | 48 | #### 13. Project Plan 49 | 50 | Please describe your proposed project in detail, including deliverables and expected timeline with milestones (this is the long answer, so spend most time here!). 51 | -------------------------------------------------------------------------------- /Ideas.md: -------------------------------------------------------------------------------- 1 | # Slips 2 | 3 | ## Improvement of Slips web interface 4 | - Better Display of timewindow numbers, start time, and end time 5 | - Showing all the info we have on each profile. 6 | - Show a list of Blocked Profiles in one place 7 | - Show the history of threat levels and confidence of each profile 8 | - If an IPv4 profile has an available IPv6 we should show it. and vice versa 9 | - Show the current threat level of each profile 10 | - Show the user agent of each profile 11 | - Show the MAC of each profile 12 | - Live (Asynchronous) updating of the web view. (meaning that without refreshing the page, new info should be displayed) 13 | - Show slips logo somewhere 14 | - Showing about a profile 15 | - Progress bar if possible 16 | - List of loaded modules and disabled modules 17 | - Show current model status (are we in training or testing mode) 18 | - Show the current gateway’s IP and MAC, an mark the gateway profile as ‘Gateway’ 19 | - Have a whitelist tab to show what IPs/domains/orgs are currently whitelisted 20 | - Manage the configuration of slips from the web 21 | - Change the feeds : JA3 feeds, SSL feeds, TI feeds 22 | - Whitelist 23 | - Manage API keys: VT, riskIQ, slack bot token 24 | - Warden.conf 25 | - Slips.conf 26 | - Local TI files 27 | 28 | ## Better Installation and usage 29 | 30 | - An easy way to install slips, Any of the following: 31 | - using apt 32 | - snap 33 | - dpkg 34 | - Now slips runs from it's main directory, after installing it using apt the goal would be to use slips from any directory, so this would require changing slips code to use relative directories, adding slips to PATH etc. 35 | - Support auto starting slips daemon on startup 36 | - Bonus: brew installation of slips (if the student has a macOS) 37 | 38 | ## Improve Performance 39 | 40 | - CPU Profiling; Using python profilers: for example profile and cProfile modules or others 41 | - Memory Profiling; Using memray, Memory Profiler module or others that may do 42 | - Provide statistics and graphs about which parts or modules of slips need optimizations 43 | - Provide optimization ideas; what can be done differently? Why and How? 44 | 45 | 46 | -------------------------------------------------------------------------------- /Contributer_guide.md: -------------------------------------------------------------------------------- 1 | 2 | 3 | ## What we expect from you 4 | 5 | We expect you to get motivated by the projects and to get involved in how to make them better! 6 | 7 | You will have to work around 4hs per day (small projects) to 6hs per day (large project), during 12 weeks (22 weeks max if we agree). 8 | 9 | We can agree in your time off, and holidays and how to better work with us. 10 | 11 | To get approved in your work during the summer you will be required to present a report 12 | and Google will ask us an evaluation of your work. This will happen twice during the summer. 13 | 14 | 15 | If you want to work on an issue from the slips repo, we highly encourage you to do so as a form of contributing and it will give you a higher chance of being accepted. but tasks from slips issues are going to be outside the GSoC. for GSoC 2023 we will stick to the 3 Ideas in our ideas list. 16 | 17 | Since we got many questions about the evaluation, the following points would greatly affect your ranking: 18 | 19 | 20 | - Early bird gets the worm! Send us your proposals early, maybe before 21 | sending them to Google. the earlier the better. 22 | - In your application, tell us which idea you want to work on, you can 23 | choose one of the 3 ideas in our ideas list. also if you have a 24 | really great idea that is worth 3 months of implementation we would 25 | love to hear about it! 26 | - Tell us in detail how you're planning to implement the idea you 27 | chose. divide it into smaller tasks, tell us the technologies you're 28 | going to use, and tell us if you've done something similar before. 29 | - Purpose initial milestones, we will plan it in more detail later if 30 | you're accepted, but we would like to know how you estimate each task 31 | and plan the timeline. 32 | - Show us your skills and experience, links to side projects would be 33 | great, and demonstrating your skills by fixing small issues from the 34 | slips repo would greatly affect your ranking. 35 | 36 | 37 | Remember that showing us your skills is way better than listing them 😉 38 | 39 | Feel free to reach out with any questions or concerns, we are here for you! 40 | 41 | ## Application template 42 | 43 | For students applying to one of Stratosphere projects, you can fill the below form and send it to us 44 | 45 | https://github.com/stratosphereips/Google-Summer-of-Code-2023/blob/main/Application_template.md 46 | 47 | 48 | We may update the ideas list later so keep an eye on it 49 | 50 | ## Communication 51 | 52 | Feel free to reach out to us, Use our [Discord](https://discord.gg/zu5HwMFy5C) (slips channel) and 53 | [GitHub](https://github.com/stratosphereips/StratosphereLinuxIPS/) channels to contact us and to ask questions. 54 | 55 | We will be in permanent contact, but we will have from 1 to 3 meetings per week to guide you on what to do. 56 | 57 | 58 | 59 | 60 | 61 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 |

2 | Logo 3 |

4 | 5 | 6 | 7 | # Stratosphere Google Summer of Code 2023 8 | This is the repository with all the information you need to know about the Google Summer of Code for Stratosphere Laboratory 2023 9 | 10 | ## About the Stratosphere Laboratory 11 | Stratosphere conducts research at the intersection of machine learning, cybersecurity and helping others by developing free software tools. We are part of the Artificial Intelligence Center, Faculty of Electrical Engineering, Czech Technical University in Prague. Stratosphere is an official organization in the Google Summer of Code 2023. 12 | 13 | ## Google Summer of Code 14 | The [Google Summer of Code](https://summerofcode.withgoogle.com/) is a global, online program focused on bringing new contributors into open source software development. GSoC Contributors work with an open source organization on a 12+ week programming project under the guidance of mentors. 15 | 16 | 17 | # Projects you can contribute for Stratosphere 18 | 1. Slips (Stratosphere Linux IPS) 19 | 2. Attacker IP Threat Intelligence Framework (AIP) 20 | 21 | # Communication 22 | We strongly suggest that you go to our public Discord and talk to us there to start discussing your own ideas on what to work on and make us questions. Go here to [Discord](https://discord.gg/zu5HwMFy5C). 23 | 24 | # Project Slips (Stratosphere Linux IPS) 25 | 26 | ### Description of Slips 27 | Slips is a behavioral intrusion prevention system that uses machine learning to detect malicious behaviors in network traffic. Slips focus on targeted attacks, detection of command and control channels, and providing a good visualization for the analyst. It can analyze network traffic in real-time, network captures such as pcap files, and network flows produced by Suricata, Zeek/Bro, and Argus. Slips processes the input data, analyzes it, and highlights suspicious behavior that needs the analyst's attention. 28 | 29 | Slips is full of features and crazy ideas, detection methods, databases, machine learning and many many more (including a P2P detection system!). So get to know the project, try it, and come up with your own ideas. 30 | 31 | ### Project Link: 32 | https://github.com/stratosphereips/StratosphereLinuxIPS 33 | 34 | 35 | ## 🧑🏽‍💻 Work Idea 1: Improvement of Slips web interface 36 | 37 | This idea consist in taking the current web page of Slips and implement a set of medium to advanced features to make it better. 38 | 39 | #### Proposed lists of topics that could be included: 40 | 41 | - Adapting the web interface to show all the information Slips has on each profile (connections, attacks, detections, etc.) 42 | - Manage the complete configuration of slips from the web. 43 | - Add graphs for continuous visualization of traffic 44 | - Add explanations for alerts, evidences and flows. 45 | 46 | ### Expected size of work 47 | 175 (4hs per day for 12 weeks) 48 | 49 | ### Expected length of project 50 | 10-22 weeks 51 | 52 | ### Difficulty 53 | Medium 54 | 55 | **Detail of the tasks description**: https://github.com/stratosphereips/Google-Summer-of-Code-2023/blob/main/Ideas.md#improvement-of-slips-web-interface 56 | 57 | **Mentor**: [Sebastian Garcia](https://github.com/eldraco) 58 | 59 | **Technology**: JavaScript, JQuery, flask, Python 60 | 61 | **Current status**: There is a working web interface 62 | 63 | 64 | 65 | --- 66 | 67 | ## 🧑🏽‍💻 Slips idea 2: Better Installation 68 | 69 | Slips has a hard time being installed in many systems given its dependencies to many tools and to TensorFlow framework. Help Slips being easier to install and use! 70 | 71 | #### Proposed lists of topics that could be included: 72 | 73 | - An easy way to install slips in many systems: Linux, Macos, Windows, Rpi, etc. 74 | - Make packages for some Linux systems, Debian, Ubuntu, Fedora 75 | - Make a brew package of slips 76 | 77 | **Details of the tasks**: https://github.com/stratosphereips/Google-Summer-of-Code-2023/blob/main/Ideas.md#better-installation 78 | 79 | **Mentor**: [Alya Gomaa](https://github.com/AlyaGomaa) 80 | 81 | **Current status**: Slips is working in docker, and can be installed locally using install.sh and conda/pip. 82 | 83 | **Technology**: python, package management, brew 84 | 85 | --- 86 | 87 | ### 🧑🏽‍💻 Slips idea 3: Improving Performance 88 | Slips wants to do many detections in your network, but that requires CPU, memory and sometimes GPU for the machine learning. This idea is to help Slips improve its performance by consuming less CPU and memory for its detections. Goal: to make Slips be able to work continusly in a large network. 89 | 90 | #### Proposed lists of topics that could be included: 91 | 92 | - CPU usage profiling 93 | - Memory usage profiling 94 | - Provide statistics and graphs about which parts or modules of slips need optimizations 95 | - Provide optimization ideas 96 | 97 | **Detailed tasks**: https://github.com/stratosphereips/Google-Summer-of-Code-2023/blob/main/Ideas.md#improve-performance 98 | 99 | **Mentor**: [Alya Gomaa](https://github.com/AlyaGomaa) 100 | 101 | **Current status**: basic previous work in this area 102 | 103 | **Technology**: Python, profiling tools 104 | 105 | 106 | --- 107 |
108 |
109 | 110 | 111 | # Project Attacker IP Prioritization Framework (AIP) 112 | ## Description of AIP 113 | AIP is a framework to design, create and evaluate the performance of Threat Intelligence lists. The current most used protection mechanism in our security community are threat intelligence feeds, but there is no clear understanding of which ones are best, why they are best, which ones do not work and how to evaluate them. More importantly, there was no framework to create new models that output TI feeds. AIP allows anyone to create their own lists and compare their performance with public lists. Stratosphere Laboratory has its own honeypots and we use the AIP framework to create new blocklists for the community every day. 114 | 115 | ### Project Link: https://github.com/stratosphereips/AIP 116 | 117 | ## 💻 AIP Idea 1: AIP Web User Interface (AIP-WebUI) 118 | ### Description 119 | Create a web application to display and manage the information produced by the tool. People running AIP and generating lists will use the AIP-WebUI to publish their lists in a user-friendly way. 120 | 121 | The main page will show a logo, a general project description, and a query form. The logo and the description of the project should be customizable. The query form will receive an IP and show the lists in which the IP appears. A checkbox will allow querying the IP in all the historical blocklists generated by AIP. 122 | 123 | AIP Tool produces several types of blocklists, depending on different models. We will evaluate the proposals about the best way to show a summary of each list that will include at least the following: 124 | 125 | * A description of the algorithm generating the list: Propose a method for AIP Tool to make this information available so AIP-WebUI can add new models and blocklists transparently. 126 | 127 | * A plot with the metrics: AIP Tool provides a .csv file with metrics. The AIP-WebUI tool will consume it to create and show the graphs. 128 | 129 | * Ten Top-ranked attackers (if applicable): Some models generate blocklists with a ranking. For those models, the AIP-WebUI application will show the top-ranked IPs.  130 | 131 | The number of different blocklists depends on the AIP Tool configuration. If new models become available, the AIP-WebUI should be flexible and add the new blocklists automatically.  132 | 133 | The application must include a REST/API endpoint to query if an IP is in a list. 134 | 135 | **Extra pointsi**: bulk query of IPs.  136 | 137 | **Extra points**: Include a Dark/Light theme switch. 138 | 139 | ### Note for wannabe contributors: 140 | 141 | This Idea states some of the requirements for the AIP-WebUI and its integration with the AIP Tool. You may have other ideas we want to hear. Explain them clearly in your proposal and include a paragraph detailing how your idea will improve the project if followed. Also, include information about your assumptions for your idea to work. For example: "To load the top-ranked attackers properly, the blocklist must include a column named 'rank'". 142 | 143 | Follow the guidelines described here to write the proposals: https://google.github.io/gsocguides/student/writing-a-proposal. Pay special attention to the "deliverables" section. 144 | 145 | Submit your proposal drafts to the #aip channel in discord. We suggest a Google Docs read-only link for which a mentor will ask permissions to make comments with a personal email address. 146 | 147 | **Mentor**: [Joaquin Bogado](https://github.com/jwackito/) 148 | 149 | **Current status**: Beta Testing 150 | 151 | **Technology**: Python, Flask 152 | 153 | ## Expected size 154 | 175 (4hs per day for 12 weeks) 155 | 156 | ## Expected length of project 157 | 10-22 weeks 158 | 159 | ## Difficulty 160 | Medium 161 | 162 | 163 | ## 💻 AIP Idea 2: Continuous Deployment 164 | 165 | This idea is to have the AIP framework being continually integrated to the network and honeypots and to produce results and information about the different TI feeds downloaded. It is not about how to show the information, but how to produce it. 166 | 167 | **Mentor**: [Joaquin Bogado](https://github.com/jwackito/) 168 | 169 | **Current status**: Beta Testing 170 | 171 | **Technology**: Python 172 | 173 | --- 174 | 175 | ## What we expect from you 176 | We expect you to get motivated by the projects and to get involved in how to make them better! You will have to work around 4hs per day (small projects) to 6hs per day (large project), during 12 weeks (22 weeks max if we agree). We can agree in your time off, and holidays and how to better work with us. 177 | 178 | To get approved in your work during the summer you will be required to present a report and Google will ask us an evaluation of your work. This will happen twice during the summer. 179 | 180 | ## Application template (for students) 181 | 182 | For students applying to one of Stratosphere projects, you can fill the below form and send it to us to stratosphere@aic.fel.cvut.cz 183 | 184 | https://github.com/stratosphereips/Google-Summer-of-Code-2023/blob/main/Application_template.md 185 | 186 | ## Communication 187 | 188 | It is very important that you keep communicated with us. Use our [Discord](https://discord.gg/zu5HwMFy5C) (slips channel) and [GitHub](https://github.com/stratosphereips/StratosphereLinuxIPS/) channels to contact us and to ask questions. 189 | 190 | We will be in permanent contact, but we will have from 1 to 3 meetings per week to guide you on what to do. 191 | 192 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | GNU GENERAL PUBLIC LICENSE 2 | Version 2, June 1991 3 | 4 | Copyright (C) 1989, 1991 Free Software Foundation, Inc., 5 | 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA 6 | Everyone is permitted to copy and distribute verbatim copies 7 | of this license document, but changing it is not allowed. 8 | 9 | Preamble 10 | 11 | The licenses for most software are designed to take away your 12 | freedom to share and change it. By contrast, the GNU General Public 13 | License is intended to guarantee your freedom to share and change free 14 | software--to make sure the software is free for all its users. This 15 | General Public License applies to most of the Free Software 16 | Foundation's software and to any other program whose authors commit to 17 | using it. (Some other Free Software Foundation software is covered by 18 | the GNU Lesser General Public License instead.) You can apply it to 19 | your programs, too. 20 | 21 | When we speak of free software, we are referring to freedom, not 22 | price. Our General Public Licenses are designed to make sure that you 23 | have the freedom to distribute copies of free software (and charge for 24 | this service if you wish), that you receive source code or can get it 25 | if you want it, that you can change the software or use pieces of it 26 | in new free programs; and that you know you can do these things. 27 | 28 | To protect your rights, we need to make restrictions that forbid 29 | anyone to deny you these rights or to ask you to surrender the rights. 30 | These restrictions translate to certain responsibilities for you if you 31 | distribute copies of the software, or if you modify it. 32 | 33 | For example, if you distribute copies of such a program, whether 34 | gratis or for a fee, you must give the recipients all the rights that 35 | you have. You must make sure that they, too, receive or can get the 36 | source code. And you must show them these terms so they know their 37 | rights. 38 | 39 | We protect your rights with two steps: (1) copyright the software, and 40 | (2) offer you this license which gives you legal permission to copy, 41 | distribute and/or modify the software. 42 | 43 | Also, for each author's protection and ours, we want to make certain 44 | that everyone understands that there is no warranty for this free 45 | software. If the software is modified by someone else and passed on, we 46 | want its recipients to know that what they have is not the original, so 47 | that any problems introduced by others will not reflect on the original 48 | authors' reputations. 49 | 50 | Finally, any free program is threatened constantly by software 51 | patents. We wish to avoid the danger that redistributors of a free 52 | program will individually obtain patent licenses, in effect making the 53 | program proprietary. To prevent this, we have made it clear that any 54 | patent must be licensed for everyone's free use or not licensed at all. 55 | 56 | The precise terms and conditions for copying, distribution and 57 | modification follow. 58 | 59 | GNU GENERAL PUBLIC LICENSE 60 | TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 61 | 62 | 0. This License applies to any program or other work which contains 63 | a notice placed by the copyright holder saying it may be distributed 64 | under the terms of this General Public License. The "Program", below, 65 | refers to any such program or work, and a "work based on the Program" 66 | means either the Program or any derivative work under copyright law: 67 | that is to say, a work containing the Program or a portion of it, 68 | either verbatim or with modifications and/or translated into another 69 | language. (Hereinafter, translation is included without limitation in 70 | the term "modification".) Each licensee is addressed as "you". 71 | 72 | Activities other than copying, distribution and modification are not 73 | covered by this License; they are outside its scope. The act of 74 | running the Program is not restricted, and the output from the Program 75 | is covered only if its contents constitute a work based on the 76 | Program (independent of having been made by running the Program). 77 | Whether that is true depends on what the Program does. 78 | 79 | 1. You may copy and distribute verbatim copies of the Program's 80 | source code as you receive it, in any medium, provided that you 81 | conspicuously and appropriately publish on each copy an appropriate 82 | copyright notice and disclaimer of warranty; keep intact all the 83 | notices that refer to this License and to the absence of any warranty; 84 | and give any other recipients of the Program a copy of this License 85 | along with the Program. 86 | 87 | You may charge a fee for the physical act of transferring a copy, and 88 | you may at your option offer warranty protection in exchange for a fee. 89 | 90 | 2. You may modify your copy or copies of the Program or any portion 91 | of it, thus forming a work based on the Program, and copy and 92 | distribute such modifications or work under the terms of Section 1 93 | above, provided that you also meet all of these conditions: 94 | 95 | a) You must cause the modified files to carry prominent notices 96 | stating that you changed the files and the date of any change. 97 | 98 | b) You must cause any work that you distribute or publish, that in 99 | whole or in part contains or is derived from the Program or any 100 | part thereof, to be licensed as a whole at no charge to all third 101 | parties under the terms of this License. 102 | 103 | c) If the modified program normally reads commands interactively 104 | when run, you must cause it, when started running for such 105 | interactive use in the most ordinary way, to print or display an 106 | announcement including an appropriate copyright notice and a 107 | notice that there is no warranty (or else, saying that you provide 108 | a warranty) and that users may redistribute the program under 109 | these conditions, and telling the user how to view a copy of this 110 | License. (Exception: if the Program itself is interactive but 111 | does not normally print such an announcement, your work based on 112 | the Program is not required to print an announcement.) 113 | 114 | These requirements apply to the modified work as a whole. If 115 | identifiable sections of that work are not derived from the Program, 116 | and can be reasonably considered independent and separate works in 117 | themselves, then this License, and its terms, do not apply to those 118 | sections when you distribute them as separate works. But when you 119 | distribute the same sections as part of a whole which is a work based 120 | on the Program, the distribution of the whole must be on the terms of 121 | this License, whose permissions for other licensees extend to the 122 | entire whole, and thus to each and every part regardless of who wrote it. 123 | 124 | Thus, it is not the intent of this section to claim rights or contest 125 | your rights to work written entirely by you; rather, the intent is to 126 | exercise the right to control the distribution of derivative or 127 | collective works based on the Program. 128 | 129 | In addition, mere aggregation of another work not based on the Program 130 | with the Program (or with a work based on the Program) on a volume of 131 | a storage or distribution medium does not bring the other work under 132 | the scope of this License. 133 | 134 | 3. You may copy and distribute the Program (or a work based on it, 135 | under Section 2) in object code or executable form under the terms of 136 | Sections 1 and 2 above provided that you also do one of the following: 137 | 138 | a) Accompany it with the complete corresponding machine-readable 139 | source code, which must be distributed under the terms of Sections 140 | 1 and 2 above on a medium customarily used for software interchange; or, 141 | 142 | b) Accompany it with a written offer, valid for at least three 143 | years, to give any third party, for a charge no more than your 144 | cost of physically performing source distribution, a complete 145 | machine-readable copy of the corresponding source code, to be 146 | distributed under the terms of Sections 1 and 2 above on a medium 147 | customarily used for software interchange; or, 148 | 149 | c) Accompany it with the information you received as to the offer 150 | to distribute corresponding source code. (This alternative is 151 | allowed only for noncommercial distribution and only if you 152 | received the program in object code or executable form with such 153 | an offer, in accord with Subsection b above.) 154 | 155 | The source code for a work means the preferred form of the work for 156 | making modifications to it. For an executable work, complete source 157 | code means all the source code for all modules it contains, plus any 158 | associated interface definition files, plus the scripts used to 159 | control compilation and installation of the executable. However, as a 160 | special exception, the source code distributed need not include 161 | anything that is normally distributed (in either source or binary 162 | form) with the major components (compiler, kernel, and so on) of the 163 | operating system on which the executable runs, unless that component 164 | itself accompanies the executable. 165 | 166 | If distribution of executable or object code is made by offering 167 | access to copy from a designated place, then offering equivalent 168 | access to copy the source code from the same place counts as 169 | distribution of the source code, even though third parties are not 170 | compelled to copy the source along with the object code. 171 | 172 | 4. You may not copy, modify, sublicense, or distribute the Program 173 | except as expressly provided under this License. Any attempt 174 | otherwise to copy, modify, sublicense or distribute the Program is 175 | void, and will automatically terminate your rights under this License. 176 | However, parties who have received copies, or rights, from you under 177 | this License will not have their licenses terminated so long as such 178 | parties remain in full compliance. 179 | 180 | 5. You are not required to accept this License, since you have not 181 | signed it. However, nothing else grants you permission to modify or 182 | distribute the Program or its derivative works. These actions are 183 | prohibited by law if you do not accept this License. Therefore, by 184 | modifying or distributing the Program (or any work based on the 185 | Program), you indicate your acceptance of this License to do so, and 186 | all its terms and conditions for copying, distributing or modifying 187 | the Program or works based on it. 188 | 189 | 6. Each time you redistribute the Program (or any work based on the 190 | Program), the recipient automatically receives a license from the 191 | original licensor to copy, distribute or modify the Program subject to 192 | these terms and conditions. You may not impose any further 193 | restrictions on the recipients' exercise of the rights granted herein. 194 | You are not responsible for enforcing compliance by third parties to 195 | this License. 196 | 197 | 7. If, as a consequence of a court judgment or allegation of patent 198 | infringement or for any other reason (not limited to patent issues), 199 | conditions are imposed on you (whether by court order, agreement or 200 | otherwise) that contradict the conditions of this License, they do not 201 | excuse you from the conditions of this License. If you cannot 202 | distribute so as to satisfy simultaneously your obligations under this 203 | License and any other pertinent obligations, then as a consequence you 204 | may not distribute the Program at all. For example, if a patent 205 | license would not permit royalty-free redistribution of the Program by 206 | all those who receive copies directly or indirectly through you, then 207 | the only way you could satisfy both it and this License would be to 208 | refrain entirely from distribution of the Program. 209 | 210 | If any portion of this section is held invalid or unenforceable under 211 | any particular circumstance, the balance of the section is intended to 212 | apply and the section as a whole is intended to apply in other 213 | circumstances. 214 | 215 | It is not the purpose of this section to induce you to infringe any 216 | patents or other property right claims or to contest validity of any 217 | such claims; this section has the sole purpose of protecting the 218 | integrity of the free software distribution system, which is 219 | implemented by public license practices. Many people have made 220 | generous contributions to the wide range of software distributed 221 | through that system in reliance on consistent application of that 222 | system; it is up to the author/donor to decide if he or she is willing 223 | to distribute software through any other system and a licensee cannot 224 | impose that choice. 225 | 226 | This section is intended to make thoroughly clear what is believed to 227 | be a consequence of the rest of this License. 228 | 229 | 8. If the distribution and/or use of the Program is restricted in 230 | certain countries either by patents or by copyrighted interfaces, the 231 | original copyright holder who places the Program under this License 232 | may add an explicit geographical distribution limitation excluding 233 | those countries, so that distribution is permitted only in or among 234 | countries not thus excluded. In such case, this License incorporates 235 | the limitation as if written in the body of this License. 236 | 237 | 9. The Free Software Foundation may publish revised and/or new versions 238 | of the General Public License from time to time. Such new versions will 239 | be similar in spirit to the present version, but may differ in detail to 240 | address new problems or concerns. 241 | 242 | Each version is given a distinguishing version number. If the Program 243 | specifies a version number of this License which applies to it and "any 244 | later version", you have the option of following the terms and conditions 245 | either of that version or of any later version published by the Free 246 | Software Foundation. If the Program does not specify a version number of 247 | this License, you may choose any version ever published by the Free Software 248 | Foundation. 249 | 250 | 10. If you wish to incorporate parts of the Program into other free 251 | programs whose distribution conditions are different, write to the author 252 | to ask for permission. For software which is copyrighted by the Free 253 | Software Foundation, write to the Free Software Foundation; we sometimes 254 | make exceptions for this. Our decision will be guided by the two goals 255 | of preserving the free status of all derivatives of our free software and 256 | of promoting the sharing and reuse of software generally. 257 | 258 | NO WARRANTY 259 | 260 | 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY 261 | FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN 262 | OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES 263 | PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED 264 | OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF 265 | MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS 266 | TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE 267 | PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, 268 | REPAIR OR CORRECTION. 269 | 270 | 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING 271 | WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR 272 | REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, 273 | INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING 274 | OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED 275 | TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY 276 | YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER 277 | PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE 278 | POSSIBILITY OF SUCH DAMAGES. 279 | 280 | END OF TERMS AND CONDITIONS 281 | 282 | How to Apply These Terms to Your New Programs 283 | 284 | If you develop a new program, and you want it to be of the greatest 285 | possible use to the public, the best way to achieve this is to make it 286 | free software which everyone can redistribute and change under these terms. 287 | 288 | To do so, attach the following notices to the program. It is safest 289 | to attach them to the start of each source file to most effectively 290 | convey the exclusion of warranty; and each file should have at least 291 | the "copyright" line and a pointer to where the full notice is found. 292 | 293 | 294 | Copyright (C) 295 | 296 | This program is free software; you can redistribute it and/or modify 297 | it under the terms of the GNU General Public License as published by 298 | the Free Software Foundation; either version 2 of the License, or 299 | (at your option) any later version. 300 | 301 | This program is distributed in the hope that it will be useful, 302 | but WITHOUT ANY WARRANTY; without even the implied warranty of 303 | MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the 304 | GNU General Public License for more details. 305 | 306 | You should have received a copy of the GNU General Public License along 307 | with this program; if not, write to the Free Software Foundation, Inc., 308 | 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA. 309 | 310 | Also add information on how to contact you by electronic and paper mail. 311 | 312 | If the program is interactive, make it output a short notice like this 313 | when it starts in an interactive mode: 314 | 315 | Gnomovision version 69, Copyright (C) year name of author 316 | Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. 317 | This is free software, and you are welcome to redistribute it 318 | under certain conditions; type `show c' for details. 319 | 320 | The hypothetical commands `show w' and `show c' should show the appropriate 321 | parts of the General Public License. Of course, the commands you use may 322 | be called something other than `show w' and `show c'; they could even be 323 | mouse-clicks or menu items--whatever suits your program. 324 | 325 | You should also get your employer (if you work as a programmer) or your 326 | school, if any, to sign a "copyright disclaimer" for the program, if 327 | necessary. Here is a sample; alter the names: 328 | 329 | Yoyodyne, Inc., hereby disclaims all copyright interest in the program 330 | `Gnomovision' (which makes passes at compilers) written by James Hacker. 331 | 332 | , 1 April 1989 333 | Ty Coon, President of Vice 334 | 335 | This General Public License does not permit incorporating your program into 336 | proprietary programs. If your program is a subroutine library, you may 337 | consider it more useful to permit linking proprietary applications with the 338 | library. If this is what you want to do, use the GNU Lesser General 339 | Public License instead of this License. 340 | --------------------------------------------------------------------------------