Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Request for Configuration of --verify-clients Parameter in Built-in DERP #1836

Open
zsio opened this issue Mar 18, 2024 · 11 comments
Open

Request for Configuration of --verify-clients Parameter in Built-in DERP #1836

zsio opened this issue Mar 18, 2024 · 11 comments
Labels
enhancement New feature or request no-stale-bot

Comments

@zsio
Copy link

zsio commented Mar 18, 2024

I am currently using the built-in DERP in Headscale and I noticed that the --verify-clients parameter is not configurable. This situation implies that the DERP I am using could be publicly accessible, which raises security concerns.

I am writing to inquire if there is a possibility to restrict the use of the built-in DERP to my clients only. This feature will greatly enhance the security of my connections and ensure that only authorized clients can use the DERP.

Looking forward to your response and potential solutions to this issue.

@zsio zsio added the enhancement New feature or request label Mar 18, 2024
@StudyingLover
Copy link

I am considering migrating from Tailscale to Headscale, but I hesitated when I suddenly notice this issue because I cannot tolerate others freeloading on my server without my permission.

@masterwishx
Copy link

Also interested in this future as using my own DERP server...

@ShadowJonathan
Copy link
Contributor

When researching tailscale I noticed this fairly subtle codepath being used for it, it requires an active embedded tailscale client to be sending peer updates to the derp server, apparantly.

Copy link
Contributor

This issue is stale because it has been open for 90 days with no activity.

@github-actions github-actions bot added the stale label Jun 27, 2024
@ShadowJonathan
Copy link
Contributor

No.

https://nostalebots.xyz/

@github-actions github-actions bot removed the stale label Jun 28, 2024
@zsio
Copy link
Author

zsio commented Aug 16, 2024

I would like to inquire if there is any new progress on this issue? This version hasn't been updated for more than a year. Will this problem be improved in the upcoming release?

@kradalby
Copy link
Collaborator

There are pull requests open, but we dont have the capacity to review and take in the amount of code for this release. I will try to review if to for the next cycle, but not sure if it will be included.

Copy link
Contributor

This issue is stale because it has been open for 90 days with no activity.

@zsio
Copy link
Author

zsio commented Dec 27, 2024

No.

https://nostalebots.xyz/

@Codelica
Copy link

Since --verify-client-url seems to have made it in (#2046) will there be config to restrict the embedded DERP server explicitly or by default?

@kradalby
Copy link
Collaborator

I think what you are waiting for is #2260, I need to circle back and check why that staled.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request no-stale-bot
Projects
None yet
Development

No branches or pull requests

8 participants
@kradalby @nblock @Codelica @zsio @ShadowJonathan @masterwishx @StudyingLover and others