├── .github └── FUNDING.yml ├── CONTRIBUTING.md ├── ENTERPRISE.md ├── README.md └── LICENSE /.github/FUNDING.yml: -------------------------------------------------------------------------------- 1 | # These are supported funding model platforms 2 | 3 | github: polhenarejos 4 | custom: ["https://www.paypal.me/polhenarejos"] 5 | -------------------------------------------------------------------------------- /CONTRIBUTING.md: -------------------------------------------------------------------------------- 1 | # Contributing 2 | 3 | Thank you for your interest in contributing to this project. 4 | 5 | This repository is published in two forms: 6 | - a Community Edition released under AGPLv3, and 7 | - a proprietary / commercial / Enterprise Edition offered to organizations. 8 | 9 | To keep that model legally clean, we need to be explicit about how contributions can be used. 10 | 11 | By opening a pull request, you agree to all of the following: 12 | 13 | 1. **You have the right to contribute this code.** 14 | You are either the original author of the contribution, or you have obtained the necessary rights/permissions to contribute it under these terms. 15 | 16 | 2. **Dual licensing permission.** 17 | You agree that your contribution may be: 18 | - merged into this repository, and 19 | - used, copied, modified, sublicensed, and redistributed 20 | - under the AGPLv3 Community Edition, and 21 | - under any proprietary / commercial / Enterprise editions of this project, 22 | now or in the future. 23 | 24 | In other words: you are granting the project maintainer(s) the right to include 25 | your contribution in both the open-source (AGPLv3) codebase and in closed-source / 26 | commercially licensed builds, without any additional approval or payment. 27 | 28 | 3. **Attribution.** 29 | The maintainers may keep or add attribution lines such as 30 | `Copyright (c) ` or an AUTHORS / CONTRIBUTORS list. 31 | The maintainers may also make changes for clarity, style, security, refactoring, 32 | or integration reasons. 33 | 34 | 4. **No automatic SLA.** 35 | Submitting a pull request does *not* create any support obligation, 36 | service-level agreement, warranty, or guarantee that the contribution 37 | will be reviewed, merged, or maintained. 38 | 39 | 5. **Potential rejection for business reasons.** 40 | Features that fall under "Enterprise / Commercial" functionality 41 | (e.g. multi-tenant provisioning at scale, centralized audit trails, 42 | corporate policy enforcement, attestation/branding flows, key escrow / dual-control, 43 | etc.) may be declined for the public AGPLv3 tree even if technically valid. 44 | That is normal: some functionality is intentionally offered only 45 | under commercial terms. 46 | 47 | If you are not comfortable with these terms, **do not open a pull request yet.** 48 | Instead, please open an Issue to start a discussion. 49 | 50 | ## How to contribute (technical side) 51 | 52 | ### 1. Bug reports / issues 53 | - Please include: 54 | - hardware / board revision 55 | - firmware / commit hash 56 | - exact steps to reproduce 57 | - expected vs actual behavior 58 | - logs / traces if available (strip secrets) 59 | 60 | Security-sensitive findings: do **not** post publicly. 61 | Send a short report by email instead so it can be triaged responsibly. 62 | 63 | ### 2. Small fixes / minor improvements 64 | - You can open a PR directly for: 65 | - bug fixes 66 | - portability fixes / new board definitions 67 | - clarifications in code comments 68 | - build / tooling cleanup 69 | - documentation of existing behavior 70 | 71 | Please keep PRs focused (one logical change per PR if possible). 72 | 73 | ### 3. Larger features / behavior changes 74 | - Please open an Issue first and describe: 75 | - what problem you're solving (not just "add feature X") 76 | - impact on existing flows / security model 77 | - any new dependencies 78 | 79 | This helps avoid doing a bunch of work on something that won't be accepted 80 | in the Community Edition. 81 | 82 | ### 4. Coding style / security posture 83 | - Aim for clarity and small, auditable changes. This code runs in places 84 | where secrets live. 85 | - No debug backdoors, no "just for testing" shortcuts left enabled. 86 | - Keep external dependencies minimal and license-compatible 87 | (MIT / Apache 2.0 / similarly permissive is usually fine). 88 | 89 | ### 5. Commit / PR format 90 | - Use descriptive commit messages ("Fix PIN retry counter wrap" is better than "fix stuff"). 91 | - In the PR description, please include a short summary of what was changed and why. 92 | - At the bottom of the PR description, **copy/paste and confirm the licensing line below**: 93 | 94 | > I confirm that I have read `CONTRIBUTING.md` and I agree that this contribution may be used under both the AGPLv3 Community Edition and any proprietary / commercial / Enterprise editions of this project, now or in the future. 95 | 96 | A PR without that confirmation may be delayed or closed without merge. 97 | 98 | ## Thank you 99 | 100 | This project exists because people build on it, break it, fix it, 101 | and push it into places it wasn't originally designed to go. 102 | 103 | Whether you are here for research, hacking on hardware, 104 | rolling out secure keys for a team, or building a commercial product: 105 | thank you for helping improve it. 106 | -------------------------------------------------------------------------------- /ENTERPRISE.md: -------------------------------------------------------------------------------- 1 | # Enterprise / Commercial Edition 2 | 3 | This project is offered under two editions: 4 | 5 | ## 1. Community Edition (FOSS) 6 | 7 | The Community Edition is released under the GNU Affero General Public License v3 (AGPLv3). 8 | 9 | Intended for: 10 | - individual users and researchers 11 | - evaluation / prototyping 12 | - internal lab / security testing 13 | 14 | You are allowed to: 15 | - read and study the source code 16 | - modify it 17 | - run it internally 18 | 19 | Obligations under AGPLv3: 20 | - If you distribute modified firmware/binaries/libraries to third parties, you must provide the corresponding source code of your modifications. 21 | - If you run a modified version of this project as a network-accessible service (internal or external), you must offer the source code of those modifications to the users of that service. 22 | - No warranty, no support, no SLA. 23 | - Enterprise features (bulk provisioning, multi-user policy enforcement, device inventory / revocation, corporate PIN rules, custom attestation/identity, etc.) are NOT included. 24 | 25 | The Community Edition will continue to exist. 26 | 27 | ## 2. Enterprise / Commercial Edition 28 | 29 | The Enterprise / Commercial Edition is a proprietary license for organizations that need to: 30 | 31 | - deploy this in production at scale (multiple devices / multiple users / multiple teams) 32 | - integrate it into their own physical product or appliance 33 | - run it as an internal service (VM / container / private cloud "HSM / auth backend") for multiple internal teams or tenants 34 | - enforce internal security policy (admin vs user roles, mandatory PIN rules, secure offboarding / revocation) 35 | - avoid any AGPLv3 disclosure obligations for their own modifications and integration code 36 | 37 | ### What the Enterprise Edition provides 38 | 39 | **Base license package (always included):** 40 | - **Commercial license (proprietary).** 41 | You may run and integrate the software/firmware in production — including virtualized / internal-cloud style deployments — without being required to disclose derivative source code under AGPLv3. 42 | - **Official signed builds.** 43 | You receive signed builds from the original developer so you can prove integrity and provenance. 44 | - **Onboarding call (up to 1 hour).** 45 | A live remote session to get you from "we have it" to "it’s actually running in our environment" with minimal guesswork. 46 | 47 | **Optional enterprise components (available on demand, scoped and priced per customer):** 48 | - **Production / multi-user readiness.** 49 | Permission to operate the system with multiple users, multiple devices and multiple teams in real environments. 50 | - **Bulk / fleet provisioning.** 51 | Automated enrollment for many tokens/devices/users at once (CSV / directory import), scripted onboarding of new users, initial PIN assignment / reset workflows, and role-based access (admin vs user). 52 | - **Policy & lifecycle tooling.** 53 | Corporate PIN policy enforcement, per-user / per-team access control, device inventory / traceability, and secure revocation / retirement when someone leaves. 54 | - **Custom attestation / per-organization identity.** 55 | Per-company certificate chains and attestation keys so devices can prove "this token/HSM is officially ours," including anti-cloning / unique device identity for OEM and fleet use. 56 | - **Virtualization / internal cloud deployment support.** 57 | Guidance and components to run this as an internal service (VM, container, private-cloud HSM/auth backend) serving multiple internal teams or tenants under your brand. 58 | - **Post-quantum (PQC) key material handling.** 59 | Integration/roadmap support for PQC algorithms (auth / signing) and secure PQC key storage inside the device or service. 60 | - **Hierarchical deterministic key derivation (HD).** 61 | Wallet-style hierarchical key trees (BIP32-like concepts adapted to this platform) for issuing per-user / per-tenant / per-purpose subkeys without exporting the root secret — e.g. embedded wallet logic, tenant isolation, firmware signing trees, large fleets. 62 | - **Cryptographically signed audit trail / tamper-evident event logging.** 63 | High-assurance logging of sensitive actions (key use, provisioning, PIN resets, revocations) with integrity protection for forensic / compliance needs. 64 | - **Dual-control / two-person approval ("four-eyes").** 65 | Require multi-party authorization for high-risk actions such as firmware signing, key export, or critical configuration changes — standard in high-assurance / regulated environments. 66 | - **Secure key escrow / disaster recovery design.** 67 | Split-secret or escrowed backup strategies so you don’t lose critical signing keys if a single admin disappears or hardware is lost. 68 | - **Release-signing / supply-chain hardening pipeline.** 69 | Reference tooling and process so every production firmware/binary is signed with hardware-backed keys, proving origin and preventing tampering in transit or at manufacturing. 70 | - **Policy-locked hardened mode ("FIPS-style profile").** 71 | Restricted algorithms, debug disabled, no raw key export, tamper-evident configuration for regulated / high-assurance deployments. 72 | - **Priority support / security response SLA.** 73 | A direct line and guaranteed response window for production-impacting security issues. 74 | - **White-label demo / pre-sales bundle.** 75 | Branded demo firmware + safe onboarding script so you can show "your product" to your own customers without exposing real production secrets. 76 | 77 | These components are NOT automatically bundled. They are available case-by-case depending on your use case and are priced separately. 78 | 79 | ### Licensing models 80 | 81 | - **Internal Use License** 82 | Internal production use within one legal entity (your company), including internal private cloud / virtualized deployments for multiple internal teams. 83 | Optional enterprise components can be added as needed. 84 | 85 | - **OEM / Redistribution / Service License** 86 | Integration into a product/appliance you ship to customers, OR operating this as a managed service / hosted feature for external clients or third parties. 87 | Optional enterprise components (attestation branding, PQC support, HD key derivation, multi-tenant service hardening, audit trail, etc.) can be added as required. 88 | 89 | Pricing depends on scope, fleet size, number of users/tenants, regulatory requirements, and which optional components you select. 90 | 91 | ### Request a quote 92 | 93 | Email: pol@henarejos.me 94 | Subject: `ENTERPRISE LICENSE ` 95 | 96 | Please include: 97 | - Company name and country 98 | - Intended use: 99 | - Internal private deployment 100 | - OEM / external service to third parties 101 | - Approximate scale (number of devices/tokens, number of users/tenants) 102 | - Which optional components you are interested in (bulk provisioning, policy & lifecycle tooling, attestation branding / anti-cloning, virtualization/cloud, PQC, HD key derivation, audit trail, dual-control, key escrow, supply-chain signing, hardened mode, SLA, white-label demo) 103 | 104 | You will receive: 105 | 1. A short commercial license agreement naming your company. 106 | 2. Access to the base package (and any optional components agreed). 107 | 3. Scheduling of the onboarding call. 108 | 109 | ## Why Enterprise exists 110 | 111 | - Companies often need hardware-backed security (HSM, FIDO2, OpenPGP, etc.) under their own control, but cannot or will not open-source their internal security workflows. 112 | - They also need multi-user / fleet-management features that hobby users do not. 113 | - The commercial license funds continued development, maintenance and new hardware support. 114 | 115 | The Community Edition remains AGPLv3. 116 | The Enterprise Edition is for production, scale, and legal clarity. 117 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Pico FIDO2 2 | 3 | This project transforms your Raspberry Pi Pico or ESP32 microcontroller into an integrated FIDO Passkey **and** OpenPGP smartcard, functioning like a standard USB Passkey for authentication and as a smartcard for cryptographic operations. 4 | 5 | --- 6 | 7 | ## Features 8 | 9 | Pico FIDO2 includes the following features: 10 | 11 | ### FIDO2 / U2F / WebAuthn 12 | 13 | - CTAP 2.1 / CTAP 1 14 | - WebAuthn 15 | - U2F 16 | - HMAC-Secret extension 17 | - CredProtect extension 18 | - User presence enforcement through physical button 19 | - User verification with PIN 20 | - Discoverable credentials (resident keys) 21 | - Credential management 22 | - ECDSA and EDDSA authentication 23 | - Support for SECP256R1, SECP384R1, SECP521R1, SECP256K1 and Ed25519 curves 24 | - App registration and login 25 | - Device selection 26 | - Support for vendor configuration 27 | - Backup with 24 words 28 | - Secure lock to protect the device from flash dumps 29 | - Permissions support (MC, GA, CM, ACFG, LBW) 30 | - Authenticator configuration 31 | - minPinLength extension 32 | - Self attestation 33 | - Enterprise attestation 34 | - credBlobs extension 35 | - largeBlobKey extension 36 | - Large blobs support (2048 bytes max) 37 | - OATH (based on YKOATH protocol specification) 38 | - TOTP / HOTP 39 | - Yubikey One Time Password 40 | - Challenge-response generation 41 | - Emulated keyboard interface 42 | - Button press generates an OTP that is directly typed 43 | - Yubico YKMAN compatible 44 | - Nitrokey nitropy and nitroapp compatible 45 | - Secure Boot and Secure Lock in RP2350 and ESP32-S3 MCUs 46 | - One Time Programming to store the master key that encrypts all resident keys and seeds. 47 | - Rescue interface to allow recovery of the device if it becomes unresponsive or undetectable. 48 | - LED customization with Pico Commissioner. 49 | 50 | ### OpenPGP Smartcard 51 | 52 | - OpenPGP card specification v3.4 53 | - 3 key slots (Signature, Encryption, Authentication) 54 | - RSA (2048, 3072, 4096), Ed25519, Curve25519, ECDSA (NIST P-256, P-384, P-521) 55 | - Key generation on device 56 | - Key import/export 57 | - PIN and Admin PIN protection 58 | - Reset and Unblock functions 59 | - Works with GnuPG, SSH, S/MIME, and compatible tools 60 | - CCID over USB 61 | - Compatible with major OS (Linux, Windows, macOS) 62 | - Touch button for user presence confirmation (optional) 63 | - Open source 64 | 65 | --- 66 | 67 | ## Security Considerations 68 | 69 | Microcontrollers RP2350 and ESP32-S3 are designed to support secure environments when Secure Boot is enabled, and optionally, Secure Lock. These features allow a master key encryption key (MKEK) to be stored in a one-time programmable (OTP) memory region, which is inaccessible from outside secure code. This master key is then used to encrypt all private and secret keys on the device, protecting sensitive data from potential flash memory dumps. 70 | 71 | **However**, the RP2040 microcontroller lacks this level of security hardware, meaning that it cannot provide the same protection. Data stored on its flash memory, including private or master keys, can be easily accessed or dumped, as encryption of the master key itself is not feasible. Consequently, if an RP2040 device is stolen, any stored private or secret keys may be exposed. 72 | 73 | --- 74 | 75 | ## Download 76 | 77 | **If you own an ESP32-S3 board, go to ESP32 Flasher for flashing your Pico FIDO2.** 78 | 79 | If you own a Raspberry Pico (RP2040 or RP2350), go to the Download page, select your vendor and model and download the proper firmware; or go to the Release page and download the UF2 file for your board. 80 | 81 | Note that UF2 files are shipped with a dummy VID/PID to avoid license issues (FEFF:FCFD). If you plan to use it with other proprietary tools, you should modify Info.plist of CCID driver to add these VID/PID or use the Pico Commissioner. 82 | 83 | You can use whatever VID/PID (i.e., 234b:0000 from FISJ), but remember that you are not authorized to distribute the binary with a VID/PID that you do not own. 84 | 85 | Note that the pure-browser option Pico Commissioner is the most recommended. 86 | 87 | --- 88 | 89 | ## Build for Raspberry Pico 90 | 91 | Before building, ensure you have installed the toolchain for the Pico and that the Pico SDK is properly located on your drive. 92 | 93 | ``` 94 | git clone https://github.com/youruser/pico-fido2 95 | git submodule update --init --recursive 96 | cd pico-fido2 97 | mkdir build 98 | cd build 99 | PICO_SDK_PATH=/path/to/pico-sdk cmake .. -DPICO_BOARD=board_type -DUSB_VID=0x1234 -DUSB_PID=0x5678 100 | make 101 | ``` 102 | 103 | Note that `PICO_BOARD`, `USB_VID` and `USB_PID` are optional. If not provided, `pico` board and VID/PID `FEFF:FCFD` will be used. 104 | 105 | Additionally, you can pass the `VIDPID=value` parameter to build the firmware with a known VID/PID. The supported values are: 106 | 107 | - `NitroHSM` 108 | - `NitroFIDO2` 109 | - `NitroStart` 110 | - `NitroPro` 111 | - `Nitro3` 112 | - `Yubikey5` 113 | - `YubikeyNeo` 114 | - `YubiHSM` 115 | - `Gnuk` 116 | - `GnuPG` 117 | 118 | After running `make`, the binary file `pico_fido2.uf2` will be generated. To load this onto your Pico board: 119 | 120 | 1. Put the Pico board into loading mode by holding the `BOOTSEL` button while plugging it in. 121 | 2. Copy the `pico_fido2.uf2` file to the new USB mass storage device that appears. 122 | 3. Once the file is copied, the Pico mass storage device will automatically disconnect, and the Pico board will reset with the new firmware. 123 | 4. A blinking LED will indicate that the device is ready to work. 124 | 125 | ## Driver 126 | 127 | Pico FIDO2 uses the `HID` driver for FIDO and `CCID` for OpenPGP, both present in all major operating systems. It should be detected by all OS and browser/applications just like normal USB FIDO keys and smartcards. 128 | 129 | ## License and Commercial Use 130 | 131 | This project is available under two editions: 132 | 133 | **Community Edition (FOSS)** 134 | - Released under the GNU Affero General Public License v3 (AGPLv3). 135 | - You are free to study, modify, and run the code, including for internal evaluation. 136 | - If you distribute modified binaries/firmware, OR if you run a modified version of this project as a network-accessible service, you must provide the corresponding source code to the users of that binary or service, as required by AGPLv3. 137 | - No warranty. No SLA. No guaranteed support. 138 | 139 | **Enterprise / Commercial Edition** 140 | - Proprietary license for organizations that want to: 141 | - run this in production with multiple users/devices, 142 | - integrate it into their own product/appliance, 143 | - enforce corporate policies (PIN policy, admin/user roles, revocation), 144 | - deploy it as an internal virtualized / cloud-style service, 145 | - and *not* be required to publish derivative source code. 146 | - Base package includes: 147 | - commercial license (no AGPLv3 disclosure obligation for your modifications / integration) 148 | - onboarding call 149 | - access to officially signed builds 150 | - Optional / on-demand enterprise components that can be added case-by-case: 151 | - ability to operate in multi-user / multi-device environments 152 | - device inventory, traceability and secure revocation/offboarding 153 | - custom attestation, per-organization device identity / anti-cloning 154 | - virtualization / internal "HSM or auth backend" service for multiple teams or tenants 155 | - post-quantum (PQC) key material handling and secure PQC credential storage 156 | - hierarchical deterministic key derivation (HD wallet–style key trees for per-user / per-tenant keys, firmware signing trees, etc.) 157 | - cryptographically signed audit trail / tamper-evident logging 158 | - dual-control / two-person approval for high-risk operations 159 | - secure key escrow / disaster recovery strategy 160 | - release-signing / supply-chain hardening toolchain 161 | - policy-locked hardened mode ("FIPS-style profile") 162 | - priority security-response SLA 163 | - white-label demo / pre-sales bundle 164 | 165 | Typical licensing models: 166 | - Internal use (single legal entity, including internal private cloud / virtualized deployments). 167 | - OEM / Redistribution / Service (ship in your product OR offer it as a service to third parties). 168 | 169 | These options are scoped and priced individually depending on which components you actually need. 170 | 171 | For commercial licensing and enterprise features, email pol@henarejos.me 172 | Subject: `ENTERPRISE LICENSE ` 173 | 174 | See `ENTERPRISE.md` for details. 175 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | GNU AFFERO GENERAL PUBLIC LICENSE 2 | Version 3, 19 November 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 Affero General Public License is a free, copyleft license for 11 | software and other kinds of works, specifically designed to ensure 12 | cooperation with the community in the case of network server software. 13 | 14 | The licenses for most software and other practical works are designed 15 | to take away your freedom to share and change the works. By contrast, 16 | our General Public Licenses are intended to guarantee your freedom to 17 | share and change all versions of a program--to make sure it remains free 18 | software for all its users. 19 | 20 | When we speak of free software, we are referring to freedom, not 21 | price. Our General Public Licenses are designed to make sure that you 22 | have the freedom to distribute copies of free software (and charge for 23 | them if you wish), that you receive source code or can get it if you 24 | want it, that you can change the software or use pieces of it in new 25 | free programs, and that you know you can do these things. 26 | 27 | Developers that use our General Public Licenses protect your rights 28 | with two steps: (1) assert copyright on the software, and (2) offer 29 | you this License which gives you legal permission to copy, distribute 30 | and/or modify the software. 31 | 32 | A secondary benefit of defending all users' freedom is that 33 | improvements made in alternate versions of the program, if they 34 | receive widespread use, become available for other developers to 35 | incorporate. Many developers of free software are heartened and 36 | encouraged by the resulting cooperation. However, in the case of 37 | software used on network servers, this result may fail to come about. 38 | The GNU General Public License permits making a modified version and 39 | letting the public access it on a server without ever releasing its 40 | source code to the public. 41 | 42 | The GNU Affero General Public License is designed specifically to 43 | ensure that, in such cases, the modified source code becomes available 44 | to the community. It requires the operator of a network server to 45 | provide the source code of the modified version running there to the 46 | users of that server. Therefore, public use of a modified version, on 47 | a publicly accessible server, gives the public access to the source 48 | code of the modified version. 49 | 50 | An older license, called the Affero General Public License and 51 | published by Affero, was designed to accomplish similar goals. This is 52 | a different license, not a version of the Affero GPL, but Affero has 53 | released a new version of the Affero GPL which permits relicensing under 54 | this license. 55 | 56 | The precise terms and conditions for copying, distribution and 57 | modification follow. 58 | 59 | TERMS AND CONDITIONS 60 | 61 | 0. Definitions. 62 | 63 | "This License" refers to version 3 of the GNU Affero General Public License. 64 | 65 | "Copyright" also means copyright-like laws that apply to other kinds of 66 | works, such as semiconductor masks. 67 | 68 | "The Program" refers to any copyrightable work licensed under this 69 | License. Each licensee is addressed as "you". "Licensees" and 70 | "recipients" may be individuals or organizations. 71 | 72 | To "modify" a work means to copy from or adapt all or part of the work 73 | in a fashion requiring copyright permission, other than the making of an 74 | exact copy. The resulting work is called a "modified version" of the 75 | earlier work or a work "based on" the earlier work. 76 | 77 | A "covered work" means either the unmodified Program or a work based 78 | on the Program. 79 | 80 | To "propagate" a work means to do anything with it that, without 81 | permission, would make you directly or secondarily liable for 82 | infringement under applicable copyright law, except executing it on a 83 | computer or modifying a private copy. Propagation includes copying, 84 | distribution (with or without modification), making available to the 85 | public, and in some countries other activities as well. 86 | 87 | To "convey" a work means any kind of propagation that enables other 88 | parties to make or receive copies. Mere interaction with a user through 89 | a computer network, with no transfer of a copy, is not conveying. 90 | 91 | An interactive user interface displays "Appropriate Legal Notices" 92 | to the extent that it includes a convenient and prominently visible 93 | feature that (1) displays an appropriate copyright notice, and (2) 94 | tells the user that there is no warranty for the work (except to the 95 | extent that warranties are provided), that licensees may convey the 96 | work under this License, and how to view a copy of this License. If 97 | the interface presents a list of user commands or options, such as a 98 | menu, a prominent item in the list meets this criterion. 99 | 100 | 1. Source Code. 101 | 102 | The "source code" for a work means the preferred form of the work 103 | for making modifications to it. "Object code" means any non-source 104 | form of a work. 105 | 106 | A "Standard Interface" means an interface that either is an official 107 | standard defined by a recognized standards body, or, in the case of 108 | interfaces specified for a particular programming language, one that 109 | is widely used among developers working in that language. 110 | 111 | The "System Libraries" of an executable work include anything, other 112 | than the work as a whole, that (a) is included in the normal form of 113 | packaging a Major Component, but which is not part of that Major 114 | Component, and (b) serves only to enable use of the work with that 115 | Major Component, or to implement a Standard Interface for which an 116 | implementation is available to the public in source code form. A 117 | "Major Component", in this context, means a major essential component 118 | (kernel, window system, and so on) of the specific operating system 119 | (if any) on which the executable work runs, or a compiler used to 120 | produce the work, or an object code interpreter used to run it. 121 | 122 | The "Corresponding Source" for a work in object code form means all 123 | the source code needed to generate, install, and (for an executable 124 | work) run the object code and to modify the work, including scripts to 125 | control those activities. However, it does not include the work's 126 | System Libraries, or general-purpose tools or generally available free 127 | programs which are used unmodified in performing those activities but 128 | which are not part of the work. For example, Corresponding Source 129 | includes interface definition files associated with source files for 130 | the work, and the source code for shared libraries and dynamically 131 | linked subprograms that the work is specifically designed to require, 132 | such as by intimate data communication or control flow between those 133 | subprograms and other parts of the work. 134 | 135 | The Corresponding Source need not include anything that users 136 | can regenerate automatically from other parts of the Corresponding 137 | Source. 138 | 139 | The Corresponding Source for a work in source code form is that 140 | same work. 141 | 142 | 2. Basic Permissions. 143 | 144 | All rights granted under this License are granted for the term of 145 | copyright on the Program, and are irrevocable provided the stated 146 | conditions are met. This License explicitly affirms your unlimited 147 | permission to run the unmodified Program. The output from running a 148 | covered work is covered by this License only if the output, given its 149 | content, constitutes a covered work. This License acknowledges your 150 | rights of fair use or other equivalent, as provided by copyright law. 151 | 152 | You may make, run and propagate covered works that you do not 153 | convey, without conditions so long as your license otherwise remains 154 | in force. You may convey covered works to others for the sole purpose 155 | of having them make modifications exclusively for you, or provide you 156 | with facilities for running those works, provided that you comply with 157 | the terms of this License in conveying all material for which you do 158 | not control copyright. Those thus making or running the covered works 159 | for you must do so exclusively on your behalf, under your direction 160 | and control, on terms that prohibit them from making any copies of 161 | your copyrighted material outside their relationship with you. 162 | 163 | Conveying under any other circumstances is permitted solely under 164 | the conditions stated below. Sublicensing is not allowed; section 10 165 | makes it unnecessary. 166 | 167 | 3. Protecting Users' Legal Rights From Anti-Circumvention Law. 168 | 169 | No covered work shall be deemed part of an effective technological 170 | measure under any applicable law fulfilling obligations under article 171 | 11 of the WIPO copyright treaty adopted on 20 December 1996, or 172 | similar laws prohibiting or restricting circumvention of such 173 | measures. 174 | 175 | When you convey a covered work, you waive any legal power to forbid 176 | circumvention of technological measures to the extent such circumvention 177 | is effected by exercising rights under this License with respect to 178 | the covered work, and you disclaim any intention to limit operation or 179 | modification of the work as a means of enforcing, against the work's 180 | users, your or third parties' legal rights to forbid circumvention of 181 | technological measures. 182 | 183 | 4. Conveying Verbatim Copies. 184 | 185 | You may convey verbatim copies of the Program's source code as you 186 | receive it, in any medium, provided that you conspicuously and 187 | appropriately publish on each copy an appropriate copyright notice; 188 | keep intact all notices stating that this License and any 189 | non-permissive terms added in accord with section 7 apply to the code; 190 | keep intact all notices of the absence of any warranty; and give all 191 | recipients a copy of this License along with the Program. 192 | 193 | You may charge any price or no price for each copy that you convey, 194 | and you may offer support or warranty protection for a fee. 195 | 196 | 5. Conveying Modified Source Versions. 197 | 198 | You may convey a work based on the Program, or the modifications to 199 | produce it from the Program, in the form of source code under the 200 | terms of section 4, provided that you also meet all of these conditions: 201 | 202 | a) The work must carry prominent notices stating that you modified 203 | it, and giving a relevant date. 204 | 205 | b) The work must carry prominent notices stating that it is 206 | released under this License and any conditions added under section 207 | 7. This requirement modifies the requirement in section 4 to 208 | "keep intact all notices". 209 | 210 | c) You must license the entire work, as a whole, under this 211 | License to anyone who comes into possession of a copy. This 212 | License will therefore apply, along with any applicable section 7 213 | additional terms, to the whole of the work, and all its parts, 214 | regardless of how they are packaged. This License gives no 215 | permission to license the work in any other way, but it does not 216 | invalidate such permission if you have separately received it. 217 | 218 | d) If the work has interactive user interfaces, each must display 219 | Appropriate Legal Notices; however, if the Program has interactive 220 | interfaces that do not display Appropriate Legal Notices, your 221 | work need not make them do so. 222 | 223 | A compilation of a covered work with other separate and independent 224 | works, which are not by their nature extensions of the covered work, 225 | and which are not combined with it such as to form a larger program, 226 | in or on a volume of a storage or distribution medium, is called an 227 | "aggregate" if the compilation and its resulting copyright are not 228 | used to limit the access or legal rights of the compilation's users 229 | beyond what the individual works permit. Inclusion of a covered work 230 | in an aggregate does not cause this License to apply to the other 231 | parts of the aggregate. 232 | 233 | 6. Conveying Non-Source Forms. 234 | 235 | You may convey a covered work in object code form under the terms 236 | of sections 4 and 5, provided that you also convey the 237 | machine-readable Corresponding Source under the terms of this License, 238 | in one of these ways: 239 | 240 | a) Convey the object code in, or embodied in, a physical product 241 | (including a physical distribution medium), accompanied by the 242 | Corresponding Source fixed on a durable physical medium 243 | customarily used for software interchange. 244 | 245 | b) Convey the object code in, or embodied in, a physical product 246 | (including a physical distribution medium), accompanied by a 247 | written offer, valid for at least three years and valid for as 248 | long as you offer spare parts or customer support for that product 249 | model, to give anyone who possesses the object code either (1) a 250 | copy of the Corresponding Source for all the software in the 251 | product that is covered by this License, on a durable physical 252 | medium customarily used for software interchange, for a price no 253 | more than your reasonable cost of physically performing this 254 | conveying of source, or (2) access to copy the 255 | Corresponding Source from a network server at no charge. 256 | 257 | c) Convey individual copies of the object code with a copy of the 258 | written offer to provide the Corresponding Source. This 259 | alternative is allowed only occasionally and noncommercially, and 260 | only if you received the object code with such an offer, in accord 261 | with subsection 6b. 262 | 263 | d) Convey the object code by offering access from a designated 264 | place (gratis or for a charge), and offer equivalent access to the 265 | Corresponding Source in the same way through the same place at no 266 | further charge. You need not require recipients to copy the 267 | Corresponding Source along with the object code. If the place to 268 | copy the object code is a network server, the Corresponding Source 269 | may be on a different server (operated by you or a third party) 270 | that supports equivalent copying facilities, provided you maintain 271 | clear directions next to the object code saying where to find the 272 | Corresponding Source. Regardless of what server hosts the 273 | Corresponding Source, you remain obligated to ensure that it is 274 | available for as long as needed to satisfy these requirements. 275 | 276 | e) Convey the object code using peer-to-peer transmission, provided 277 | you inform other peers where the object code and Corresponding 278 | Source of the work are being offered to the general public at no 279 | charge under subsection 6d. 280 | 281 | A separable portion of the object code, whose source code is excluded 282 | from the Corresponding Source as a System Library, need not be 283 | included in conveying the object code work. 284 | 285 | A "User Product" is either (1) a "consumer product", which means any 286 | tangible personal property which is normally used for personal, family, 287 | or household purposes, or (2) anything designed or sold for incorporation 288 | into a dwelling. In determining whether a product is a consumer product, 289 | doubtful cases shall be resolved in favor of coverage. For a particular 290 | product received by a particular user, "normally used" refers to a 291 | typical or common use of that class of product, regardless of the status 292 | of the particular user or of the way in which the particular user 293 | actually uses, or expects or is expected to use, the product. A product 294 | is a consumer product regardless of whether the product has substantial 295 | commercial, industrial or non-consumer uses, unless such uses represent 296 | the only significant mode of use of the product. 297 | 298 | "Installation Information" for a User Product means any methods, 299 | procedures, authorization keys, or other information required to install 300 | and execute modified versions of a covered work in that User Product from 301 | a modified version of its Corresponding Source. The information must 302 | suffice to ensure that the continued functioning of the modified object 303 | code is in no case prevented or interfered with solely because 304 | modification has been made. 305 | 306 | If you convey an object code work under this section in, or with, or 307 | specifically for use in, a User Product, and the conveying occurs as 308 | part of a transaction in which the right of possession and use of the 309 | User Product is transferred to the recipient in perpetuity or for a 310 | fixed term (regardless of how the transaction is characterized), the 311 | Corresponding Source conveyed under this section must be accompanied 312 | by the Installation Information. But this requirement does not apply 313 | if neither you nor any third party retains the ability to install 314 | modified object code on the User Product (for example, the work has 315 | been installed in ROM). 316 | 317 | The requirement to provide Installation Information does not include a 318 | requirement to continue to provide support service, warranty, or updates 319 | for a work that has been modified or installed by the recipient, or for 320 | the User Product in which it has been modified or installed. Access to a 321 | network may be denied when the modification itself materially and 322 | adversely affects the operation of the network or violates the rules and 323 | protocols for communication across the network. 324 | 325 | Corresponding Source conveyed, and Installation Information provided, 326 | in accord with this section must be in a format that is publicly 327 | documented (and with an implementation available to the public in 328 | source code form), and must require no special password or key for 329 | unpacking, reading or copying. 330 | 331 | 7. Additional Terms. 332 | 333 | "Additional permissions" are terms that supplement the terms of this 334 | License by making exceptions from one or more of its conditions. 335 | Additional permissions that are applicable to the entire Program shall 336 | be treated as though they were included in this License, to the extent 337 | that they are valid under applicable law. If additional permissions 338 | apply only to part of the Program, that part may be used separately 339 | under those permissions, but the entire Program remains governed by 340 | this License without regard to the additional permissions. 341 | 342 | When you convey a copy of a covered work, you may at your option 343 | remove any additional permissions from that copy, or from any part of 344 | it. (Additional permissions may be written to require their own 345 | removal in certain cases when you modify the work.) You may place 346 | additional permissions on material, added by you to a covered work, 347 | for which you have or can give appropriate copyright permission. 348 | 349 | Notwithstanding any other provision of this License, for material you 350 | add to a covered work, you may (if authorized by the copyright holders of 351 | that material) supplement the terms of this License with terms: 352 | 353 | a) Disclaiming warranty or limiting liability differently from the 354 | terms of sections 15 and 16 of this License; or 355 | 356 | b) Requiring preservation of specified reasonable legal notices or 357 | author attributions in that material or in the Appropriate Legal 358 | Notices displayed by works containing it; or 359 | 360 | c) Prohibiting misrepresentation of the origin of that material, or 361 | requiring that modified versions of such material be marked in 362 | reasonable ways as different from the original version; or 363 | 364 | d) Limiting the use for publicity purposes of names of licensors or 365 | authors of the material; or 366 | 367 | e) Declining to grant rights under trademark law for use of some 368 | trade names, trademarks, or service marks; or 369 | 370 | f) Requiring indemnification of licensors and authors of that 371 | material by anyone who conveys the material (or modified versions of 372 | it) with contractual assumptions of liability to the recipient, for 373 | any liability that these contractual assumptions directly impose on 374 | those licensors and authors. 375 | 376 | All other non-permissive additional terms are considered "further 377 | restrictions" within the meaning of section 10. If the Program as you 378 | received it, or any part of it, contains a notice stating that it is 379 | governed by this License along with a term that is a further 380 | restriction, you may remove that term. If a license document contains 381 | a further restriction but permits relicensing or conveying under this 382 | License, you may add to a covered work material governed by the terms 383 | of that license document, provided that the further restriction does 384 | not survive such relicensing or conveying. 385 | 386 | If you add terms to a covered work in accord with this section, you 387 | must place, in the relevant source files, a statement of the 388 | additional terms that apply to those files, or a notice indicating 389 | where to find the applicable terms. 390 | 391 | Additional terms, permissive or non-permissive, may be stated in the 392 | form of a separately written license, or stated as exceptions; 393 | the above requirements apply either way. 394 | 395 | 8. Termination. 396 | 397 | You may not propagate or modify a covered work except as expressly 398 | provided under this License. Any attempt otherwise to propagate or 399 | modify it is void, and will automatically terminate your rights under 400 | this License (including any patent licenses granted under the third 401 | paragraph of section 11). 402 | 403 | However, if you cease all violation of this License, then your 404 | license from a particular copyright holder is reinstated (a) 405 | provisionally, unless and until the copyright holder explicitly and 406 | finally terminates your license, and (b) permanently, if the copyright 407 | holder fails to notify you of the violation by some reasonable means 408 | prior to 60 days after the cessation. 409 | 410 | Moreover, your license from a particular copyright holder is 411 | reinstated permanently if the copyright holder notifies you of the 412 | violation by some reasonable means, this is the first time you have 413 | received notice of violation of this License (for any work) from that 414 | copyright holder, and you cure the violation prior to 30 days after 415 | your receipt of the notice. 416 | 417 | Termination of your rights under this section does not terminate the 418 | licenses of parties who have received copies or rights from you under 419 | this License. If your rights have been terminated and not permanently 420 | reinstated, you do not qualify to receive new licenses for the same 421 | material under section 10. 422 | 423 | 9. Acceptance Not Required for Having Copies. 424 | 425 | You are not required to accept this License in order to receive or 426 | run a copy of the Program. Ancillary propagation of a covered work 427 | occurring solely as a consequence of using peer-to-peer transmission 428 | to receive a copy likewise does not require acceptance. However, 429 | nothing other than this License grants you permission to propagate or 430 | modify any covered work. These actions infringe copyright if you do 431 | not accept this License. Therefore, by modifying or propagating a 432 | covered work, you indicate your acceptance of this License to do so. 433 | 434 | 10. Automatic Licensing of Downstream Recipients. 435 | 436 | Each time you convey a covered work, the recipient automatically 437 | receives a license from the original licensors, to run, modify and 438 | propagate that work, subject to this License. You are not responsible 439 | for enforcing compliance by third parties with this License. 440 | 441 | An "entity transaction" is a transaction transferring control of an 442 | organization, or substantially all assets of one, or subdividing an 443 | organization, or merging organizations. If propagation of a covered 444 | work results from an entity transaction, each party to that 445 | transaction who receives a copy of the work also receives whatever 446 | licenses to the work the party's predecessor in interest had or could 447 | give under the previous paragraph, plus a right to possession of the 448 | Corresponding Source of the work from the predecessor in interest, if 449 | the predecessor has it or can get it with reasonable efforts. 450 | 451 | You may not impose any further restrictions on the exercise of the 452 | rights granted or affirmed under this License. For example, you may 453 | not impose a license fee, royalty, or other charge for exercise of 454 | rights granted under this License, and you may not initiate litigation 455 | (including a cross-claim or counterclaim in a lawsuit) alleging that 456 | any patent claim is infringed by making, using, selling, offering for 457 | sale, or importing the Program or any portion of it. 458 | 459 | 11. Patents. 460 | 461 | A "contributor" is a copyright holder who authorizes use under this 462 | License of the Program or a work on which the Program is based. The 463 | work thus licensed is called the contributor's "contributor version". 464 | 465 | A contributor's "essential patent claims" are all patent claims 466 | owned or controlled by the contributor, whether already acquired or 467 | hereafter acquired, that would be infringed by some manner, permitted 468 | by this License, of making, using, or selling its contributor version, 469 | but do not include claims that would be infringed only as a 470 | consequence of further modification of the contributor version. For 471 | purposes of this definition, "control" includes the right to grant 472 | patent sublicenses in a manner consistent with the requirements of 473 | this License. 474 | 475 | Each contributor grants you a non-exclusive, worldwide, royalty-free 476 | patent license under the contributor's essential patent claims, to 477 | make, use, sell, offer for sale, import and otherwise run, modify and 478 | propagate the contents of its contributor version. 479 | 480 | In the following three paragraphs, a "patent license" is any express 481 | agreement or commitment, however denominated, not to enforce a patent 482 | (such as an express permission to practice a patent or covenant not to 483 | sue for patent infringement). To "grant" such a patent license to a 484 | party means to make such an agreement or commitment not to enforce a 485 | patent against the party. 486 | 487 | If you convey a covered work, knowingly relying on a patent license, 488 | and the Corresponding Source of the work is not available for anyone 489 | to copy, free of charge and under the terms of this License, through a 490 | publicly available network server or other readily accessible means, 491 | then you must either (1) cause the Corresponding Source to be so 492 | available, or (2) arrange to deprive yourself of the benefit of the 493 | patent license for this particular work, or (3) arrange, in a manner 494 | consistent with the requirements of this License, to extend the patent 495 | license to downstream recipients. "Knowingly relying" means you have 496 | actual knowledge that, but for the patent license, your conveying the 497 | covered work in a country, or your recipient's use of the covered work 498 | in a country, would infringe one or more identifiable patents in that 499 | country that you have reason to believe are valid. 500 | 501 | If, pursuant to or in connection with a single transaction or 502 | arrangement, you convey, or propagate by procuring conveyance of, a 503 | covered work, and grant a patent license to some of the parties 504 | receiving the covered work authorizing them to use, propagate, modify 505 | or convey a specific copy of the covered work, then the patent license 506 | you grant is automatically extended to all recipients of the covered 507 | work and works based on it. 508 | 509 | A patent license is "discriminatory" if it does not include within 510 | the scope of its coverage, prohibits the exercise of, or is 511 | conditioned on the non-exercise of one or more of the rights that are 512 | specifically granted under this License. You may not convey a covered 513 | work if you are a party to an arrangement with a third party that is 514 | in the business of distributing software, under which you make payment 515 | to the third party based on the extent of your activity of conveying 516 | the work, and under which the third party grants, to any of the 517 | parties who would receive the covered work from you, a discriminatory 518 | patent license (a) in connection with copies of the covered work 519 | conveyed by you (or copies made from those copies), or (b) primarily 520 | for and in connection with specific products or compilations that 521 | contain the covered work, unless you entered into that arrangement, 522 | or that patent license was granted, prior to 28 March 2007. 523 | 524 | Nothing in this License shall be construed as excluding or limiting 525 | any implied license or other defenses to infringement that may 526 | otherwise be available to you under applicable patent law. 527 | 528 | 12. No Surrender of Others' Freedom. 529 | 530 | If conditions are imposed on you (whether by court order, agreement or 531 | otherwise) that contradict the conditions of this License, they do not 532 | excuse you from the conditions of this License. If you cannot convey a 533 | covered work so as to satisfy simultaneously your obligations under this 534 | License and any other pertinent obligations, then as a consequence you may 535 | not convey it at all. For example, if you agree to terms that obligate you 536 | to collect a royalty for further conveying from those to whom you convey 537 | the Program, the only way you could satisfy both those terms and this 538 | License would be to refrain entirely from conveying the Program. 539 | 540 | 13. Remote Network Interaction; Use with the GNU General Public License. 541 | 542 | Notwithstanding any other provision of this License, if you modify the 543 | Program, your modified version must prominently offer all users 544 | interacting with it remotely through a computer network (if your version 545 | supports such interaction) an opportunity to receive the Corresponding 546 | Source of your version by providing access to the Corresponding Source 547 | from a network server at no charge, through some standard or customary 548 | means of facilitating copying of software. This Corresponding Source 549 | shall include the Corresponding Source for any work covered by version 3 550 | of the GNU General Public License that is incorporated pursuant to the 551 | following paragraph. 552 | 553 | Notwithstanding any other provision of this License, you have 554 | permission to link or combine any covered work with a work licensed 555 | under version 3 of the GNU General Public License into a single 556 | combined work, and to convey the resulting work. The terms of this 557 | License will continue to apply to the part which is the covered work, 558 | but the work with which it is combined will remain governed by version 559 | 3 of the GNU General Public License. 560 | 561 | 14. Revised Versions of this License. 562 | 563 | The Free Software Foundation may publish revised and/or new versions of 564 | the GNU Affero General Public License from time to time. Such new versions 565 | will be similar in spirit to the present version, but may differ in detail to 566 | address new problems or concerns. 567 | 568 | Each version is given a distinguishing version number. If the 569 | Program specifies that a certain numbered version of the GNU Affero General 570 | Public License "or any later version" applies to it, you have the 571 | option of following the terms and conditions either of that numbered 572 | version or of any later version published by the Free Software 573 | Foundation. If the Program does not specify a version number of the 574 | GNU Affero General Public License, you may choose any version ever published 575 | by the Free Software Foundation. 576 | 577 | If the Program specifies that a proxy can decide which future 578 | versions of the GNU Affero General Public License can be used, that proxy's 579 | public statement of acceptance of a version permanently authorizes you 580 | to choose that version for the Program. 581 | 582 | Later license versions may give you additional or different 583 | permissions. However, no additional obligations are imposed on any 584 | author or copyright holder as a result of your choosing to follow a 585 | later version. 586 | 587 | 15. Disclaimer of Warranty. 588 | 589 | THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY 590 | APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT 591 | HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY 592 | OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, 593 | THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR 594 | PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM 595 | IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF 596 | ALL NECESSARY SERVICING, REPAIR OR CORRECTION. 597 | 598 | 16. Limitation of Liability. 599 | 600 | IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING 601 | WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS 602 | THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY 603 | GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE 604 | USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF 605 | DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD 606 | PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), 607 | EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF 608 | SUCH DAMAGES. 609 | 610 | 17. Interpretation of Sections 15 and 16. 611 | 612 | If the disclaimer of warranty and limitation of liability provided 613 | above cannot be given local legal effect according to their terms, 614 | reviewing courts shall apply local law that most closely approximates 615 | an absolute waiver of all civil liability in connection with the 616 | Program, unless a warranty or assumption of liability accompanies a 617 | copy of the Program in return for a fee. 618 | 619 | END OF TERMS AND CONDITIONS 620 | 621 | How to Apply These Terms to Your New Programs 622 | 623 | If you develop a new program, and you want it to be of the greatest 624 | possible use to the public, the best way to achieve this is to make it 625 | free software which everyone can redistribute and change under these terms. 626 | 627 | To do so, attach the following notices to the program. It is safest 628 | to attach them to the start of each source file to most effectively 629 | state the exclusion of warranty; and each file should have at least 630 | the "copyright" line and a pointer to where the full notice is found. 631 | 632 | 633 | Copyright (C) 634 | 635 | This program is free software: you can redistribute it and/or modify 636 | it under the terms of the GNU Affero General Public License as published by 637 | the Free Software Foundation, either version 3 of the License, or 638 | (at your option) any later version. 639 | 640 | This program is distributed in the hope that it will be useful, 641 | but WITHOUT ANY WARRANTY; without even the implied warranty of 642 | MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the 643 | GNU Affero General Public License for more details. 644 | 645 | You should have received a copy of the GNU Affero General Public License 646 | along with this program. If not, see . 647 | 648 | Also add information on how to contact you by electronic and paper mail. 649 | 650 | If your software can interact with users remotely through a computer 651 | network, you should also make sure that it provides a way for users to 652 | get its source. For example, if your program is a web application, its 653 | interface could display a "Source" link that leads users to an archive 654 | of the code. There are many ways you could offer source, and different 655 | solutions will be better for different programs; see section 13 for the 656 | specific requirements. 657 | 658 | You should also get your employer (if you work as a programmer) or school, 659 | if any, to sign a "copyright disclaimer" for the program, if necessary. 660 | For more information on this, and how to apply and follow the GNU AGPL, see 661 | . --------------------------------------------------------------------------------