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

.netrc support #72

Open
lalten opened this issue Apr 8, 2024 · 3 comments
Open

.netrc support #72

lalten opened this issue Apr 8, 2024 · 3 comments

Comments

@lalten
Copy link

lalten commented Apr 8, 2024

zsync2 does not offer .netrc support.

As a workaround, you can pass credentials directly in the URL like

zsync2 \
  --url=https://$USER:[email protected]/artifact.appimage \
  https://$USER:[email protected]/artifact.appimage.zsync

Any plans to support this?

@probonopd
Copy link
Member

probonopd commented Apr 9, 2024

What would you like to achieve? Can you describe your use case for this? Looking at the link, I see that .netrc is somehow related to automatic login (to FTP?) on GNU systems. It is not clear to me how this would relate to zsync2.

@lalten
Copy link
Author

lalten commented Apr 9, 2024

.netrc is a standard way to provide credentials and not only used for FTP. wget uses it automatically, and curl uses it when you supply -n/--netrc.
My https://example.com/artifact.appimage will return 404 without the right credentials passed in the authorization header.

@probonopd
Copy link
Member

Thanks for the clarification. I don't think this is a planned feature but if we'd get a pull request we'd definitely consider it. My only worry is that it might introduce additional complexity and/or security attack vectors, and hence increase maintenance burden.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants