Frank Hunleth
Frank Hunleth
It's possible to set the time by using the `Date` header in HTTPS requests. While this won't be near as accurate as NTP, it should be plenty good for TLS...
While the use of NTP is convenient since it's included in Busybox, the NTP client only supports unauthenticated time and sends everything in the clear. See the [Linux Hardening Guide](https://madaidans-insecurities.github.io/guides/linux-hardening.html#time-synchronization)...
This function will tell you where the time comes from and can be used to determine the trustworthiness of time. Possible values: * `:build_time` * `:file_timestamp` * `:ntp` * `:rtc`...
I have no reason to believe that ntpd will hang, but if it does, then that would be catastrophic to maintaining good time. My reading of the code so far...
This is a rebased version of #91 with a couple updates.
See #105 for partial work towards this goal.
We currently manually build them. It looks like the toolchain Dockerfile works find on `arm64`, so it seems like it should be possible to get these to run on CircleCI.
Pelemay uses `nvcc` to generate CUDA code and would require it when targeting devices with NVidia GPUs (like the Jetson Nano) The path to `nvcc` should be set in the...
Labels would be super helpful. For example, `pin1_1` is `{"gpiochip0", 1}` and `pin1_3` is `{"gpiochip0", 3}`. See https://hexdocs.pm/grisp/grisp_gpio.html for naming.