github-starred/pangolin
2
0
Fork 0
mirror of https://github.com/fosrl/pangolin.git synced 2026-05-06 00:22:42 -05:00
Code Issues 464 Packages Projects Releases 71 Wiki Activity

[GH-ISSUE #143] Whitelisting IPs to bypass authentication mechanisms #8072

New Issue
Closed
opened 2026-04-30 03:30:44 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-04-30 03:30:44 -05:00
Owner
Copy Link

Originally created by @miloschwartz on GitHub (Feb 1, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/143

Originally assigned to: @oschwartz10612, @miloschwartz on GitHub.

Discussed in https://github.com/orgs/fosrl/discussions/11

Originally posted by fr34kyn01535 January 7, 2025
Similar to how authentik allows trusted networks, it would be cool if we could whitelist networks that are trusted and bypass auth.
While most users don't have a fixed IP to whitelist I came up with a second idea here:
It would actually be quite cool if we can automatically select newt tunnel nodes / sites to whitelist, and their WAN address is added to that whitelist.

Originally created by @miloschwartz on GitHub (Feb 1, 2025). Original GitHub issue: https://github.com/fosrl/pangolin/issues/143 Originally assigned to: @oschwartz10612, @miloschwartz on GitHub. ### Discussed in https://github.com/orgs/fosrl/discussions/11 <div type='discussions-op-text'> <sup>Originally posted by **fr34kyn01535** January 7, 2025</sup> Similar to how authentik allows trusted networks, it would be cool if we could whitelist networks that are trusted and bypass auth. While most users don't have a fixed IP to whitelist I came up with a second idea here: It would actually be quite cool if we can automatically select newt tunnel nodes / sites to whitelist, and their WAN address is added to that whitelist. </div>
GiteaMirror added the new feature label 2026-04-30 03:30:44 -05:00
GiteaMirror commented 2026-04-30 03:30:48 -05:00
Author
Owner
Copy Link

@scroguard commented on GitHub (Feb 6, 2025):

to add to this - within other proxy packages i heavily make use of only allowing internal networks to access certain resources. it's a great additional step along with authentication to minimize the scope of who can access the proxied resource. being able to have something like "allow connections from specified private ip ranges, and deny the rest" would be very useful.

<!-- gh-comment-id:2641270093 --> @scroguard commented on GitHub (Feb 6, 2025): to add to this - within other proxy packages i heavily make use of only allowing internal networks to access certain resources. it's a great additional step along with authentication to minimize the scope of who can access the proxied resource. being able to have something like "allow connections from specified private ip ranges, and deny the rest" would be very useful.
GiteaMirror commented 2026-04-30 03:30:48 -05:00
Author
Owner
Copy Link

@synologyy commented on GitHub (Feb 9, 2025):

The same as an access list as in npm for WireGuard ip connections

Image

<!-- gh-comment-id:2646091510 --> @synologyy commented on GitHub (Feb 9, 2025): The same as an access list as in npm for WireGuard ip connections ![Image](https://github.com/user-attachments/assets/c6a35dd7-640d-455a-ac57-c574d9f4ec5c)
GiteaMirror commented 2026-04-30 03:30:49 -05:00
Author
Owner
Copy Link

@miloschwartz commented on GitHub (Feb 13, 2025):

Added in 1.0.0-beta.13

<!-- gh-comment-id:2657654859 --> @miloschwartz commented on GitHub (Feb 13, 2025): Added in [1.0.0-beta.13](https://github.com/fosrl/pangolin/releases/tag/1.0.0-beta.13)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
api
authentication
bug
config
dependencies
docker
documentation
enhancement
good first issue
help wanted
Improvement
Look Into
needs investigating
networking
new feature
non-critical bug
potential bug
pull-request
Mirrored from GitHub Pull Request
 question
reverse proxy
Security
stale
ui
wontfix
No Label new feature
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/pangolin#8072
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?