commit | 9a4b2f9c4b2cd064e381befcc4a4996793c2ffc0 | [log] [tgz] |
---|---|---|
author | Aaron Green <aarongreen@google.com> | Thu Mar 15 19:56:45 2018 -0700 |
committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Fri Mar 16 23:17:41 2018 +0000 |
tree | c2c645ba63a1f4652d7094d3d436b0e4f7eea105 | |
parent | ec3b83e7307e23319bfa8f1d175107421df2b97e [diff] |
[crypto] Add AES128-CTR This CL adds AES128-CTR, which is MUCH faster than our current AES256-XTS implementation, but suffers from catastrophic nonce reuse and MUST be replaced. It's worth repeating: this is a TEMPORARY solution to unblock zxcrypt until we have a fast XTS implementation, or can substitute it with something else. ZX-1811 #comment Prerequisite to switching zxcrypt Change-Id: I63386bb2ece2348736b8fdd0e20556a84937258c
Zircon is the core platform that powers the Fuchsia OS. Zircon is composed of a microkernel (source in kernel/...) as well as a small set of userspace services, drivers, and libraries (source in system/...) necessary for the system to boot, talk to hardware, load userspace processes and run them, etc. Fuchsia builds a much larger OS on top of this foundation.
The canonical Zircon Git repository is located at: https://fuchsia.googlesource.com/zircon
A read-only mirror of the code is present at: https://github.com/fuchsia-mirror/zircon
The Zircon Kernel provides syscalls to manage processes, threads, virtual memory, inter-process communication, waiting on object state changes, and locking (via futexes).
Currently there are some temporary syscalls that have been used for early bringup work, which will be going away in the future as the long term syscall API/ABI surface is finalized. The expectation is that there will be about 100 syscalls.
Zircon syscalls are generally non-blocking. The wait_one, wait_many port_wait and thread sleep being the notable exceptions.
This page is a non-comprehensive index of the zircon documentation.