Skip to content

pppd: do not rely on have_route_to(0) during auth.#581

Open
jkroonza wants to merge 1 commit intoppp-project:masterfrom
jkroonza:always-assume-have-default
Open

pppd: do not rely on have_route_to(0) during auth.#581
jkroonza wants to merge 1 commit intoppp-project:masterfrom
jkroonza:always-assume-have-default

Conversation

@jkroonza
Copy link
Copy Markdown
Contributor

@jkroonza jkroonza commented Apr 2, 2026

#543 for reference.

Closes: #543

ppp-project#543 for reference.

Closes: ppp-project#543
Signed-off-by: Jaco Kroon <jaco@uls.co.za>
@jkroonza
Copy link
Copy Markdown
Contributor Author

jkroonza commented Apr 2, 2026

Impact assessment is surprisingly hard. The case that changes is where have_route_to(0) previously returned false for non-privileged users and neither auth nor noauth was set.

In other words, if we did have a default route, we'd suddenly require the remote side to auth, but if we did not we'd default to noauth (without allow_any_ip, meaning we could have multiple pppd's but only certain IPs would be available to the remote side). This feels counter-intuitive to me.

The motivation was that non-privileged users could establish internet connection without needing the privileged noauth option I believe. This use-case should be extremely rare nowadays, so just assume that a default route is already available, and force auth for all non-privileged invocations, meaning a system administrator would need to create a noauth peer for non-privileged users - typically managed via network manager nowadays anyway.

@Neustradamus
Copy link
Copy Markdown
Member

@paulusmack: What do you think about this @jkroonza PR?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

have_route_to auth protection is insufficient

2 participants