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.

Sign up for GitHub

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

Jump to bottom

Create a tool for generating fuzz seeds #165

Open
haowqs opened this issue Mar 21, 2022 · 2 comments
Open

Create a tool for generating fuzz seeds #165

haowqs opened this issue Mar 21, 2022 · 2 comments
Assignees
@liuw1

Comments

@haowqs
Copy link
Contributor

haowqs commented Mar 21, 2022

image

cfv.bin
fv_buffer
hob_buffer
@liuw1
Copy link
Contributor

liuw1 commented May 19, 2022

I will take this issue.

@jyao1 jyao1 assigned liuw1 and unassigned haowqs May 19, 2022
gaojiaqi7 pushed a commit to gaojiaqi7/td-shim that referenced this issue Sep 14, 2022
@bors @sburton84
Merge confidential-containers#165
e7e9f98 
165: Unset _FORTIFY_SOURCE before setting it to fix error about redefinition r=jethrogb a=sburton84

When building for the `x86_64-fortanix-unknown-sgx` target in release mode I receive the following errors:

```
  <command-line>: error: "_FORTIFY_SOURCE" redefined [-Werror]
  <built-in>: note: this is the location of the previous definition
  <command-line>: error: "_FORTIFY_SOURCE" redefined [-Werror]
  <built-in>: note: this is the location of the previous definition
  cc1: all warnings being treated as errors
```

I think these would only be warnings but `MBEDTLS_FATAL_WARNINGS` defaults to `ON` which makes them into errors.

This patch fixes this by explicitly unsetting `_FORTIFY_SOURCE` before setting it to a new value.

Co-authored-by: Sean Burton <[email protected]>
@ariel-adam
Copy link
Member

@haowqs is this issue still relevant or can be closed?
If it's still relevant to what release do you think we should map it to (mid-November, end-December, mid-February etc...)?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@liuw1 liuw1

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@liuw1 @ariel-adam @haowqs