-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy pathsupported-platforms.html
58 lines (56 loc) · 2.48 KB
/
supported-platforms.html
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
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
<!DOCTYPE html>
<html lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta name="generator" content="AsciiDoc 8.6.9">
<title>Platform support policy</title>
<link rel="stylesheet" href="./asciidoc.css" type="text/css">
<script type="text/javascript" src="./asciidoc.js"></script>
<script type="text/javascript">
/*<![CDATA[*/
asciidoc.install();
/*]]>*/
</script>
</head>
<body class="article">
<div id="header">
<h1>Platform support policy</h1>
</div>
<div id="content">
<div id="preamble">
<div class="sectionbody">
<div class="paragraph"><p>Our primary development platforms are Linux and FreeBSD.</p></div>
<div class="paragraph"><p>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.</p></div>
<div class="paragraph"><p>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.</p></div>
<div class="paragraph"><p>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.</p></div>
<div class="paragraph"><p>Hardware with 32 or 64 bits and any endianness is supported.</p></div>
<div class="paragraph"><p>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.</p></div>
<div class="paragraph"><p>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.</p></div>
</div>
</div>
</div>
<div id="footnotes"><hr></div>
<div id="footer">
<div id="footer-text">
Last updated
2015-11-16 03:20:07 EST
</div>
</div>
</body>
</html>