diff --git a/.github/ISSUE_TEMPLATE/bug_report.yml b/.github/ISSUE_TEMPLATE/bug_report.yml new file mode 100644 index 0000000..631b2f6 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/bug_report.yml @@ -0,0 +1,66 @@ +--- +name: 🐛 Bug report +description: Create a report to help us improve +type: Bug +body: + - type: markdown + attributes: + value: | + Thanks for taking the time to fill out this bug report! + + Before you continue filling out this report, please take a moment to check that your bug has not been [already reported on GitHub][issue search] 🙌 + + Remember to redact any sensitive information such as authentication credentials and/or license keys! + + **Note:** If you are seeking community support, please start a new topic in the [NGINX Community forum][forum]. If you wish to discuss the codebase, please start a new thread via [GitHub discussions][discussions]. + + [issue search]: https://github.com/nginx/nginx-acme/search?q=is%3Aissue&type=issues + [discussions]: https://github.com/nginx/nginx-acme/discussions + [forum]: https://community.nginx.org + + - type: textarea + id: overview + attributes: + label: Bug Overview + description: A clear and concise overview of the bug. + placeholder: When I do "X", "Y" happens instead of "Z". + validations: + required: true + + - type: textarea + id: behavior + attributes: + label: Expected Behavior + description: A clear and concise description of what you expected to happen. + placeholder: When I do "X", I expect "Z" to happen. + validations: + required: true + + - type: textarea + id: steps + attributes: + label: Steps to Reproduce the Bug + description: Detail the series of steps required to reproduce the bug. + placeholder: When I run "X" using [...], "X" fails with "Y" error message. If I check the terminal outputs and/or logs, I see the following info. + validations: + required: true + + - type: textarea + id: environment + attributes: + label: Environment Details + description: Please provide details about your environment. + value: | + - Target deployment platform: [e.g. AWS/GCP/local cluster/etc...] + - Target OS: [e.g. RHEL 9/Ubuntu 24.04/etc...] + - Version of this project or specific commit: [e.g. 1.4.3/commit hash] + - Version of any relevant project languages: [e.g. Kubernetes 1.30/Python 3.9.7/etc...] + validations: + required: true + + - type: textarea + id: context + attributes: + label: Additional Context + description: Add any other context about the problem here. + placeholder: Feel free to add any other context/information/screenshots/etc... that you think might be relevant to this issue in here. diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml new file mode 100644 index 0000000..bcac4c7 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/config.yml @@ -0,0 +1,12 @@ +--- +blank_issues_enabled: true +contact_links: + - name: 💬 Talk to the NGINX community! + url: https://community.nginx.org + about: A community forum for NGINX users, developers, and contributors + - name: 📝 Code of Conduct + url: https://www.contributor-covenant.org/version/2/1/code_of_conduct + about: NGINX follows the Contributor Covenant Code of Conduct to ensure a safe and inclusive community + - name: 💼 For commercial & enterprise users + url: https://www.f5.com/products/nginx + about: F5 offers a wide range of NGINX products for commercial & enterprise users diff --git a/.github/ISSUE_TEMPLATE/feature_request.yml b/.github/ISSUE_TEMPLATE/feature_request.yml new file mode 100644 index 0000000..e178089 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/feature_request.yml @@ -0,0 +1,40 @@ +--- +name: ✨ Feature request +description: Suggest an idea for this project +type: Enhancement +body: + - type: markdown + attributes: + value: | + Thanks for taking the time to fill out this feature request! + + Before you continue filling out this request, please take a moment to check that your feature has not been [already requested on GitHub][issue search] 🙌 + + **Note:** If you are seeking community support, please start a new topic in the [NGINX Community forum][forum]. If you wish to discuss the codebase, please start a new thread via [GitHub discussions][discussions]. + + [issue search]: https://github.com/nginx/nginx-acme/search?q=is%3Aissue&type=issues + [discussions]: https://github.com/nginx/nginx-acme/discussions + [forum]: https://community.nginx.org + + - type: textarea + id: overview + attributes: + label: Feature Overview + description: A clear and concise description of what the feature request is. + placeholder: I would like this project to be able to do "X". + validations: + required: true + + - type: textarea + id: alternatives + attributes: + label: Alternatives Considered + description: Detail any potential alternative solutions/workarounds you've used or considered. + placeholder: I have done/might be able to do "X" in this project by doing "Y". + + - type: textarea + id: context + attributes: + label: Additional Context + description: Add any other context about the problem here. + placeholder: Feel free to add any other context/information/screenshots/etc... that you think might be relevant to this feature request here. diff --git a/.github/dependabot.yml b/.github/dependabot.yml new file mode 100644 index 0000000..da5371e --- /dev/null +++ b/.github/dependabot.yml @@ -0,0 +1,19 @@ +--- +version: 2 +updates: + - package-ecosystem: "github-actions" + directory: "/" + schedule: + interval: "weekly" + day: "monday" + + - package-ecosystem: "cargo" + directory: "/" + groups: + all-dependencies: + patterns: + - "*" + schedule: + interval: "cron" + cronjob: "1 2 1,15 * *" + versioning-strategy: "increase-if-necessary" diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md new file mode 100644 index 0000000..369a4a3 --- /dev/null +++ b/.github/pull_request_template.md @@ -0,0 +1,13 @@ +### Proposed changes + +Describe the use case and detail of the change. If this PR addresses an issue on GitHub, make sure to include a link to that issue using one of the [supported keywords](https://docs.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue) in this PR's description or commit message. + +### Checklist + +Before creating a PR, run through this checklist and mark each as complete: + +- [ ] I have read the [contributing guidelines](/CONTRIBUTING.md). +- [ ] I have signed the [F5 Contributor License Agreement (CLA)](https://github.com/f5/f5-cla/blob/main/docs/f5_cla.md). +- [ ] If applicable, I have added tests that prove my fix is effective or that my feature works. +- [ ] If applicable, I have checked that any relevant tests pass after adding my changes. +- [ ] I have updated any relevant documentation ([`README.md`](/README.md) and/or [`CHANGELOG.md`](/CHANGELOG.md)). diff --git a/.github/workflows/f5_cla.yml b/.github/workflows/f5_cla.yml new file mode 100644 index 0000000..43e473e --- /dev/null +++ b/.github/workflows/f5_cla.yml @@ -0,0 +1,41 @@ +--- +name: F5 CLA +on: + issue_comment: + types: [created] + pull_request_target: + types: [opened, closed, synchronize] +permissions: read-all +jobs: + f5-cla: + name: F5 CLA + runs-on: ubuntu-24.04 + permissions: + actions: write + pull-requests: write + statuses: write + steps: + - name: Run F5 Contributor License Agreement (CLA) assistant + if: (github.event.comment.body == 'recheck' || github.event.comment.body == 'I have hereby read the F5 CLA and agree to its terms') || github.event_name == 'pull_request_target' + uses: contributor-assistant/github-action@ca4a40a7d1004f18d9960b404b97e5f30a505a08 # v2.6.1 + with: + # Path to the CLA document. + path-to-document: https://github.com/f5/f5-cla/blob/main/docs/f5_cla.md + # Custom CLA messages. + custom-notsigned-prcomment: '🎉 Thank you for your contribution! It appears you have not yet signed the [F5 Contributor License Agreement (CLA)](https://github.com/f5/f5-cla/blob/main/docs/f5_cla.md), which is required for your changes to be incorporated into an F5 Open Source Software (OSS) project. Please kindly read the [F5 CLA](https://github.com/f5/f5-cla/blob/main/docs/f5_cla.md) and reply on a new comment with the following text to agree:' + custom-pr-sign-comment: 'I have hereby read the F5 CLA and agree to its terms' + custom-allsigned-prcomment: '✅ All required contributors have signed the F5 CLA for this PR. Thank you!' + # Remote repository storing CLA signatures. + remote-organization-name: f5 + remote-repository-name: f5-cla-data + # Branch where CLA signatures are stored. + branch: main + path-to-signatures: signatures/signatures.json + # Comma separated list of usernames for maintainers or any other individuals who should not be prompted for a CLA. + # NOTE: You will want to edit the usernames to suit your project needs. + allowlist: bot* + # Do not lock PRs after a merge. + lock-pullrequest-aftermerge: false + env: + GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} + PERSONAL_ACCESS_TOKEN: ${{ secrets.F5_CLA_TOKEN }} diff --git a/.gitignore b/.gitignore index cced776..981389d 100644 --- a/.gitignore +++ b/.gitignore @@ -1,2 +1,34 @@ +######################## +# Any crt/keys/license # +######################## +*.crt +*.key + +########################## +# Backup/temporary files # +########################## +*~ +\#* + +################## +# MacOS specific # +################## +Thumbs.db +.DS_Store + +######################## +# Code editor specific # +######################## +.idea +.vscode + +######## +# Logs # +######## +*.log + +########################### +# Project build artifacts # +########################### /target /objs-* diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md new file mode 100644 index 0000000..e18d370 --- /dev/null +++ b/CODE_OF_CONDUCT.md @@ -0,0 +1,78 @@ +# Contributor Covenant Code of Conduct + +## Our Pledge + +We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation. + +We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community. + +## Our Standards + +Examples of behavior that contributes to a positive environment for our community include: + +- Demonstrating empathy and kindness toward other people. +- Being respectful of differing opinions, viewpoints, and experiences. +- Giving and gracefully accepting constructive feedback. +- Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience. +- Focusing on what is best not just for us as individuals, but for the overall community. + +Examples of unacceptable behavior include: + +- The use of sexualized language or imagery, and sexual attention or advances of any kind. +- Trolling, insulting or derogatory comments, and personal or political attacks. +- Public or private harassment. +- Publishing others' private information, such as a physical or email address, without their explicit permission. +- Other conduct which could reasonably be considered inappropriate in a professional setting. + +## Enforcement Responsibilities + +Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful. + +Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate. + +## Scope + +This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official email address, posting via an official social media account, or acting as an appointed representative at an online or offline event. + +## Enforcement + +Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at . All complaints will be reviewed and investigated promptly and fairly. + +All community leaders are obligated to respect the privacy and security of the reporter of any incident. + +## Enforcement Guidelines + +Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct: + +### 1. Correction + +**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community. + +**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested. + +### 2. Warning + +**Community Impact**: A violation through a single incident or series of actions. + +**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban. + +### 3. Temporary Ban + +**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior. + +**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban. + +### 4. Permanent Ban + +**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals. + +**Consequence**: A permanent ban from any sort of public interaction within the community. + +## Attribution + +This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org), version 2.1, available at . + +Community Impact Guidelines were inspired by +[Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/inclusion). + +For answers to common questions about this code of conduct, see the FAQ at . Translations are available at . diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md new file mode 100644 index 0000000..64855ca --- /dev/null +++ b/CONTRIBUTING.md @@ -0,0 +1,47 @@ +# Contributing Guidelines + +The following is a set of guidelines for contributing to this project. We really appreciate that you are considering contributing! + +#### Table of Contents + +- [Getting Started](#getting-started) +- [Contributing](#contributing) +- [Code of Conduct](/CODE_OF_CONDUCT.md) + +## Getting Started + +Follow the instructions on the README's [Getting Started](/README.md#Getting-Started) section to get this project up and running. + +## Contributing + +### Report a Bug + +To report a bug, open an issue on GitHub with the type `Bug` using the available [bug report issue form](/.github/ISSUE_TEMPLATE/bug_report.yml). Please ensure the bug has not already been reported. **If the bug is a potential security vulnerability, please report it using our [security policy](/SECURITY.md).** + +### Suggest a Feature or Enhancement + +To suggest a feature or enhancement, please create an issue on GitHub with the type `Enhancement` using the available [feature request issue form](/.github/ISSUE_TEMPLATE/feature_request.yml). Please ensure the feature or enhancement has not already been suggested. + +### Open a Pull Request (PR) + +- Fork the repo, create a branch, implement your changes, add any relevant tests, and submit a PR when your changes are **tested** and ready for review. +- Fill in the [PR template](/.github/pull_request_template.md). + +> [!NOTE] +> If you'd like to implement a new feature, please consider creating a [feature request issue](/.github/ISSUE_TEMPLATE/feature_request.yml) first to start a discussion about the feature. + +#### F5 Contributor License Agreement (CLA) + +F5 requires all contributors to agree to the terms of the F5 CLA (available [here](https://github.com/f5/f5-cla/blob/main/docs/f5_cla.md)) before any of their changes can be incorporated into an F5 Open Source repository (even contributions to the F5 CLA itself!). + +If you have not yet agreed to the F5 CLA terms and submit a PR to this repository, a bot will prompt you to view and agree to the F5 CLA. You will have to agree to the F5 CLA terms through a comment in the PR before any of your changes can be merged. Your agreement signature will be safely stored by F5 and no longer be required in future PRs. + +### Git Guidelines + +- Keep a clean, concise and meaningful git commit history on your branch (within reason), rebasing locally and squashing before submitting a PR. +- Follow the guidelines of writing a good commit message as described here and summarized in the next few points: + - In the subject line, use the present tense ("Add feature" not "Added feature"). + - In the subject line, use the imperative mood ("Move cursor to..." not "Moves cursor to..."). + - Limit the subject line to 72 characters or less. + - Reference issues and pull requests liberally after the subject line. + - Add more detailed description in the body of the git message (`git commit -a` to give you more space and time in your text editor to write a good message instead of `git commit -am`). diff --git a/README.md b/README.md index fe23a19..60f6b22 100644 --- a/README.md +++ b/README.md @@ -1,20 +1,29 @@ +[![Project Status: Active – The project has reached a stable, usable state and is being actively developed.](https://www.repostatus.org/badges/latest/active.svg)](https://www.repostatus.org/#active) +[![Community Support](https://badgen.net/badge/support/community/cyan?icon=awesome)](/SUPPORT.md) +[![Community Forum](https://img.shields.io/badge/community-forum-009639?logo=discourse&link=https%3A%2F%2Fcommunity.nginx.org)](https://community.nginx.org) +[![License](https://img.shields.io/badge/License-Apache%202.0-blue.svg)](https://opensource.org/license/apache-2-0) +[![Contributor Covenant](https://img.shields.io/badge/Contributor%20Covenant-2.1-4baaaa.svg)](/CODE_OF_CONDUCT.md) + # nginx-acme nginx-acme is an [NGINX] module with the implementation of the automatic -certificate management ([ACME]) protocol. +certificate management ([ACMEv2]) protocol. [NGINX]: https://nginx.org/ -[ACME]: https://www.rfc-editor.org/rfc/rfc8555.html +[ACMEv2]: https://www.rfc-editor.org/rfc/rfc8555.html -## Building +## Getting Started ### Requirements -- Regular nginx build dependencies +- Regular NGINX build dependencies: C compliler, make, PCRE2, Zlib - System-wide installation of OpenSSL 1.1.1 or later - Rust toolchain (1.81.0 or later) +- [libclang] for rust-bindgen + +[libclang]: https://rust-lang.github.io/rust-bindgen/requirements.html -### Commands +### Building One way to build the module is to export a path to a pre-built nginx source tree and run `cargo`. @@ -38,10 +47,10 @@ auto/configure \ --add-[dynamic-]module=/path/to/nginx-acme ``` -The result will be located at `$NGX_OBJS/ngx_http_acme_module.so`. +The result will be located at `objs/ngx_http_acme_module.so`. Currently this method produces a slightly larger library, as we don't instruct -the linker to perform LTO and dead code elimination. +the linker to perform LTO and remove unused code. ## How to Use @@ -246,6 +255,10 @@ SSL certificate that can be passed to the SSL certificate private key that can be passed to the [ssl_certificate_key](https://nginx.org/en/docs/http/ngx_http_ssl_module.html#ssl_certificate_key). +## Contributing + +Please see the [contributing guide](/CONTRIBUTING.md) for guidelines on how to best contribute to this project. + ## License [Apache License, Version 2.0](/LICENSE) diff --git a/SECURITY.md b/SECURITY.md new file mode 100644 index 0000000..8052046 --- /dev/null +++ b/SECURITY.md @@ -0,0 +1,11 @@ +# Security Policy + +## Latest Versions + +We advise users to run or update to the most recent release of this project. Older versions of this project may not have all enhancements and/or bug fixes applied to them. + +## Reporting a Vulnerability + +The F5 Security Incident Response Team (F5 SIRT) requests that you report any potential or current instances of security vulnerabilities in any F5 product to the F5 Security Incident Response Team at . + +For more information, please read the F5 SIRT vulnerability reporting guidelines available at [https://www.f5.com/support/report-a-vulnerability](https://www.f5.com/support/report-a-vulnerability). diff --git a/SUPPORT.md b/SUPPORT.md new file mode 100644 index 0000000..a3f9a3b --- /dev/null +++ b/SUPPORT.md @@ -0,0 +1,29 @@ +# Support + +## Ask a Question + +We use GitHub for tracking bugs and feature requests related to this project. + +Don't know how something in this project works? Curious if this project can achieve your desired functionality? Please open an issue on GitHub with the label `question`. Alternatively, start a GitHub discussion! + +## NGINX Specific Questions and/or Issues + +This isn't the right place to get support for NGINX specific questions, but the following resources are available below. Thanks for your understanding! + +### Community Forum + +We have a community [forum](https://community.nginx.org/)! If you have any questions and/or issues, try checking out the [`Troubleshooting`](https://community.nginx.org/c/troubleshooting/8) and [`How do I...?`](https://community.nginx.org/c/how-do-i/9) categories. Both fellow community members and NGINXers might be able to help you! :) + +### Documentation + +For a comprehensive list of all NGINX directives, check out . + +For a comprehensive list of administration and deployment guides for all NGINX products, check out . + +## Contributing + +Please see the [contributing guide](/CONTRIBUTING.md) for guidelines on how to best contribute to this project. + +## Community and Commercial Support + +Community support is offered on a best effort basis through either GitHub issues/PRs/discussions or through any of our active communities. For commercial support, please get in touch with [NGINX sales](https://www.f5.com/products/get-f5/) or check your contract details for more information! diff --git a/auto/rust b/auto/rust index 109a2a2..f152ad5 100644 --- a/auto/rust +++ b/auto/rust @@ -1,6 +1,6 @@ #!/bin/sh # -# Copyright 2025 Nginx, Inc. +# Copyright (c) F5, Inc. # # Licensed under the Apache License, Version 2.0 (the "License"); # you may not use this file except in compliance with the License. diff --git a/build.rs b/build.rs index 7ea22fc..4b94326 100644 --- a/build.rs +++ b/build.rs @@ -1,3 +1,8 @@ +// Copyright (c) F5, Inc. +// +// This source code is licensed under the Apache License, Version 2.0 license found in the +// LICENSE file in the root directory of this source tree. + use std::env; /// Buildscript for an nginx module. diff --git a/src/conf.rs b/src/conf.rs index 01f2ae4..3792056 100644 --- a/src/conf.rs +++ b/src/conf.rs @@ -1,3 +1,8 @@ +// Copyright (c) F5, Inc. +// +// This source code is licensed under the Apache License, Version 2.0 license found in the +// LICENSE file in the root directory of this source tree. + use core::ffi::{c_char, c_void, CStr}; use core::{mem, ptr}; diff --git a/src/conf/ext.rs b/src/conf/ext.rs index e4feb69..db28cff 100644 --- a/src/conf/ext.rs +++ b/src/conf/ext.rs @@ -1,5 +1,9 @@ -//! Extension traits for nginx-sys types. +// Copyright (c) F5, Inc. +// +// This source code is licensed under the Apache License, Version 2.0 license found in the +// LICENSE file in the root directory of this source tree. +//! Extension traits for nginx-sys types. use core::ffi::c_char; use core::{error::Error as StdError, ptr}; diff --git a/src/conf/identifier.rs b/src/conf/identifier.rs index fbc18f6..2c9b4af 100644 --- a/src/conf/identifier.rs +++ b/src/conf/identifier.rs @@ -1,3 +1,8 @@ +// Copyright (c) F5, Inc. +// +// This source code is licensed under the Apache License, Version 2.0 license found in the +// LICENSE file in the root directory of this source tree. + use core::str; use ngx::allocator::{AllocError, Allocator, TryCloneIn}; diff --git a/src/conf/issuer.rs b/src/conf/issuer.rs index f017d5a..00f104b 100644 --- a/src/conf/issuer.rs +++ b/src/conf/issuer.rs @@ -1,3 +1,8 @@ +// Copyright (c) F5, Inc. +// +// This source code is licensed under the Apache License, Version 2.0 license found in the +// LICENSE file in the root directory of this source tree. + use core::error::Error as StdError; use core::ptr::{self, NonNull}; use core::str; diff --git a/src/conf/order.rs b/src/conf/order.rs index b5775d6..7e2483c 100644 --- a/src/conf/order.rs +++ b/src/conf/order.rs @@ -1,3 +1,8 @@ +// Copyright (c) F5, Inc. +// +// This source code is licensed under the Apache License, Version 2.0 license found in the +// LICENSE file in the root directory of this source tree. + use core::fmt::{self, Write}; use core::hash::{self, Hash, Hasher}; use core::net::IpAddr; diff --git a/src/conf/pkey.rs b/src/conf/pkey.rs index a11c24d..04b91f1 100644 --- a/src/conf/pkey.rs +++ b/src/conf/pkey.rs @@ -1,3 +1,8 @@ +// Copyright (c) F5, Inc. +// +// This source code is licensed under the Apache License, Version 2.0 license found in the +// LICENSE file in the root directory of this source tree. + use nginx_sys::ngx_str_t; use openssl::nid::Nid; use openssl::pkey::{PKey, Private}; diff --git a/src/conf/shared_zone.rs b/src/conf/shared_zone.rs index ccb6012..799c476 100644 --- a/src/conf/shared_zone.rs +++ b/src/conf/shared_zone.rs @@ -1,3 +1,8 @@ +// Copyright (c) F5, Inc. +// +// This source code is licensed under the Apache License, Version 2.0 license found in the +// LICENSE file in the root directory of this source tree. + use core::ffi::c_void; use core::ptr::{self, NonNull}; diff --git a/src/conf/ssl.rs b/src/conf/ssl.rs index 1f49d3e..c5cead9 100644 --- a/src/conf/ssl.rs +++ b/src/conf/ssl.rs @@ -1,3 +1,8 @@ +// Copyright (c) F5, Inc. +// +// This source code is licensed under the Apache License, Version 2.0 license found in the +// LICENSE file in the root directory of this source tree. + //! Various SSL configuration utilities. use core::ffi::{c_void, CStr}; use core::{mem, ptr}; diff --git a/src/lib.rs b/src/lib.rs index d7355af..c18049b 100644 --- a/src/lib.rs +++ b/src/lib.rs @@ -1,3 +1,8 @@ +// Copyright (c) F5, Inc. +// +// This source code is licensed under the Apache License, Version 2.0 license found in the +// LICENSE file in the root directory of this source tree. + #![no_std] extern crate std; diff --git a/src/state.rs b/src/state.rs index 2316385..88c3f44 100644 --- a/src/state.rs +++ b/src/state.rs @@ -1,3 +1,8 @@ +// Copyright (c) F5, Inc. +// +// This source code is licensed under the Apache License, Version 2.0 license found in the +// LICENSE file in the root directory of this source tree. + //! Shared runtime state of the module. use core::ffi::c_void; use core::ptr; diff --git a/src/state/certificate.rs b/src/state/certificate.rs index 94fd90a..3e3b362 100644 --- a/src/state/certificate.rs +++ b/src/state/certificate.rs @@ -1,3 +1,8 @@ +// Copyright (c) F5, Inc. +// +// This source code is licensed under the Apache License, Version 2.0 license found in the +// LICENSE file in the root directory of this source tree. + use core::error::Error as StdError; use core::time::Duration; use std::string::ToString; diff --git a/src/state/issuer.rs b/src/state/issuer.rs index f81cd9f..c9efd3c 100644 --- a/src/state/issuer.rs +++ b/src/state/issuer.rs @@ -1,3 +1,8 @@ +// Copyright (c) F5, Inc. +// +// This source code is licensed under the Apache License, Version 2.0 license found in the +// LICENSE file in the root directory of this source tree. + use core::error::Error as StdError; use core::ptr; diff --git a/src/time.rs b/src/time.rs index ec47944..637e5ff 100644 --- a/src/time.rs +++ b/src/time.rs @@ -1,3 +1,8 @@ +// Copyright (c) F5, Inc. +// +// This source code is licensed under the Apache License, Version 2.0 license found in the +// LICENSE file in the root directory of this source tree. + use core::ops; use core::time::Duration; diff --git a/src/variables.rs b/src/variables.rs index 96ceea7..a1ece12 100644 --- a/src/variables.rs +++ b/src/variables.rs @@ -1,3 +1,8 @@ +// Copyright (c) F5, Inc. +// +// This source code is licensed under the Apache License, Version 2.0 license found in the +// LICENSE file in the root directory of this source tree. + use nginx_sys::{ ngx_http_request_t, ngx_http_variable_t, ngx_int_t, ngx_str_t, ngx_variable_value_t, }; diff --git a/t/acme_conf_certificate.t b/t/acme_conf_certificate.t index 152b591..e4ccc04 100644 --- a/t/acme_conf_certificate.t +++ b/t/acme_conf_certificate.t @@ -1,7 +1,9 @@ #!/usr/bin/perl -# (C) Aleksei Bavshin -# (C) Nginx, Inc. +# Copyright (c) F5, Inc. +# +# This source code is licensed under the Apache License, Version 2.0 license +# found in the LICENSE file in the root directory of this source tree. # Tests for ACME client: configuration parsing and validation. diff --git a/t/acme_conf_issuer.t b/t/acme_conf_issuer.t index 714f528..c834a2d 100644 --- a/t/acme_conf_issuer.t +++ b/t/acme_conf_issuer.t @@ -1,7 +1,9 @@ #!/usr/bin/perl -# (C) Aleksei Bavshin -# (C) Nginx, Inc. +# Copyright (c) F5, Inc. +# +# This source code is licensed under the Apache License, Version 2.0 license +# found in the LICENSE file in the root directory of this source tree. # Tests for ACME client: configuration parsing and validation.