openvpn3-session-acl(1)

πŸ“¦
version 27.1 Β· 3 versions
, in nixpkgs unstable, ubuntu stonking

✨ NAME ✨

openvpn3-session-acl β€” it's the OpenVPN 3 Linux Session Access Control Management bestie, and it's here to let your friends in (or kick them out) of a running VPN session πŸ’–


πŸ¦‹ SYNOPSIS πŸ¦‹

openvpn3 session-acl [OPTIONS]
openvpn3 session-acl -h | --help

🌸 DESCRIPTION 🌸

okay so picture this: every single running VPN session has its own Access Control List attached to it. own it, queen πŸ‘‘

and why do we care?? because that's literally how one session can be managed by multiple users. you can grant specific users β€” or like, every user β€” access to openvpn3 session-manage, openvpn3 session-stats and openvpn3 log for one specific VPN session. that's it, that's the power πŸ’…

all the options down below? they stack. use them together, no problem. And if you toss --show in there, it'll list out the current Access Control List after all your changes have been made β€” so it's giving "receipts" ✨

πŸŽ€ OPTIONS πŸŽ€

  • -h, --help β€” prints usage and help details right to your terminal 🫢
  • -o SESSION-DBUS-PATH, --path SESSION-DBUS-PATH β€” required, bestie, don't skip it. this is the D-Bus session path to the currently running session you want to manage. wanna find one? run openvpn3 sessions-list and it'll hand you a list of available session D-Bus paths 🌈
  • --session-path DBUS-PATH β€” just an alias for --path. same energy, different name πŸ’œ
  • -c CONFIG-NAME, --config CONFIG-NAME β€” you can use this instead of --path if you'd rather name the configuration profile. the CONFIG_NAME has to be the configuration name that was active when the session was started, ok?? available configuration names? once again: openvpn3 sessions-list 😌
  • -I INTERFACE, --interface INTERFACE β€” also usable instead of --path, but this time you're giving the tun interface name that OpenVPN 3 manages πŸ¦‹
  • -s, --show β€” shows the currently active ACL. the vibe check πŸ‘€
  • -G USER, --grant USER β€” grant that user read-only access to this VPN session. the USER argument can be either a UID or a username that belongs to the system. let them in, they're cool 🌸
  • -R USER, --revoke USER β€” revoke access on this VPN session for that user. again, USER is either a UID or a username belonging to the system. it's giving "we're done here" πŸ’€
  • --public-access BOOL β€” grants all users on the system access to manage this VPN session. fair warning: this effectively disables the more fine-grained access control you get from --grant. so like, pick a lane, bestie 😭 Valid argument values: true:, false.
  • --allow-log-access BOOL β€” by default, users you granted access to will not have access to the session log. set this option to true and your granted users can use openvpn3 log to pull real-time log events as they happen πŸ”₯ Valid argument values: true:, false.

πŸ’– SEE ALSO πŸ’–

openvpn3(1) openvpn3-log(1) openvpn3-session-manage(1) openvpn3-session-start(1) openvpn3-session-stats(1) openvpn3-sessions-list(1)


okay that's the whole page, you ate it fr fr πŸ‘‘ this was openvpn3-session-acl(1) from OpenVPN 3 Linux β€” go forth and manage those ACLs, icon πŸ’œβœ¨

πŸ“¦ where this page comes from