gh-Mbed-TLS/TF-PSA-Crypto

Watch

Fork 0

expand fuzzers, set-up safe fuzzing defaults #865

Open

vanhauser-thc wants to merge 1 commit from vanhauser-thc/development into development

vanhauser-thc commented

2026-08-05 04:49:30 -05:00

(Migrated from github.com)

This enhances the fuzzing harnesses and makes the config more friendly for fuzzing.

mbedtls development PR provided Mbed-TLS/mbedtls#10857

Please ping me if anything else is needed

This enhances the fuzzing harnesses and makes the config more friendly for fuzzing. - [X] **mbedtls development PR** provided Mbed-TLS/mbedtls#10857 Please ping me if anything else is needed

gilles-peskine-arm commented

2026-09-01 04:36:49 -05:00

(Migrated from github.com)

Thank you very much for these fuzzing improvements from an expert!

Unfortunately, we aren't allowed to use your contribution unless you declare that you agree with the Developer Certificate of Origin. To indicate your agreement, please amend your commit messages to add a signoff line (git rebase --signoff).

This applies to https://github.com/Mbed-TLS/mbedtls/pull/10857 as well.

Thank you very much for these fuzzing improvements from an expert! Unfortunately, we aren't allowed to use your contribution unless you declare that you agree with the [Developer Certificate of Origin](https://github.com/Mbed-TLS/TF-PSA-Crypto/blob/development/dco.txt). To indicate your agreement, please amend your commit messages to add a signoff line (`git rebase --signoff`). This applies to https://github.com/Mbed-TLS/mbedtls/pull/10857 as well.

vanhauser-thc commented

2026-09-02 03:09:18 -05:00

(Migrated from github.com)

I tried to signoff on the mbedtls PR, can you please check if this works? I have never done this before

gilles-peskine-arm commented

2026-09-02 03:38:02 -05:00

(Migrated from github.com)

I'm afraid not: the new dummy commit has a signoff but not the previous ones.

git reset --hard e854de019686fb3e0e957e40ddd4639986778b54 # to remove the dummy commit
git rebase --signoff
git force-push …

ought to do it.

I'm afraid not: the new dummy commit has a signoff but not the previous ones. ``` git reset --hard e854de019686fb3e0e957e40ddd4639986778b54 # to remove the dummy commit git rebase --signoff git force-push … ``` ought to do it.

This pull request is broken due to missing fork information.

View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.

git fetch -u origin 'vanhauser-thc/development:vanhauser-thc/development'

git switch 'vanhauser-thc/development'

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch 'development'

git merge --no-ff 'vanhauser-thc/development'

git switch 'vanhauser-thc/development'

git rebase 'development'

git switch 'development'

git merge --ff-only 'vanhauser-thc/development'

git switch 'vanhauser-thc/development'

git rebase 'development'

git switch 'development'

git merge --no-ff 'vanhauser-thc/development'

git switch 'development'

git merge --squash 'vanhauser-thc/development'

git switch 'development'

git merge --ff-only 'vanhauser-thc/development'

git switch 'development'

git merge 'vanhauser-thc/development'

git push origin 'development'

No reviewers

No milestone

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

gh-Mbed-TLS/TF-PSA-Crypto!865

No description provided.

Rows
Columns