3 ms·
In addition to squiguy7's point, I'd add that A: it may not be clear if this is your only contact with ntpsec.org [1], but this is actually a fork of the classi
by jerf 10y ago
In addition to squiguy7's point, I'd add that A: it may not be clear if this is your only contact with ntpsec.org [1], but this is actually a fork of the classic ntp, so they may be more willing to abandon some older architectures to produce a more secure product going forward than the core NTP project would and B: the older versions will still be around even so.
Also, it has been suggested by some experiences that older architectures often end up getting supported past when they really should be stopped out of sheer inertia, though I'm not having luck digging up the articles that prompt me to say this. Are there that many systems out there running ntp that can't run Go and/or Rust, and if there are, are there enough to be worth bending the project around? If the people running those things care, perhaps they should fork the project and maintain it themselves. Which is less harsh than it may sound, because they can still pull from upstream, and they probably just need to tread water rather than stay up with the latest & greatest.
(I should emphasize that the operative question is are there enough to be worth bending the project around, rather than whether there are any. Because there certainly are non-zero numbers of systems running ntpd that can't run Rust or Go. But who's going to pay to maintain them? Especially if classic ntp is still available?)
[1]: https://www.ntpsec.org/ https://www.ntpsec.org/
- falcolas 10y agoWell, it's not just older architectures which are not currently supported, it's architectures used in IOT devices, mainframes, and other non-commodity hardware. Specific to LLVM based languages, if it's not a priority to Apple (or the other big LLVM players), it infrequently gets done. Specific to IOT devices, I would personally love to see secure everyting. NTP, TLS, SSH, etc.
- TheAceOfHearts 10y agoIf it's a business requirement, they should hire engineers and contribute. Expecting free support seems unreasonable. There's a high cost for supporting and maintaining features, so somebody ends up having to pay for it.
- falcolas 10y agoTo be fair, I imagine most of those arch manufacturers simply think "embedded developers use C, we support C, job done." LLVM support would benefit the developers more, but they have their own budgets and constraints, which are probably not conducive to submitting and maintaining a LLVM plugin.
- kelnos 10y agoI expect that most of these older devices don't receive much in the way of software updates anyway, so the point is moot. For things that do receive updates, I would much rather see a secure NTP implementation that the majority of the world can use, even if a few parts of the long tail get excluded... and they still have the old versions of the C-based NTPsec they can use; I would also expect there to be a niche market arising for releasing security updates to it after the transition. (Specifically addressing IoT devices, IoT security is so abysmal in general that there are much easier ways to compromise one than targeting its NTP daemon, if it's even running one, and if it's even "bothering" to run a secure one like NTPsec.) Dropping support for things is certainly not a decision you make lightly, but sometimes the greater good demands it.
- eridius 10y agoThere is a lot of community interest in Rust with regards to running on embedded devices, so I wouldn't be so quick to point to IOT devices as a reason for not using Rust. That said, I don't know what the current state of support for these less popular architectures is. The official page for platform support is https://forge.rust-lang.org/platform-support.html https://forge.rust-lang.org/platform-support.html.
- mitchty 10y agoLLVM's biggest weakness right now is micro controller support like PIC/AVR. But its getting better: http://lists.llvm.org/pipermail/llvm-dev/2016-November/107177.html http://lists.llvm.org/pipermail/llvm-dev/2016-November/10717... That should hit most of the chips most people would care about. I presume rust would gain from the upstream LLVM support?
- eridius 10y agoYeah it should. AIUI Rust uses a fork of LLVM, but they should be regularly pulling in upstream changes (but I don't know how often this happens) as well as submitting their own changes back upstream.
- steveklabnik 10y agoWe do, in both directions.
- moosingin3space 10y agoIs there a technical or political issue preventing Rust from using upstream LLVM? Either way, is there a possible resolution on the horizon?
- steveklabnik 10y agoNope. You can use a stock LLVM if you want. Some tests might fail, since patches might not be in upstream yet. It's not really something to resolve; it's just the usual situation with a big dependency.
- pjmlp 10y agoWe are getting some piece of it with companies that still sell safe system programming languages (e.g. MikroElektronika, Astrobe), expose mostly via Java or its variants (e.g. Oracle, Aicas, Aonix, IBM, IS2T, Google), .NET (Microsoft).
- tedunangst 10y agoI'm never quite sure where MIPS and SPARC are in terms of llvm support. (And does llvm support automatically mean rust support?)
- binarycrusader 10y agoLLVM is generally usable on sparc, although a significant amount of optimisation work still needs to be done, and there are some specific variants/platforms that sparc is used by that need better support.
- protomyth 10y agoIs it likely that work will ever be done? Oracle is, well, Oracle, and Fujitsu used ARM instead of SPARC for their new supercomputer.
- cesarb 10y agoNo, LLVM support does not automatically mean Rust support, though it's a prerequisite for it. There are several small things which have to be defined in the Rust compiler. For instance, which registers are used for stack unwinding, and other ABI details.