This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | |||
cmd:ntp [2017/01/26 12:49] mcb30 |
cmd:ntp [2017/01/26 12:49] mcb30 |
||
---|---|---|---|
Line 33: | Line 33: | ||
===== Notes ===== | ===== Notes ===== | ||
- | You can use the ''[[:cfg:unixtime]]'' setting to obtain the current time after running the ''ntp'' command. | + | You can use the ''[[:cfg:unixtime]]'' setting to obtain the current UTC time after running the ''ntp'' command. |
iPXE uses the time and date primarily for validating [[:crypto|X.509 certificates]]. If your system clock is inaccurate, then iPXE may erroneously decide that a valid certificate has expired. You can use the ''ntp'' command to work around this problem, by fetching the time and date from an external NTP server. You should be aware that there is no security or authentication used for NTP, and so using the ''ntp'' command is effectively equivalent to ignoring the validity period of any X.509 certificates. | iPXE uses the time and date primarily for validating [[:crypto|X.509 certificates]]. If your system clock is inaccurate, then iPXE may erroneously decide that a valid certificate has expired. You can use the ''ntp'' command to work around this problem, by fetching the time and date from an external NTP server. You should be aware that there is no security or authentication used for NTP, and so using the ''ntp'' command is effectively equivalent to ignoring the validity period of any X.509 certificates. |