Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release: Botan 3.5.0 #225

Open
wants to merge 19 commits into
base: main
Choose a base branch
from
Open

Release: Botan 3.5.0 #225

wants to merge 19 commits into from

Conversation

reneme
Copy link
Collaborator

@reneme reneme commented Jul 11, 2024

Those will contain the finishing touches for the Botan 3.5.0 documents, after the library was released on Monday.

THIS PULL REQUEST WON'T BE MERGED, BUT THE release/3.5.0 BRANCH WILL LIVE ON. We'll close the pull request as soon as the documents are finalized. Nevertheless, there are changes to the cryptodoc and testspec in this pull request that have to be applied to main. We'll cherry-pick those as soon as we're ready to submit the documents.

TODO

  • Reminder: Cryptodoc Update for Botan 3.5.0 #214
  • Write up the summary chapters in the Audit Report
  • Write up summaries for the Audit Report topics
  • Update the "reviewed modules" list
    (perhaps also regard the new "experimental" and "deprecated" modules)
  • Review of audit entries regarding required modifications in the cryptodoc, testspec and so on
  • Final document review

@reneme reneme added the release label Jul 11, 2024
@reneme reneme added this to the Botan 3.5.0 milestone Jul 11, 2024
@reneme reneme self-assigned this Jul 11, 2024
@reneme reneme mentioned this pull request Jul 11, 2024
reneme and others added 3 commits July 18, 2024 10:27
This reverts the audit of a few patches that got picked up by the
auto-update bot but that don't belong into 3.5.0 anymore.
Comment on lines -103 to -122
# Add an explicit warning about Botan2 reaching end of life to readme [ci skip] (Jack Lloyd)
- commit: 0417790d0794d2c4382f4cfe6f87a88e33f3d21d # https://github.com/randombit/botan/commit/0417790d0794d2c4382f4cfe6f87a88e33f3d21d
classification: info
auditer: FAlbertDev

# Fix some spelling and formatting errors in the release notes [ci skip] (Jack Lloyd)
- commit: 722dde9d63b1c4b0b3f5b2fcd5851f3a24937c1a # https://github.com/randombit/botan/commit/722dde9d63b1c4b0b3f5b2fcd5851f3a24937c1a
classification: info
auditer: FAlbertDev

# Describe affected versions of name constraint bugs [ci skip] (Jack Lloyd)
- commit: 82ad62fea5629c1952aa112e3016b61e2c2a56b4 # https://github.com/randombit/botan/commit/82ad62fea5629c1952aa112e3016b61e2c2a56b4
classification: info
auditer: FAlbertDev

# Add 2.19.5 release notes [ci skip] (Jack Lloyd)
- commit: 939f200875f708f6b281b6aa3d38bc62a5b80355 # https://github.com/randombit/botan/commit/939f200875f708f6b281b6aa3d38bc62a5b80355
classification: info
auditer: FAlbertDev

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Those are removed because they were pulled in by the Auto-Update Bot but are not part of the 3.5.0 release.

Comment on lines +84 to +85
KMAC
----
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Originally, KMAC was introduced in Botan 3.2.0 but we failed to mention it in the cryptodoc. That may have been by design, I'm not sure anymore.

Nevertheless, now that we mention KMAC in the context of SP800-56Cr2, I guess it's just fair to also mention it explicitly in the MAC section of the cryptodoc.

Comment on lines -6 to -13
.. todo::

This documentation is outdated (and potentially too detailed).
It should be updated as soon as those pull requests are merged:

* https://github.com/randombit/botan/pull/4024

Until then, I've removed some of the source links to pass CI.
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This was postponed to 3.6.0 but randombit/botan#4024 was merged in the meantime. I.e. we'll have to tackle the overhaul of the Kyber/Dilthium chapters rather soon.

Comment on lines -744 to -760
**Vulnerability:** Botan 3.0.0-alpha1 and previous versions contained a bug in
the OCSP response validation where the authenticity of a spoofed response was not
properly checked. That allowed an attacker to forge OCSP responses for arbitrary
CAs that were considered authentic. That alone had the potential for DOS
attacks. Provided the attacker was in possession of a compromised subject
certificate, they would have been able to circumvent revocation checks and (keep)
impersonating the legitimate certificate owner (if no additional CRL-based
checks are performed).

This vulnerability was assigned CVE-2022-43705. For further details, please refer
to the `associated security advisory in Botan's GitHub repository
<https://github.com/randombit/botan/security/advisories/GHSA-4v9w-qvcq-6q7w>`_ or
the vulnerability description document provided along with this report.

**Conclusion:** With `the given patch <https://github.com/randombit/botan/pull/3067>`_
applied, Botan is no longer vulnerable to the described issue.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should have been removed from the document as early as the 3.1.0 release.

Copy link
Collaborator

@FAlbertDev FAlbertDev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Very nice! Some nits I found while proofreading. I'll fix them myself :)

Comment on lines 4 to 6
This section covers changes to the build system. Most notably, Botan now
requires at least XCode 15 to build on macOS and distinguishes between clang
fork of xcode and vanilla clang.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
This section covers changes to the build system. Most notably, Botan now
requires at least XCode 15 to build on macOS and distinguishes between clang
fork of xcode and vanilla clang.
This section covers changes to the build system. Most notably, Botan now
requires at least XCode 15 to build on macOS and distinguishes between the clang
fork of XCode and vanilla clang.

docs/audit_report/src/01_generic_changes.rst Outdated Show resolved Hide resolved
docs/cryptodoc/src/05_09_kyber.rst Outdated Show resolved Hide resolved
docs/audit_report/src/02_security_issues.rst Outdated Show resolved Hide resolved
docs/audit_report/src/02_security_issues.rst Outdated Show resolved Hide resolved
Copy link
Collaborator

@FAlbertDev FAlbertDev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For me, the release is ready to go :)

docs/audit_report/src/02_security_issues.rst Outdated Show resolved Hide resolved
@@ -1,5 +1,8 @@
title: HSS/LMS

description: |
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Somehow Philippe is missing as Code Author here in the PDF

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Currently the scripts don't take the Co-Authored-By: ... in the commits into account. Only the pull-request author. I'm guessing that's the reason it didn't pick up @lieser.

We could certainly look into this, though. Sucks that we're currently missing due credit. Perhaps GitHub even provides an API to resolve the email addresses in Co-Authored-By into a GitHub account? That'd certainly help.

Co-authored-by: Amos Treiber <40764707+atreiber94@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants