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

Possible security problems exposing Radicale to the internet? #1529

Open
OIRNOIR opened this issue Jun 26, 2024 · 3 comments
Open

Possible security problems exposing Radicale to the internet? #1529

OIRNOIR opened this issue Jun 26, 2024 · 3 comments
Assignees
Milestone

Comments

@OIRNOIR
Copy link

OIRNOIR commented Jun 26, 2024

I'm installing Radicale and was confused by this language in the installation guide:
In the reverse proxy section, it says that "Untrusted clients should not be able to access the Radicale server directly. Otherwise, they can authenticate as any user." Does this mean that someone without my credentials will be able to access my Radicale remotely? Is it only if the X-Remote-User header is passed? Am I safe if requests are not allowed except through nginx?

@Unrud
Copy link
Collaborator

Unrud commented Jun 26, 2024

If auth-type is set to http_x_remote_user, the user will be set via the X-Remote-User header without any further restrictions. Clients must not be allowed to pass the header in this case.
If auth-type is set to something different, the header is ignored.

@OIRNOIR
Copy link
Author

OIRNOIR commented Jun 26, 2024

If auth-type is set to http_x_remote_user, the user will be set via the X-Remote-User header without any further restrictions. Clients must not be allowed to pass the header in this case. If auth-type is set to something different, the header is ignored.

I see. Thank you, that clears up my confusion. My auth type is set to htpasswd and I chose not to pass the X-Remote-User header so I should be fine.

@pbiering pbiering self-assigned this Jun 27, 2024
@pbiering pbiering added this to the 3.2.x milestone Jun 27, 2024
@pbiering
Copy link
Collaborator

I will review this part of documentation next to add some clarifications and when a reverse proxy is strongly recommended.

@pbiering pbiering modified the milestones: 3.2.x, 3.3.0 Sep 27, 2024
@pbiering pbiering added the task label Oct 8, 2024
@pbiering pbiering modified the milestones: 3.3.0, 3.3.x Oct 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants