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

Feature: Auth should use .netrc instead of a .cfg #154

Closed
vxbinaca opened this issue Aug 14, 2016 · 3 comments
Closed

Feature: Auth should use .netrc instead of a .cfg #154

vxbinaca opened this issue Aug 14, 2016 · 3 comments

Comments

@vxbinaca
Copy link

vxbinaca commented Aug 14, 2016

  • There should be a module to handle this (there was with perl when I was using it to beef up a script I used for a while) that gives .netrc that can be pulled on install after the change is made.
  • If no .netrc exists, create one and set perms to 600, insert auth.
  • Don't use flags to do this, use the inbuilt prompts that don't leave traces in the bash history
  • Might be an issue if someones using Cygwin, though I don't know because I run all Linux.
@jjjake
Copy link
Owner

jjjake commented Mar 14, 2018

@vxbinaca We're still going to want to want a config specifically for ia, but I added support for using a .netrc file to configure ia.

For example:

ia configure --netrc

That simply uses netrc.netrc(). It doesn't support pointing to specific files, but feel free to add that if you would find it useful. Also note that the Python netrc module does not support spaces in password. It's a known issue, but doesn't seem to have been resolved yet.

@vxbinaca
Copy link
Author

vxbinaca commented Mar 14, 2018

I'll hold off using it until they fix that. I only brought it up because it's a unix standard way of secure storage and parsing of credentials. Some of us use shell boxes and on a multi-user setup......eh it's the box admins fault for not setting 600 or 700 on each user directory.

Thanks. Also, I have questions about deriving. Who do I direct them to? If it's you I'll just email you.

@jjjake
Copy link
Owner

jjjake commented Mar 14, 2018

@vxbinaca you can email me. I'll direct it elsewhere if needed.

BTW, here's the issue if you'd like to follow (looks like the patch is awaiting review): python/cpython#127

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

2 participants