title: Github multiple accounts one computer always sees one account
body: <p>This is probably not a dup; I have read through many similar problems on StackOverflow but not this issue.</p>
  
  <p>I am trying to use multiple git accounts on Ubuntu Linux and whenever I try to push from the 2nd account it thinks that I am still using the username of the first account.  </p>
  
  <pre><code>$ git push -u origin master
  ERROR: Permission to &lt;act2&gt;/&lt;repo&gt;.git denied to &lt;act1&gt;.
  </code></pre>
  
  <p>I first tried the multiple SSH key method.  When I got the above error I then created a completely new user on my local machine, logged in as that user, recreated the local repo (its the first push) and tried again.  Same error.  My local .config shows the user as  and so does my ~/.gitconfig.</p>
  
  <p>Any ideas?</p>
  
  <p>I do:
  ssh @localhost
  then ssh -vvv -T git@github.com</p>
  
  <p>I get this interesting output.  It seems to go off and find a key in my  account. But somehow it uses a key in my  account, which is really shouldn't have access to.</p>
  
  <pre><code>
  debug1: Host 'github.com' is known and matches the RSA host key.
  debug1: Found key in /home//.ssh/known_hosts:1
  debug2: bits set: 513/1024
  debug1: ssh_rsa_verify: signature correct
  debug2: kex_derive_keys
  debug2: set_newkeys: mode 1
  debug1: SSH2_MSG_NEWKEYS sent
  debug1: expecting SSH2_MSG_NEWKEYS
  debug3: Wrote 16 bytes for a total of 1015
  debug2: set_newkeys: mode 0
  debug1: SSH2_MSG_NEWKEYS received
  debug1: SSH2_MSG_SERVICE_REQUEST sent
  debug3: Wrote 48 bytes for a total of 1063
  debug2: service_accept: ssh-userauth
  debug1: SSH2_MSG_SERVICE_ACCEPT received
  debug2: key:  
  debug2: key:  
  debug2: key: /home//.ssh/identity ((nil))
  debug2: key: /home//.ssh/id_rsa ()
  debug2: key: /home//.ssh/id_dsa ((nil))
  debug3: Wrote 64 bytes for a total of 1127
  debug1: Authentications that can continue: publickey
  debug3: start over, passed a different list publickey
  debug3: preferred gssapi-keyex,gssapi-with-mic,gssapi,publickey,keyboard-interactive,password
  debug3: authmethod_lookup publickey
  debug3: remaining preferred: keyboard-interactive,password
  debug3: authmethod_is_enabled publickey
  debug1: Next authentication method: publickey
  debug1: Offering public key: 
  debug3: send_pubkey_test
  debug2: we sent a publickey packet, wait for reply
  debug3: Wrote 368 bytes for a total of 1495
  debug1: Authentications that can continue: publickey
  debug1: Offering public key: 
  debug3: send_pubkey_test
  debug2: we sent a publickey packet, wait for reply
  debug3: Wrote 368 bytes for a total of 1863
  debug1: Remote: Forced command: gerve 
  debug1: Remote: Port forwarding disabled.
  debug1: Remote: X11 forwarding disabled.
  debug1: Remote: Agent forwarding disabled.
  debug1: Remote: Pty allocation disabled.
  debug1: Server accepts key: pkalg ssh-rsa blen 277
  debug2: input_userauth_pk_ok: fp 
  debug3: sign_and_send_pubkey
  debug3: Wrote 640 bytes for a total of 2503
  debug1: Remote: Forced command: gerve 
  debug1: Remote: Port forwarding disabled.
  debug1: Remote: X11 forwarding disabled.
  debug1: Remote: Agent forwarding disabled.
  debug1: Remote: Pty allocation disabled.
  debug1: Authentication succeeded (publickey).
  debug1: channel 0: new [client-session]
  debug3: ssh_session2_open: channel_new: 0
  debug2: channel 0: send open
  debug1: Requesting no-more-sessions@openssh.com
  debug1: Entering interactive session.
  debug3: Wrote 128 bytes for a total of 2631
  debug2: callback start
  ...
  </code></pre>