hanko_xml 0.1.0

data/README.md

@@ -0,0 +1,222 @@
+<p align="center">
+  <img src="assets/hanko-mark.png" alt="HankoXml" width="120" height="120">
+</p>
+
+<h1 align="center">HankoXml</h1>
+
+<p align="center">
+  A high-performance, strictly secure XML Digital Signature (XML-DSig) library for Ruby.
+</p>
+
+---
+
+HankoXml is backed by a native Rust extension that binds directly to [libxmlsec1](https://www.aleksey.com/xmlsec/) using [Magnus](https://github.com/matsadler/magnus). It is designed to be completely byte-faithful, blazingly fast, and natively immune to XML Signature Wrapping (XSW) attacks.
+
+It works nicely with Nokogiri, signing and verifying the documents you already hold without fragile re-serialization, and it works without Nokogiri too: verification runs on plain bytes.
+
+## Features
+- **Full XML-DSig Support:** Sign and verify Enveloped, Enveloping, and Detached signatures.
+- **Nokogiri Native, Nokogiri Optional:** Signs and verifies the Nokogiri documents you already hold, with opt-in `doc.sign!` / `doc.signature_valid?` shorthands (`require "hanko_xml/nokogiri_ext"`), and verifies Strings, files and IOs without Nokogiri.
+- **XSW Defense:** Provides a robust `Policy` engine and structural `signed?(node)` checks to defeat XML Signature Wrapping (XSW) attacks.
+- **Rust-Backed:** Memory-safe FFI boundaries, zero shell-outs to CLI binaries, and massive performance gains over pure-Ruby cryptography.
+
+A feature and security comparison with Python [SignXML](https://pypi.org/project/signxml/), including a plan to close the remaining gaps (XAdES first), lives in [`docs/src/content/guide/comparison-signxml.md`](docs/src/content/guide/comparison-signxml.md).
+
+## Requirements
+
+Most users install a precompiled platform gem and do **not** need a local build
+toolchain.
+
+- Ruby 3.1+
+
+Precompiled gems are published for:
+
+- `x86_64-linux`
+- `aarch64-linux`
+- `arm64-darwin`
+- `x64-mingw-ucrt`
+
+### Building from source (fallback)
+
+If RubyGems falls back to the source gem for your platform, HankoXml compiles
+its Rust extension against the local `libxmlsec1`, so the build toolchain has
+to be present:
+
+- Rust toolchain (stable)
+- `libxmlsec1` and `libxml2` development headers, `pkg-config`, and libclang
+  (bindgen generates the FFI bindings during the build):
+  - **macOS:** `brew install libxmlsec1 libxml2 pkg-config`
+  - **Debian/Ubuntu:** `apt install libxmlsec1-dev libxml2-dev pkg-config libclang-dev`
+
+Supported libxmlsec1: `>= 1.2.30, < 1.4`.
+
+*(Note for macOS: Homebrew's `libxml2` is keg-only. HankoXml's `build.rs` automatically works around this by resolving absolute library paths during compilation.)*
+
+### Version safety
+
+bindgen bakes xmlsec's and libxml2's struct layouts into the compiled
+extension, and a later mismatch is invisible to the dynamic linker — every
+symbol still resolves, and a field is then read at the wrong offset. HankoXml
+checks for this when it loads and raises `HankoXml::NativeVersionMismatch`
+rather than returning a wrong answer from `verify!`:
+
+```ruby
+HankoXml::NativeVersion.build_versions
+# => { xmlsec: "1.3.12", libxml2: "2.15.3", crypto: "openssl" }
+```
+
+If you installed from source and later upgrade libxmlsec1 through your OS
+package manager, rebuild the extension with `gem pristine hanko_xml`.
+
+## Installation
+
+Add this line to your application's Gemfile:
+
+```ruby
+gem "hanko_xml"
+```
+
+Nokogiri is optional, and `hanko_xml` does not depend on it or load it. Pick
+the setup that fits:
+
+- **With Nokogiri** (most projects already have it): add `gem "nokogiri"` and
+  `require "nokogiri"`. Everything is available, including signing, the
+  Nokogiri API below, and node-level `signed?` checks.
+- **Bytes only**: leave Nokogiri out. Verification works on a String, a path
+  or an IO, with the same policy, schema and structural checks. Signing works
+  when the document already holds the `<Signature>` template. Building one, and
+  the DOM features, raise `HankoXml::NokogiriRequired`, naming what needs
+  Nokogiri.
+
+| Capability | With Nokogiri | Bytes only |
+|---|---|---|
+| `valid?`, `verify!`, `Verifier`, `signature_present?` | yes | yes |
+| `sign` into a template the document already holds | yes | yes, one template per call |
+| `sign` that builds the template, `sign!`, `Signer#template` | yes | raises `NokogiriRequired` |
+| `Verification#signed?`, `#at_signed`, `#signed_nodes` | yes | raises; `#covers_root?` still answers |
+| Custom `Nokogiri::XML::Schema`, `signature:` XPath, `resolver:`, XAdES | yes | raises `NokogiriRequired` |
+
+`HankoXml.capabilities` reports the same thing at runtime. On Linux with
+system libraries, whichever of hanko_xml and Nokogiri loads first decides which
+libxml2 the other runs on, so HankoXml leaves the load order to you.
+
+## Usage
+
+### 1. The Nokogiri API (Recommended)
+
+HankoXml can extend Nokogiri directly, making signing and verifying incredibly
+ergonomic. The extension is opt-in: `require "hanko_xml"` alone does not touch
+Nokogiri's classes, and `require "hanko_xml/nokogiri_ext"` adds `#sign`,
+`#sign!`, `#signature_valid?`, `#signatures` and `#signature_present?` to
+`Nokogiri::XML::Document` and `Node`.
+
+```ruby
+require "nokogiri"
+require "hanko_xml"
+require "hanko_xml/nokogiri_ext"
+
+doc = Nokogiri::XML(File.read("document.xml"))
+private_key = File.read("private.pem")
+certificate = File.read("public.crt")
+
+# Sign the document in place
+doc.sign!(key: private_key, certificate: certificate)
+
+# Safely serialize without destroying the signature bytes
+File.write("signed.xml", doc.to_xml(save_with: Nokogiri::XML::Node::SaveOptions::AS_XML))
+
+# Verify it later
+signed_doc = Nokogiri::XML(File.read("signed.xml"))
+if signed_doc.signature_valid?(certificate: certificate)
+  puts "Signature is valid!"
+end
+```
+
+### 2. The Module API
+
+If you prefer not to load the Nokogiri extension, use the top-level module:
+
+#### Verification
+
+This works with or without Nokogiri:
+
+```ruby
+require "hanko_xml"
+require "pathname"
+
+xml = File.read("signed.xml")
+
+# Raises HankoXml::VerificationError if the signature is invalid or tampered with
+result = HankoXml.verify!(xml, certificate: Pathname("public.crt"))
+
+puts result.valid? # => true
+```
+
+#### Signing (Immutable)
+```ruby
+# Returns a safe `SignedDocument` wrapper without mutating the original
+# A String is PEM content, not a filename: pass files as Pathname (or File.read them).
+signed_doc = HankoXml.sign(xml, key: Pathname("private.pem"), certificate: Pathname("public.crt"))
+
+puts signed_doc.to_s
+```
+
+### Defending against XML Signature Wrapping (XSW)
+
+A signature is only secure if it actually signed the data you are looking at. Attackers often wrap or move the `<Signature>` block to trick naive verifiers. HankoXml provides a structural `signed?` check on the verification result to prove a specific node was cryptographically covered by the digest.
+
+```ruby
+result = HankoXml.verify!(doc, certificate: cert)
+
+# Find the critical data in your document
+payload = doc.at_xpath("//Invoice")
+
+# Ensure the attacker didn't move it outside the signed block
+unless result.signed?(payload)
+  raise "XSW Attack Detected: The invoice was tampered with!"
+end
+```
+
+### Trust Anchors & Verification Options
+
+You can verify signatures against multiple certificates, strict schemas, or specific validation times.
+
+```ruby
+HankoXml.verify!(
+  doc,
+  # Pass a single cert, an array of certs, an OpenSSL::X509::Store, or a mapping of <KeyName>s
+  store: my_trusted_ca_store,
+  
+  # Ensure the certificate was valid at a specific time
+  verification_time: Time.parse("2023-01-01"),
+  
+  # Pre-validate the <Signature> structure against the W3C XSD to prevent parser exploits
+  schema: :default,
+  
+  # Enforce strict security policies (no SHA-1, no external references)
+  policy: HankoXml::Policy.strict
+)
+```
+
+## Contributing
+
+Bug reports and pull requests are welcome on GitHub at https://github.com/danimaribeiro/HankoXml.
+
+`bundle exec rake compile spec` by default builds the Rust extension against
+your system's `libxmlsec1` (see "Building from source" above), which is fine
+for day-to-day development. But the system library's build configuration can
+differ from the pinned, vendored `libxmlsec1` that CI and the released gem
+actually use — on macOS with Homebrew's `libxmlsec1`, this has been observed
+to make some native URI-restriction and `KeyValue` specs fail or hang. Before
+relying on a full local `bundle exec rspec` run (e.g. to validate a security
+fix), rebuild against the vendored library instead:
+
+```sh
+HANKO_XML_VENDOR=1 bundle exec rake compile spec
+```
+
+See [VENDORING.md](VENDORING.md) for details on what gets vendored and why.
+
+## License
+
+The gem is available as open source under the terms of the [MIT License](https://opensource.org/licenses/MIT).

data/THIRD_PARTY_LICENSES.md

@@ -0,0 +1,392 @@
+# Third-party licenses for vendored platform gems
+
+The precompiled platform gems for `hanko_xml` statically vendor these upstream
+libraries from `dependencies.yml`:
+
+- libxml2 2.15.4 — MIT
+- xmlsec1 1.3.12 — MIT
+- OpenSSL 3.5.9 — Apache-2.0
+
+The source gem normally links system libraries instead of redistributing these
+copies, but the platform gems ship the vendored code and therefore ship the
+corresponding license and notice text here as well.
+
+## libxml2 2.15.4
+
+Source: `GNOME/libxml2`, tag `v2.15.4`, file `Copyright`
+
+```text
+Except where otherwise noted in the source code (e.g. the files dict.c and
+list.c, which are covered by a similar licence but with different Copyright
+notices) all the files are:
+
+ Copyright (C) 1998-2012 Daniel Veillard.  All Rights Reserved.
+ Copyright (C) The Libxml2 Contributors.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is fur-
+nished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FIT-
+NESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.  IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.
+```
+
+## xmlsec1 1.3.12
+
+Source: `lsh123/xmlsec`, tag `1.3.12`, file `Copyright`
+
+```text
+------------------------------------------------------------------------------
+xmlsec, xmlsec-openssl, xmlsec-gnutls, xmlsec-gcrypt libraries
+------------------------------------------------------------------------------
+
+Copyright (C) 2002-2026 Aleksey Sanin <aleksey@aleksey.com>. All Rights Reserved.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is fur-
+nished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FIT-
+NESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.  IN NO EVENT SHALL THE
+ALEKSEY SANIN BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER
+IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CON-
+NECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+
+Except as contained in this notice, the name of Aleksey Sanin shall not
+be used in advertising or otherwise to promote the sale, use or other deal-
+ings in this Software without prior written authorization from him.
+
+------------------------------------------------------------------------------
+xmlsec-nss library
+------------------------------------------------------------------------------
+Copyright (C) 2002-2026 Aleksey Sanin <aleksey@aleksey.com>. All Rights Reserved.
+Copyright (c) 2003 America Online, Inc.  All rights reserved.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is fur-
+nished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+Portions of the Software were created using source code and/or APIs
+governed by the Mozilla Public License (MPL). The MPL is available
+at http://www.mozilla.org/MPL/MPL-1.1.html. The MPL permits such
+portions to be distributed with code not governed by MPL, as long
+as the requirements of MPL are fulfilled for such portions.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FIT-
+NESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.  IN NO EVENT SHALL THE
+ALEKSEY SANIN BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER
+IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CON-
+NECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+
+Except as contained in this notice, the name of Aleksey Sanin shall not
+be used in advertising or otherwise to promote the sale, use or other deal-
+ings in this Software without prior written authorization from him.
+
+
+------------------------------------------------------------------------------
+xmlsec-mscrypto library
+------------------------------------------------------------------------------
+
+Copyright (C) 2002-2026 Aleksey Sanin <aleksey@aleksey.com>. All Rights Reserved.
+Copyright (C) 2003 Cordys R&D BV, All rights reserved.
+Copyright (C) 2007 Roumen Petrov.
+Copyright (c) 2005-2006 Cryptocom LTD (http://www.cryptocom.ru).
+
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is fur-
+nished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FIT-
+NESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.  IN NO EVENT SHALL THE
+ALEKSEY SANIN BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER
+IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CON-
+NECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+
+Except as contained in this notice, the name of Aleksey Sanin shall not
+be used in advertising or otherwise to promote the sale, use or other deal-
+ings in this Software without prior written authorization from him.
+
+
+------------------------------------------------------------------------------
+xmlsec-mscng library
+------------------------------------------------------------------------------
+
+Copyright (C) 2018-2026 Aleksey Sanin. All Rights Reserved.
+Copyright (C) 2018 Miklos Vajna. All Rights Reserved.
+
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is fur-
+nished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FIT-
+NESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.  IN NO EVENT SHALL THE
+ALEKSEY SANIN BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER
+IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CON-
+NECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+
+Except as contained in this notice, the name of Aleksey Sanin shall not
+be used in advertising or otherwise to promote the sale, use or other deal-
+ings in this Software without prior written authorization from him.
+
+------------------------------------------------------------------------------
+Additional copyright information
+------------------------------------------------------------------------------
+See individual source files for any additional copyright information
+
+
+------------------------------------------------------------------------------
+References
+------------------------------------------------------------------------------
+* AOL
+http://www.aleksey.com/pipermail/xmlsec/2003/005488.html
+http://www.aleksey.com/pipermail/xmlsec/attachments/20030729/0e25648e/attachment.htm
+
+* Cordys R&D BV
+http://www.aleksey.com/pipermail/xmlsec/2003/005581.html
+
+* Cryptocom LTD
+http://www.aleksey.com/pipermail/xmlsec/2006/007410.html
+```
+
+The `1.3.12` release also includes a top-level `COPYING` file containing:
+
+```text
+See Copyright file for information about the copyright
+```
+
+## OpenSSL 3.5.9
+
+Source: `openssl/openssl`, tag `openssl-3.5.9`, file `LICENSE.txt`
+
+```text
+                                 Apache License
+                           Version 2.0, January 2004
+                        https://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+```
+
+At the pinned `openssl-3.5.9` ref, the upstream repository does not include a
+top-level `NOTICE` file. It does include `ACKNOWLEDGEMENTS.md`; the block
+below reproduces that upstream Markdown file verbatim as shipped:
+
+```text
+Acknowledgements
+================
+
+Please see our [Thanks!][] page for the current acknowledgements.
+
+[Thanks!]: https://www.openssl.org/community/thanks.html
+```