3 ms·
> do you anticipate ever having to change it or do you think it's pretty final at this point? We're not there yet, but defining a stable driver runtime is on o
by kerneis 5y ago
> do you anticipate ever having to change it or do you think it's pretty final at this point?
We're not there yet, but defining a stable driver runtime is on our roadmap for 2021:
https://fuchsia.dev/fuchsia-src/contribute/roadmap/2021/stable_driver_runtime https://fuchsia.dev/fuchsia-src/contribute/roadmap/2021/stab...
For non-driver interfaces, similar stability commitments may be shared over time, as the platform matures and we get more users.
> Are there any sort of security guarantees to protect against malicious services?
Fuchsia is based on capabilities, ie. handles to access resources, and those include memory regions. So a driver will only be able to access the parts of memory that you delegate to it. I don't know enough about drivers to provide a detailed security analysis, but I think it provides far more isolation than what you have in a monolithic kernel such as Linux.
- ryukafalz 5y ago> Fuchsia is based on capabilities, ie. handles to access resources, and those include memory regions. So a driver will only be able to access the parts of memory that you delegate to it. Ah thanks - Fuchsia drivers having capabilities to specific memory regions mostly answers my concerns at that level I think. Well, I guess I'll continue to be both interested in it from a technical perspective and conflicted about it based on licensing.