search

intel / intel-ipsec-mb

Intel(R) Multi-Buffer Crypto for IPSec
BSD 3-Clause "New" or "Revised" License
288 stars 88 forks source link

Mayhem #103

Closed ykyle01 closed 2 years ago

ykyle01 commented 2 years ago

Description

Affected parts

Motivation and Context

How Has This Been Tested?

Types of changes

Checklist:

tkanteck commented 2 years ago

Hey @ykyle01,

Thanks for the PR.

Could you shed some light on how this works? I am not familiar with Mayhem. How is it supposed to be triggered on every push or pull request? Is it some sort of clever smoke fuzz test infrastructure?

Is Mayhem free to use for opensource projects?

It also seems that commit 4f2b4ec9d627e2d8650d6890e550340b19c8c3d4 and 3ab5717e05ca134abbce305c1673f7c72adb9643 could be squashed together (the last one corrects the former one).

ykyle01 commented 2 years ago

Hello!

It will be triggered on every push and pull request through Github actions, which will build a Docker image and analyze it with Mayhem on every code change, where Mayhem essentially does all the fuzz testing. I am not sure if Mayhem is free to use for open source projects. Sorry that PR was an accident, but I do think Mayhem is interesting. You should probably not merge that PR. I was just testing a bit with Mayhem on public repositories for a school hackathon.

Best, Kyle

On Fri, Apr 8, 2022 at 11:21 AM Tomasz Kantecki @.***> wrote:

Hey @ykyle01 https://github.com/ykyle01,

Thanks for the PR.

Could you shed some light on how this works? I am not familiar with Mayhem. How is it supposed to be triggered on every push or pull request? Is it some sort of clever smoke fuzz test infrastructure?

Is Mayhem free to use for opensource projects?

It also seems that commit 4f2b4ec https://github.com/intel/intel-ipsec-mb/commit/4f2b4ec9d627e2d8650d6890e550340b19c8c3d4 and 3ab5717 https://github.com/intel/intel-ipsec-mb/commit/3ab5717e05ca134abbce305c1673f7c72adb9643 could be squashed together (the last one corrects the former one).

— Reply to this email directly, view it on GitHub https://github.com/intel/intel-ipsec-mb/pull/103#issuecomment-1092997725, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALIC6I37C3PNVKZA2JNVCRDVEBFHLANCNFSM5SLULWAA . You are receiving this because you were mentioned.Message ID: @.***>

tkanteck commented 2 years ago

Hello Kyle, Thanks for coming back with the info. I agree with you that it is interesting and worth learning more about. For now, I am going to close this PR. Is that OK? Thanks, Tomasz

ykyle01 commented 2 years ago

Hi Tomas’s,

Sounds good! Sorry about this.

Best, Kyle

On Apr 11, 2022, at 6:22 AM, Tomasz Kantecki @.***> wrote:

 Hello Kyle, Thanks for coming back with the info. I agree with you that it is interesting and worth learning more about. For now, I am going to close this PR. Is that OK? Thanks, Tomasz

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.

tkanteck commented 2 years ago

No problem at all Kyle. Thanks

ykyle01 commented 1 year ago

Here is some extra resources: https://github.com/mayhemheroes/hackathon-resources

On Sat, Apr 9, 2022 at 3:33 PM Kyle Yang @.***> wrote:

Hello!

It will be triggered on every push and pull request through Github actions, which will build a Docker image and analyze it with Mayhem on every code change, where Mayhem essentially does all the fuzz testing. I am not sure if Mayhem is free to use for open source projects. Sorry that PR was an accident, but I do think Mayhem is interesting. You should probably not merge that PR. I was just testing a bit with Mayhem on public repositories for a school hackathon.

Best, Kyle

On Fri, Apr 8, 2022 at 11:21 AM Tomasz Kantecki @.***> wrote:

Hey @ykyle01 https://github.com/ykyle01,

Thanks for the PR.

Could you shed some light on how this works? I am not familiar with Mayhem. How is it supposed to be triggered on every push or pull request? Is it some sort of clever smoke fuzz test infrastructure?

Is Mayhem free to use for opensource projects?

It also seems that commit 4f2b4ec https://github.com/intel/intel-ipsec-mb/commit/4f2b4ec9d627e2d8650d6890e550340b19c8c3d4 and 3ab5717 https://github.com/intel/intel-ipsec-mb/commit/3ab5717e05ca134abbce305c1673f7c72adb9643 could be squashed together (the last one corrects the former one).

— Reply to this email directly, view it on GitHub https://github.com/intel/intel-ipsec-mb/pull/103#issuecomment-1092997725, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALIC6I37C3PNVKZA2JNVCRDVEBFHLANCNFSM5SLULWAA . You are receiving this because you were mentioned.Message ID: @.***>