Added Dovecot project #3502
Merged
Added Dovecot project #3502
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…1) targets for readelf (with sample ELF file) and cxxfilt and (3) added my email to the project yaml. Fixed travis. Removed whitespace and fixed commit email for google cla Fixed travis. Removed whitespace and fixed commit email for google cla
mbarbella-chromium
suggested changes
Mar 13, 2020
catenacyber
reviewed
Mar 24, 2020
projects/dovecot/build.sh
Outdated
|
|
||
|
|
||
| # fuzz-imap-utf7 | ||
| clang $CFLAGS -DHAVE_CONFIG_H -I. -I../.. -I../../src/lib -I../../src/lib-test -I../../src/lib-charset -I../../src/lib-mail -std=gnu99 -fstack-protector-strong -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -Wno-duplicate-decl-specifier -Wstrict-aliasing=2 -MT test-imap-utf7.o -MD -MP -c -o fuzz-imap-utf7.o fuzz-imap-utf7.c |
There was a problem hiding this comment.
The fuzz targets should be built by make cf dovecot/core#117
This way, we do not have to modify oss-fuzz each time a new fuzz target is added to dovecot
There was a problem hiding this comment.
Sounds good - I will update once @sirainen finalises his thoughts on how it will be added in Dovecot!
…integrated the build process into the actual project.
Travis tests have failedHey @DavidKorczynski, 4th Build./infra/travis/travis_build.pyTravisBuddy Request Identifier: 70984ac0-6e96-11ea-bef5-ab2a7fe30e4a |
Travis tests have failedHey @DavidKorczynski, 3rd Build./infra/travis/travis_build.pyTravisBuddy Request Identifier: 5076a010-6e97-11ea-bef5-ab2a7fe30e4a |
Travis tests have failedHey @DavidKorczynski, 3rd Build./infra/travis/travis_build.pyTravisBuddy Request Identifier: 2e50fc50-6eca-11ea-bef5-ab2a7fe30e4a |
|
Looks like build.sh should begin with |
|
Hey @mbarbella-chromium ! Could you please review again? In the end the maintainers of Dovecot were very enthusiastic and did a great job integrating it nicely into the Dovecot building process (dovecot/core#116 and https://github.com/dovecot/core/pull/117/files). This should be a good setup for future fuzzing of Dovecot too! |
|
Hey! I found dovecot was not #402 marked as solved - @DavidKorczynski maybe worth saying it there :))) |
44 tasks
yay, marked as Done! Thanks a lot! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I added the Dovecot project with three initial fuzzers. Please follow the thread on Dovecots repo about progress: dovecot/core#116
By the looks of it they will provide an email soon that can get the bug reports, then I will update here. I made this pull request so we can follow progress both places.