Feature #8794


NTP authentiction

Added by Tod L almost 3 years ago. Updated 18 days ago.

Target version:
Start date:
Due date:
% Done:


Estimated time:
Plus Target Version:
Release Notes:


NIST 800.53, specifically CM-6, requires network devices sync their time source using authenticated NTP. I'd like to request the NTP client in pfsense have an option to use authentication with NIST time servers. Cicso routers have this capability built in.

Actions #1

Updated by Jim Pingle almost 2 years ago

  • Category set to NTPD
Actions #2

Updated by Viktor Gurov over 1 year ago

Currently supported NTP auth hashes by vendors:
Juniper - MD5, SHA1, SHA256
Huawei - MD5, SHA256
Palo Alto - MD5, SHA1
Cisco, Avaya and most other vendors - MD5 only

Actions #3

Updated by Viktor Gurov 10 months ago

Server side authentication support:

Actions #4

Updated by Jim Pingle 10 months ago

  • Status changed from New to Pull Request Review
  • Target version set to 2.5.0
Actions #5

Updated by Renato Botelho 10 months ago

  • Status changed from Pull Request Review to Feedback
  • Assignee set to Renato Botelho
  • % Done changed from 0 to 100

PR has been merged. Thanks!

Actions #6

Updated by Steve Beaver 10 months ago

  • Assignee changed from Renato Botelho to Tod L
Actions #7

Updated by Viktor Gurov 8 months ago

  • Status changed from Feedback to New
  • Target version changed from 2.5.0 to CE-Next

after configuring ntpd authentication on Debian peer I can see packets with MAC:

Network Time Protocol (NTP Version 4, server)
    Flags: 0x24, Leap Indicator: no warning, Version number: NTP Version 4, Mode: server
    Peer Clock Stratum: secondary reference (3)
    Peer Polling Interval: 6 (64 sec)
    Peer Clock Precision: 0.000015 sec
    Root Delay: 0.0244598388671875 seconds
    Root Dispersion: 0.07177734375 seconds
    Reference ID:
    Reference Timestamp: Nov 28, 2020 16:00:20.461789665 UTC
    Origin Timestamp: Nov 28, 2020 16:09:03.511942520 UTC
    Receive Timestamp: Nov 28, 2020 16:09:03.515572186 UTC
    Transmit Timestamp: Nov 28, 2020 16:09:03.515697472 UTC
    Key ID: 00000001
    Message Authentication Code: 5e194bd30f46bb22789f80c8e8964ae7

linux peer 'ntpq -c as' output:

ind assid status  conf reach auth condition  last_event cnt
  1 59188  8811   yes  none  none    reject    mobilize  1
  2 59189  f31a   yes   yes   ok    outlier    sys_peer  1

pfSense 2.5.0.a.20201127.1850

pfSense NTP client still doesn't have authentication support, so I set the target version to

Actions #8

Updated by LamaZ . 4 months ago

Folks, I made a patch to the function system_ntp_configure() in the file /etc/inc/ to get this working. Tested on 21.02.2.

Patch pasted here:, see below auth field indicating ok on the ntp client on pfSense.

[21.02.2-RELEASE][admin@your-sweet-pfsense-server-name]/root: ntpq -pc as
     remote           refid      st t when poll reach   delay   offset  jitter
*  .NIST.           1 u    7   64  377   10.865   -0.019   0.738

ind assid status  conf reach auth condition  last_event cnt
  1 64816  f61a   yes   yes   ok   sys.peer    sys_peer  1


Actions #9

Updated by Steve Wheeler about 2 months ago

  • % Done changed from 100 to 50

The ntp client auth is yet to be implemented.

Actions #10

Updated by Ansley Barnes 18 days ago

Is it possible to add the option for SHA256 authentication? The underlying NTPd version appears to support it.


Also available in: Atom PDF