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

Enable os_entropy on SGX + std #28

Open
jethrogb opened this issue Jan 24, 2019 · 2 comments
Open

Enable os_entropy on SGX + std #28

jethrogb opened this issue Jan 24, 2019 · 2 comments

Comments

@jethrogb
Copy link
Member

If you compile for the x86_64-fortanix-unknown-sgx target, the public API looks differently in that os_entropy is not available. This should be fixed.

@jack-fortanix
Copy link
Contributor

For SGX should we just declare os_entropy == rdrand?

@jethrogb
Copy link
Member Author

Well, yes, but note that it's supposed to map to the underlying MbedTLS API and that there is some additional APIs that are not "just RDRAND"

mcr pushed a commit to mcr/rust-mbedtls that referenced this issue Aug 10, 2023
This deprecates timeout_read() and timeout_write() in favor of
timeout(). The new timeout method on Request takes a Duration instead
of a number of milliseconds, and is measured against overall request
time, not per-read time.

Once a request is started, the timeout is turned into a deadline
specific to that call. The deadline is used in conjunction with the
new DeadlineStream class, which sets a timeout on each read according
to the remaining time for the request. Once the request is done,
the DeadlineStream is unwrapped via .into::<Stream>() to become
an undecorated Stream again for return to the pool. Timeouts on the
stream are unset at this point.

Still to be done:

Add a setting on Agent for default timeout.
Change header-writing code to apply overall deadline rather than
per-write timeout.
Fixes fortanix#28.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants