URONODE.PERMS(5)

💖 URONODE.PERMS 💖

okay bestie, so this is the uronode.perms manual page — it lives in the Linux Programmer's Manual section 5 (that's the file formats girlies 💅). Come sit, we're gonna read the permissions file together and it's gonna be so slay.

✨ NAME ✨

uronode.perms — the URONode permissions file. that's it. that's the whole name. iconic.

🌸 DESCRIPTION 🌸

So here's the tea 🫖: the uronode.perms file gets read at program startup, and URONode already knows some things about whoever's knocking at the door — their username (aka their call), the type of connection they came in on (could be AX.25, NET/ROM, ROSE, or TCP/IP), their peer's IP address (only matters for TCP/IP), and the port name (only matters for AX.25). It takes the first entry that matches all that info, and that's the entry that decides whether the user gets asked for a password and what permissions they get handed. first match wins, no take-backs, no re-dos. 💀

Every line in uronode.perms has to be one of exactly two things:

• a comment line, which starts with a # in the very first column (column one, bestie, not column two, she's picky), or
• a permission entry, in this exact format, where every field is separated by white space:

username type portname password permissions

Here's what each of those fields is actually doing 👇

• username — this gets matched against the user's username (their call) without the SSID. An asterisk (*) matches any username at all. queen of inclusivity.
• type — this gets matched against the type of connection the user came in on. the possible values are:
  • * — matches any type of connection.
  • ax25 — matches users coming in with AX.25 and FlexNet.
  • netrom — matches users coming in with NET/ROM.
  • rose — matches users coming in with ROSE.
  • local — matches TCP/IP connections where the user's host is in the "local" network, as defined in uronode.conf(5).
  • ampr — matches TCP/IP connections where the user's host is in amprnet (44.0.0.0/8).
  • inet — matches TCP/IP connections where the user's host is in neither the "local" network nor amprnet.
  • host — matches users starting URONode from the shell. 🐚
• portname — if the user is coming in with AX.25, this field gets matched against the local port name they're coming in via. An asterisk (*) matches any port name.
• password — if the previous three fields match and this field is not a single asterisk (*), the user gets asked for a password. that password is then matched against this field. (so * = no password prompt, any other value = you're getting interrogated 💅)
• permissions — this field is a bitmask of the operations the user is allowed to do. it's the sum of the values listed below:
• 1 — permits logging in even if no other permissions are given.
• 2 — permits outgoing AX.25 and Flexnet connects.
• 4 — permits outgoing NET/ROM connects.
• 8 — permits telneting to hosts in the "local" network as defined in uronode.conf(5).
• 16 — permits telneting to hosts in amprnet.
• 32 — permits telneting to hosts neither in the "local" network nor in amprnet.
• 64 — ANSI Color flag. Enable per interface to allow the user to have ANSI color graphics on their terminal. A * for the interface will flag color ON for all interfaces for that callsign. Suggested to leave OFF unless requested by the end user… but looks kewl in a shell terminal. 🌈✨
• 128 — permits outgoing ROSE connects.
• 256 — The no-escape flag. Disables the escape mechanism for this user.

🎀 FILES 🎀

• /usr/local/etc/ax25/uronode.perms

that's the one, bestie. that's where she lives. 🏠

🦋 SEE ALSO 🦋

• uronode(8)
• uronode.conf(5)
• axports(5)
• ax25(4)

and that's the whole page, bestie!! go forth and configure responsibly 💜

this lil' page came from the Linux manual, dated 28 April 1998, and she answers to the name URONODE.PERMS(5) — a true 90s icon, no cap. 🎀🦋💖