-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy pathsupported-platforms.txt
33 lines (25 loc) · 1.51 KB
/
supported-platforms.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
= Platform support policy =
Our primary development platforms are Linux and FreeBSD.
We expect the NTPsec code to run with at most minor port changes on
Unixlike operating systems conforming to POSIX.1-2001 and ISO/IEC
9899:1999 (aka C99) and supporting ntp_gettime(2)/ntp_adjtime(2).
Python 2.5 is also required. We will fully support these platforms.
We have an actively maintained port to Mac OS X. Basic testing has been
performed and we are looking for people with OS X skill and interest to help
support this platform and perform detailed testing.
We intend to port to Windows, but that may not land in early releases. The work
requires we first sort out the threading code in NTPsec and then review the
Windows support and how it is integrated into the code base.
Hardware with 32 or 64 bits and any endianness is supported.
NTP Classic kept legacy support for a lot of very ancient Unix big
iron, and for other systems such as VMS. But increasing security
requires reducing complexity and attack surface. We have almost
completely removed legacy Unix support, and our direction is towards
dropping the remainder (along with unused or rarely-used features) in
order to achieve secure simplicity.
If you are a stranded legacy user with security and reliability
requirements strong enough that only NTPsec will do, our team is open
to working with active port maintainers who will take responsibility
for specific target environments not fully conformant to the
POSIX.1-2001/C99/Python-2.5 combination, or for exotic hardware.
// end