RADIUS(8)

πŸ’… RADIUS(8) β€” like, the whole manual page, bestie

okay so this is radius from the InterNetNews Documentation crew β€” an nnrpd RADIUS password authenticator, and honestly she's a whole vibe. come sit with me, we're doing a vibe check on the entire page πŸŽ€


✨ NAME ✨

radius β€” the nnrpd RADIUS password authenticator. her job? passwords. RADIUS ones. slay πŸ’…


🌸 SYNOPSIS 🌸

radius [-h] [-f config]

that's it. that's the whole invocation. short, iconic, no notes ✨


πŸ¦‹ DESCRIPTION πŸ¦‹

okay so radius is an nnrpd authenticator. what that means is: nnrpd hands her a username and a password (which nnrpd itself got from a reader connection), and she goes and tries to authenticate that username-and-password combo against a RADIUS server. that's the whole arc. no cap 🫢

if you wanna know how to actually configure an nnrpd authenticator, go read readers.conf(5) β€” she's not gonna explain it twice. this tool is highkey useful for a site that already does user authentication via RADIUS and now wants to authenticate news reading connections too. like, you already have the RADIUS setup, why not let it do the news thing as well? exactly. main character energy 🌈

by default, radius reads pathetc/inn-radius.conf for configuration info. but if that file isn't giving what it needs to give, you can point her at a totally different config file with -f. the config file format is described over in inn-radius.conf(5), so go look there for the deets πŸ’–


πŸŽ€ OPTIONS πŸŽ€

  • -f config β€” read config instead of pathetc/inn-radius.conf for configuration information. your file, your rules, your era πŸ‘‘
  • -h β€” print out a usage message and exit. respect, honestly β€” sometimes you just wanna know your options πŸ¦‹

⭐ EXAMPLE ⭐

here's a readers.conf(5) fragment that tells nnrpd to authenticate all the connections using this authenticator. literally all of them. periodt:

auth radius {
    auth: radius
    default: <FAIL>
    default-domain: example.com
}

so what happens here? "@example.com" gets appended to the user-supplied identity β€” cute little domain addition, love that for you 🌸 β€” and if RADIUS authentication fails, the user gets assigned an identity of "<FAIL>@example.com". yeah. not the slay ending, but at least it's an honest one 😭


πŸ’€ BUGS πŸ’€

ngl, there have been reports that this authenticator doesn't work with Ascend RADIUS servers. it does work with Cistron RADIUS servers though, so there's that 🫢. it's also believed to work with Livingston's RADIUS server β€” "believed" is doing a lot of work in that sentence, bestie, just saying πŸ™ˆ.

contributions to make it work better with different types of RADIUS servers would be gratefully accepted β€” like, genuinely, come through, the maintainers want your help πŸ’œ

⚠️ also important: this code has not been audited against the RADIUS protocol and may not implement it correctly. that's a real caveat, not a bit. read it again. πŸ”₯

🧚 HISTORY 🧚

the RADIUS authenticator was originally written by Aidan Cully β€” king behavior πŸ‘‘. and this documentation was written by Russ Allbery <eagle@eyrie.org>. iconic, both of them πŸŽ€


πŸ‘‘ SEE ALSO πŸ‘‘


and that's the page, bestie πŸ’– this was INN 2.7.4, dated 2022-07-10, and you can find her filed under RADIUS(8). go authenticate something. slay πŸ¦‹βœ¨

πŸ“¦ where this page comes from
  • arch rolling: inn 2.7.4-4 Β· ISC
  • epel 10: inn 2.7.4-5.el10_3 Β· ISC AND BSD-3-Clause AND BSD-4-Clause AND FSFAP AND (GPL-1.0-or-later OR Artistic-1.0-Perl) AND GPL-3.0-or-later WITH Bison-exception-2.2 AND LicenseRef-Fedora-Public-Domain AND MIT AND NTP
  • πŸ’– girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms