<package-name>: <short description>

Open
#31,296 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
40/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
linux

Research direction

The payload names no files, so start with the tinyproxy and nordvpnlite package directories and their init or firewall configuration. Confirm the running Tinyproxy's effective UID on a device, then check whether it is 65534. Done means a dedicated tinyproxy account with its own UID, nftables OUTPUT rules that match that UID, and fail-closed behaviour that survives reboot and firewall reload.

Written by the indexing model from the issue text.

Description

bug
Package Name

tinyproxy, nordvpnlite

Maintainer

@openwrt

OpenWrt Version

25.12.6

OpenWrt Target/Subtarget

mediatek/filogic

Steps to Reproduce

Observed behavior and configuration

The default Tinyproxy runtime identity is nobody (UID 65534). The inspected nftables rules were scoped to UID 65534:

meta skuid 65534 oifname "lo" accept comment "Tinyproxy DNS loopback"
meta skuid 65534 oifname "nordvpnobonlite" accept comment "Tinyproxy VPN only"
meta skuid 65534 drop comment "Tinyproxy fail closed"

Because UID 65534 is the shared nobody identity, these rules do not uniquely identify Tinyproxy. Other processes using that UID are subject to the same restrictions, and the rules cannot provide a dedicated per-proxy security boundary. The earlier investigation also identified the need to ensure the rules match Tinyproxy's actual post-privilege-drop UID.

Expected behavior

Tinyproxy should run under its own dedicated tinyproxy account, whose UID is not 65534. Only that account's outbound traffic should be permitted to use loopback for DNS and the NordVPN interface for Internet access. If VPN egress is unavailable, Tinyproxy must fail closed without falling back to WAN.

Recommended correction

  1. Create a dedicated tinyproxy user (and group if required by the package) with a UID other than 65534.
  2. Configure Tinyproxy to use that account after startup/privilege drop, and verify its effective UID on the running system.
  3. Update all Tinyproxy-specific nftables OUTPUT rules to match the dedicated UID, not 65534. Keep the loopback DNS allow, NordVPN-interface allow, and fail-closed drop scoped to that UID.
  4. Verify that unrelated services running as nobody are no longer captured by the Tinyproxy-specific policy.
  5. Test with VPN active: users with UID 65535 gets no VPN connection, users with other UID can access the VPN connection.
  6. Check that the account, Tinyproxy privilege-drop setting, and firewall rules persist across reboot and firewall reload.

if it help https://buymeacoffee.com/andrewlev

Actual Behaviour

Tinyproxy runs by default as user nobody, UID 65534. On this OpenWrt router, nftables OUTPUT rules use the process UID to restrict Tinyproxy to loopback DNS and the NordVPN interface, with a fail-closed drop for other egress. Using the shared nobody UID for that policy is the wrong identity boundary: unrelated processes can also run as nobody, while the proxy does not have its own dedicated account.

The solution is to create a dedicated tinyproxy user with a UID other than 65534, configure Tinyproxy to drop privileges to that account, and make the VPN-only / fail-closed nftables rules match the dedicated UID.

Environment

  • Device: OpenWrt router
  • OpenWrt Version: 25.12.6
  • Proxy: Tinyproxy
  • VPN interface: nordvpnlite
  • Firewall: nftables custom OUTPUT chain
  • Docker-Container client: at 172.30.200.2; proxy endpoint 172.30.200.1:8888
Confirmation Checklist
Dominant language
Makefile
Stars
4.7k
Forks
4k
Avg merge
2d 2h
Merged PRs (30d)
251

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from openwrt/packages

All issues in openwrt/packages

Similar issues

More Networking issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.