-
Notifications
You must be signed in to change notification settings - Fork 36
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
[RFE] ~/.netrc support #9
Comments
For the command line tools, of course. |
Hi, I had a look at .netrc, it seems you can only specify a username and password in there. It would not be appropriate for davix, as it supports more authentication methods apart from simple username/password: x509 certificates, S3, Azure.. I think I will add ~/.davixrc, similar to .netrc in syntax but with support for the additional authentication methods. What do you think? |
Hi georgios, If my opinion matter, It would be awesome to have both I think. netrc for compat and something like davixrc for exotic auth method. Nowadays, a lot of service can now generate temporary service password which are safe to store in ~/.netrc. Cheers, |
Sure, we could first check ~/.davixrc, and if no hosts in there match, then check ~/.netrc. Since the file format will be the same in both, no need to write two different parsers. Some people have started using gpg-encrypted .netrc files.. :-) |
Hi All, |
Hi, The feature has been implemented and can be found in the devel branch. Please test, and try to break my terrible parser. :) Let me know especially in case it misbehaves with existing .netrc files. It always gives priority to .davixrc over .netrc.
Even though I usually prefer strict error checking, in this case any directives not understood are deliberately ignored, to minimize the risk of creating incompatibilities with other tools using their own custom directives. Cheers |
For authentication, would it be possible to add ~/.netrc support for providing credentials? This feature is used a lot by FTP command line tools.
PS: thanks so much davix (I use it for WebDAV access)!
The text was updated successfully, but these errors were encountered: