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.

Sign up for GitHub

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

Jump to bottom

Don't force usage of a ~/.netrc file when remote server requires authentication #55

Closed
sguillope opened this issue May 14, 2016 · 1 comment
Closed

Don't force usage of a ~/.netrc file when remote server requires authentication #55

sguillope opened this issue May 14, 2016 · 1 comment

Comments

@sguillope
Copy link
Contributor

#54 added the option --netrc to the curl call in the HTTP module.

However when downloading using the HTTP module, curl should use --netrc-optional instead of the more restrictive --netrc option. This allows users to choose to specify the authentication credentials through the url instead of having to set them up in a ~/.netrc file

See CocoaPods/CocoaPods#5318
sguillope pushed a commit to sguillope/cocoapods-downloader that referenced this issue May 14, 2016
Use curl's --netrc-optional option instead of --netrc
e189947 
Using --netrc forces the user to provide authentication credentials through a
.netrc file in the user's home folder if the remote server requires
authentication.

However a user may want to provide the credentials right in the url which has
the advantage of not being dependent on having build machines set up with the
.netrc file. In an enterprise environment - potentially using many build
machines and having many team members - it can become a hassle to ensure proper
configuration of all build environments.

Ideally we should be able to specify the path to the .netrc file using the
--netrc-file option but that's for another time.

CocoaPodsgh-55
@sguillope sguillope mentioned this issue May 14, 2016
Merged
@mackoj
Copy link

mackoj commented Jun 2, 2016 •
edited

Thanks for the fix.

I have the same issue.
Please @segiddins consider tag a new version of Cocoapods with it.

Thanks,

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@mackoj @segiddins @sguillope