HPROP(8)

πŸ“¦
version 7.8.0 Β· 3 versions
, in alpine 3.22, alpine 3.23, alpine 3.24, debian bookworm, debian trixie, epel 10, epel 9, fedora 43, fedora 44, ubuntu jammy, ubuntu noble, ubuntu questing, ubuntu resolute, ubuntu stonking

πŸ’– HPROP πŸ’–

okay bestie, welcome to hprop from section 8 of the System Manager's Manual β€” it's the little tool that yeets your KDC database at other machines and honestly? she eats. πŸ’…


🌸 NAME 🌸

hprop β€” propagate the KDC database ✨


πŸŽ€ SYNOPSIS πŸŽ€

hprop [-m file | --master-key=file] [-d file | --database=file]
      [--source=heimdal|mit-dump] [-r string | --v4-realm=string] [-c
      cell | --cell=cell] [-k keytab | --keytab=keytab] [-R string |
      --v5-realm=string] [-D | --decrypt] [-E | --encrypt]
      [-n | --stdout] [-v | --verbose] [--version] [-h | --help]
      [host[:port]] ...

✨ DESCRIPTION ✨

so like, hprop takes a principal database in a format you specify and converts it into a stream of Heimdal database records. that stream can go two places: straight out to standard out, or β€” and this is the main character move β€” get propagated to an hpropd(8) server running on a different machine. πŸ¦‹

if you're propagating, she connects to all the hosts you listed on the command line by opening a TCP connection to port 754 (that's the service hprop) and sends the database in encrypted form. no cap, it's encrypted.

here's what she supports:

🌈 supported options 🌈

  • -m file, --master-key=file β€” where to find the master key, the one used to encrypt or decrypt keys with. πŸ”‘
  • -d file, --database=file β€” the database that's getting propagated, periodt.
  • --source=heimdal|mit-dump|krb4-dump|kaserver β€” tells her what kind of source database you're handing over. the alternatives include:
    • heimdal β€” a Heimdal database
    • mit-dump β€” a MIT Kerberos 5 dump file
  • -r string, --v4-realm=string β€” this one's in the synopsis, bestie, but the page never spells out what it does πŸ’€ so I'm not gonna make anything up about it.
  • -c cell, --cell=cell β€” same situation as -r, ngl: it's listed up in the synopsis, and that's all the page gives us. πŸ™ˆ
  • -k keytab, --keytab=keytab β€” the keytab to use for fetching the key that authenticates you to the propagation daemon(s). she uses the key hprop/hostname out of this keytab. the default is to fetch the key from the KDC database instead.
  • -R string, --v5-realm=string β€” local realm override. your realm, your rules. πŸ‘‘
  • -D, --decrypt β€” the encryption keys in the database can be either in clear or encrypted with a master key. this option transmits the database with unencrypted keys.
  • -E, --encrypt β€” this one transmits the database with encrypted keys. and heads up: this is the default if you don't supply any option. πŸ’–
  • -n, --stdout β€” dump the database on stdout, in a format that can be fed straight to hpropd. cute and pipeable. πŸŽ€
  • -v, --verbose β€” listed in the synopsis, no description on the page. fr fr, that's all we got.
  • --version β€” also synopsis-only, no description given.
  • -h, --help β€” you guessed it: synopsis-only, the page doesn't describe it.
  • [host[:port]] ... β€” one or more hosts to propagate to, optionally with a port. you can list as many as you want, hence the .... ✨

πŸ“ EXAMPLES πŸ“

the following will propagate a database to another machine (which should be running hpropd(8)):

$ hprop slave-1 slave-2

πŸ¦‹ SEE ALSO πŸ¦‹


and that's the whole vibe, bestie 🫢 this one's from HEIMDAL, dated December 8, 2004 β€” iconic behaviour, honestly, still serving after all these years. πŸ’œβœ¨

πŸ“¦ where this page comes from