#Using git on mac os code
#Using git on mac os password

#Using git on mac os code

The problem is that when you call the native C functions from inside ruby, ruby is the application that is running (your code is just a script that Keychain is unaware of).

This makes sense because you store passwords to be able to recover their plaintext later (otherwise you should be using key derivation function like bcrypt or scrypt). When you add an item to the keychain unless you otherwise specify, the current application running is implicitly the only authorized application.

#Using git on mac os password

But I quickly found another problem.Д®ach OS X Keychain item has a list of authorized applications that can read the password from the item without the user being prompted. Using native C functions to add the password prevents it from being available in plaintext to other processes which fixes that problem. I found the mac-keychain gem and later heard about zenspider's gem osx_keychain. My next step was to search for a gem that wrapped the C api for me so I don't have to get my hand dirty in C. This quickly ruled out using the security tool so I had to look at using the keychain api natively.

But to store a password in your keychain using this tool you have to pass it as an argument to security which means anyone on the system can see this if they know were to look. I started writing this program using ruby and some system calls to the security command line tool. If you only want the program, skip to it. To solve this, I decided to write a program that stores your username and/or password in your keychain so git will ask once for you username/password and retrieve it later so you don't have to type it again. One major disadvantage is that it asks you for your username/password each time you interact with your remote repository (clone, pull, push, etc). The only other advantages is that it's easier to set up HTTP proxy for git ( git config -global http.proxy proxy:8080 vs ssh config) and being able to use more than one GitHub account (which you shouldn't since anyone can add you as a contributor to a project). There aren't any major advantages using https over ssh to access your GitHub repositories, it's just more simple to use your username/password instead of adding your ssh key. And a few months later GitHub added support for this new HTTP transport and made it the default selected url for repositories (that you aren't a contributor for). Pretty clearly they botched the crap out of the repository authentication logic in Xcode 7 for git and have yet to fix it.Around this time last year git added a 'smart' HTTP transport that is faster than the old HTTP transport (and in some cases faster than SSH too). Repeated attempts to clear out the repo pointer in Xcode and re-create it fail. Xcode config is correct, using HTTPS rather than SSL.but no I enter the exact same credentials that are being used in 1-4 above and I get authentication failures. Actually - I am running Xcode 7.3 against a premise TFS instance with the same issue.ДЎ) Both 'Basic Authentication' and 'Windows Authentication' are enabled for the TFS Web app in IIS manager.Дў) Accessing the team project via Safari on the Mac works - prompting me for authentication when I first connect, and there is no problem.ДЈ) Both push and pull requests from the Git commands in the Terminal application on the Mac work to the same TFS repo.Д¤) Pushes and pulls to/from the TFS server using a third-party utility (SourceTree) work with no problem to the same TFS repo.ДҐ) Attempts to use the same repository from within Xcode, specifically using PUSH, fail.