bitlvl
EN

Port 464 Kerberos passwd · TCP and UDP

Kerberos password change (kpasswd) and the Microsoft kadmin variant. A client that can get tickets on 88 but cannot change passwords is usually missing this port in a firewall rule.

Port464
TransportTCP and UDP
ServiceKerberos passwd
CategoryAuthentication and directories
Rangewell-known (0–1023, needs root to bind on Unix)
EncryptedYes, always (TLS or equivalent)
ExposurePrivate network or VPN only

What runs on port 464

Kerberos password change (kpasswd) and the Microsoft kadmin variant. A client that can get tickets on 88 but cannot change passwords is usually missing this port in a firewall rule.

Software that uses it: Active Directory · MIT Kerberos kadmind · FreeIPA

Should port 464 be open?

Private network or VPN only. Nothing good comes from this port being reachable from the internet. Keep it on an internal network, reach it over a VPN or an SSH tunnel, and firewall it from everything that does not need it.

Check port 464

# on the host: is anything listening, and which process?
ss -ltnp 'sport = :464'
ss -lunp 'sport = :464'
sudo lsof -i :464

# from another machine: is it reachable?
nc -zv host 464
nmap -p 464 host
nc -zuv host 464
sudo nmap -sU -p 464 host
curl -v telnet://host:464      # raw TCP connect test, Ctrl-C to leave

A port that answers from the internet when it should not is the finding; nmap from a machine outside your network (or a VPS) is the honest test, because scans from inside the LAN pass the firewall you are trying to verify.

Allow or block port 464

# ufw (Ubuntu/Debian)
sudo ufw allow from 10.0.0.0/8 to any port 464 proto tcp
sudo ufw allow from 10.0.0.0/8 to any port 464 proto udp
sudo ufw deny 464/tcp
sudo ufw deny 464/udp

# nftables
nft add rule inet filter input ip saddr 10.0.0.0/8 meta l4proto { tcp, udp } th dport 464 accept
nft add rule inet filter input meta l4proto { tcp, udp } th dport 464 drop

# iptables (legacy)
iptables -A INPUT -p tcp --dport 464 -s 10.0.0.0/8 -j ACCEPT
iptables -A INPUT -p tcp --dport 464 -j DROP
iptables -A INPUT -p udp --dport 464 -s 10.0.0.0/8 -j ACCEPT
iptables -A INPUT -p udp --dport 464 -j DROP

# firewalld
sudo firewall-cmd --permanent --add-rich-rule='rule family=ipv4 source address=10.0.0.0/8 port port=464 protocol=tcp accept'

Replace 10.0.0.0/8 with the networks that need access. Allowing by source address is the rule that matters; "allow 464" with no source is just "open".

Related ports

Part of the port number reference. Ports are 16-bit numbers; see also the subnet calculator and the packet decoder, which shows ports inside TCP and UDP headers.

Questions

Is port 464 TCP or UDP?

Both. Kerberos passwd uses TCP and UDP on 464: see the notes above for when each is used.

Is port 464 encrypted?

Yes, always (TLS or equivalent). The port number does not make it safe by itself: certificate validation, authentication and patching still decide.

How do I check whether port 464 is open?

On the server, ss -ltnp (or -lunp for UDP) shows whether something listens on 464 and which process. From another machine, nc -zv host 464 or nmap -p 464 host tests reachability. "Open" in a scan means something answered; a firewall usually makes the port filtered (no answer) rather than closed (RST).

Can Kerberos passwd run on a different port?

Yes; the number is a convention, not a requirement. Changing it reduces log noise from scanners but does not add security, and every client, firewall rule and monitoring check then needs the new number. Keep the default unless you have a concrete reason.