xous-core/services/dns/Cargo.toml

47 lines
1.6 KiB
TOML
Raw Permalink Normal View History

[package]
name = "dns"
version = "0.1.0"
authors = ["bunnie <bunnie@kosagi.com>"]
edition = "2018"
description = "Xous DNS resolver"
2022-06-10 13:36:53 +00:00
# Dependency versions enforced by Cargo.lock.
[dependencies]
2026-01-29 11:12:00 +00:00
xous = "0.9.70"
log-server = { package = "xous-api-log", version = "0.1.69" }
ticktimer-server = { package = "xous-api-ticktimer", version = "0.9.70" }
xous-names = { package = "xous-api-names", version = "0.9.71" }
log = "0.4.14"
num-derive = { version = "0.4.2", default-features = false }
num-traits = { version = "0.2.14", default-features = false }
net = { path = "../net" }
2026-01-29 11:12:00 +00:00
xous-ipc = "0.10.10"
rkyv = { version = "0.8.8", default-features = false, features = [
"std",
"alloc",
] }
trng = { path = "../trng" }
move time services into the DNS crate Time services are moved into the DNS crate so that the EC update thread can remain running and consuming resources. The problem is that we are out of connections in the connection table (it's limited to 32 total), and in order to allow a "force update" function for the EC we need to hold on to more connections than are possible. The "time" service is fairly self contained and could be moved elsewhere. It sort of logically fit in the status crate initially because the status crate manages preferences and displays the current time on the screen, but it's modular enough that we could put the service in any process space, at a minor trade-off of the time UX function being public. This was avoided for a long time because it could be a security risk but in the end the records that store time zone and offsets are in the PDDB, which are accessible to anyone who knows the names of these records, which is in the end equivalent to knowing the name of the time UX server. Thus the time UX server was made a dynamically registered "public" server with just one connection (so only a minor downgrade in security, the only vector exists in between boot and when the time servers connect up), and the time server itself was slotted into the DNS server's process space. The DNS server was chosen because the DNS service itself is very lightweight and will be unlikely to grow any heavier, so there is little risk in merging the time service into the DNS crate's process connection allocation.
2023-04-07 16:30:07 +00:00
# for the time UX wart
# time UX is stuck here because the DNS crate has a lot of connections available
# and the more logically grouped status crate has run out of resources.
llio = { path = "../llio" }
pddb = { path = "../pddb" }
chrono = { version = "0.4.33", default-features = false, features = ["std"] }
sntpc = { version = "0.3.1" } #, features = ["log"]
locales = { path = "../../locales" }
gam = { path = "../gam" }
susres = { path = "../../api/xous-api-susres", package = "xous-api-susres" }
userprefs = { path = "../../libs/userprefs" }
modals = { path = "../modals" }
2025-05-11 04:36:20 +00:00
precursor-hal = { path = "../../libs/precursor-hal" }
move time services into the DNS crate Time services are moved into the DNS crate so that the EC update thread can remain running and consuming resources. The problem is that we are out of connections in the connection table (it's limited to 32 total), and in order to allow a "force update" function for the EC we need to hold on to more connections than are possible. The "time" service is fairly self contained and could be moved elsewhere. It sort of logically fit in the status crate initially because the status crate manages preferences and displays the current time on the screen, but it's modular enough that we could put the service in any process space, at a minor trade-off of the time UX function being public. This was avoided for a long time because it could be a security risk but in the end the records that store time zone and offsets are in the PDDB, which are accessible to anyone who knows the names of these records, which is in the end equivalent to knowing the name of the time UX server. Thus the time UX server was made a dynamically registered "public" server with just one connection (so only a minor downgrade in security, the only vector exists in between boot and when the time servers connect up), and the time server itself was slotted into the DNS server's process space. The DNS server was chosen because the DNS service itself is very lightweight and will be unlikely to grow any heavier, so there is little risk in merging the time service into the DNS crate's process connection allocation.
2023-04-07 16:30:07 +00:00
2026-01-29 11:12:00 +00:00
utralib = { version = "0.1.27", optional = true, default-features = false }
[features]
precursor = ["utralib/precursor"]
hosted = ["utralib/hosted"]
renode = ["utralib/renode"]
minimal-testing = []
default = []