rust - https://github.com/rust-lang/rust

Age	Commit message (Collapse)	Author	Lines
2024-01-11	std: begin moving platform support modules into `pal`	joboet	-93/+0

2021-12-12	Stabilize asm! and global_asm!	Amanieu d'Antras	-0/+2
	They are also removed from the prelude as per the decision in https://github.com/rust-lang/rust/issues/87228. stdarch and compiler-builtins are updated to work with the new, stable asm! and global_asm! macros.
2021-05-07	Revert SGX inline asm syntax	Jethro Beekman	-2/+2
	This was erroneously changed in #83387
2021-03-22	Fix asm! from AT&T to Intel syntax	Josh Stone	-1/+1

2021-03-22	Update the minimum external LLVM to 10	Josh Stone	-2/+1

2021-03-03	Auto merge of #76345 - okready:sgx-mem-range-overflow-checks, r=joshtriplett	bors	-8/+34
	Add is_enclave_range/is_user_range overflow checks Fixes #76343. This adds overflow checking to `is_enclave_range` and `is_user_range` in `sgx::os::fortanix_sgx::mem` in order to mitigate possible security issues with enclave code. It also accounts for an edge case where the memory range provided ends exactly at the end of the address space, where calculating `p + len` would overflow back to zero despite the range potentially being valid.
2020-11-12	Upgrading dlmalloc to 0.2.1	Raoul Strackx	-0/+12

2020-09-28	Prefer asm! in std - all in sgx module	Lzu Tao	-2/+9

2020-09-04	Add is_enclave_range/is_user_range overflow checks	Theodore Cipicchio	-8/+34
	Functions such as `is_enclave_range` and `is_user_range` in `sgx::os::fortanix_sgx::mem` are often used to make sure memory ranges passed to an enclave from untrusted code or passed to other trusted code functions are safe to use for their intended purpose. Currently, these functions do not perform any checks to make sure the range provided doesn't overflow when adding the range length to the base address. While debug builds will panic if overflow occurs, release builds will simply wrap the result, leading to false positive results for either function. The burden is placed on application authors to know to perform overflow checks on their own before calling these functions, which can easily lead to security vulnerabilities if omitted. Additionally, since such checks are performed in the Intel SGX SDK versions of these functions, developers migrating from Intel SGX SDK code may expect these functions to operate the same. This commit adds explicit overflow checking to `is_enclave_range` and `is_user_range`, returning `false` if overflow occurs in order to prevent misuse of invalid memory ranges. It also alters the checks to account for ranges that lie exactly at the end of the address space, where calculating `p + len` would overflow despite the range being valid.
2020-07-27	mv std libs to library/	mark	-0/+47