mudando a porta do git

398 views
Skip to first unread message

Edson Lima

unread,
Mar 8, 2012, 6:55:38 AM3/8/12
to Rail Groups
A porta padrão do repositório que trabalho mudou. Preciso efetuar um push para essa outra porta.
Alguém poderia me dar uma força?
Obrigado.


Marcelo Henrique

unread,
Mar 8, 2012, 6:56:37 AM3/8/12
to rail...@googlegroups.com
Voce tem que gerar outra key... o GIT enviu email pra todo mundo pedindo pra gera uma nova. 

--
Você recebeu essa mensagem porquê está inscrito no Google
Groups "rails-br".
Para enviar uma mensagem para o grupo, mande um email para rail...@googlegroups.com
Para se descadastrar, mande um e-mail para
rails-br+u...@googlegroups.com
Visite o grupo em http://groups.google.com/group/rails-br?hl=pt-BR
Leia nossa política de uso: http://goo.gl/YGgt7



--
                                              - Marcelo Henrique -
  "Se não puder se destacar pelo talento, vença pelo esforço." (Dave Weinbaum)

Marcelo Henrique

unread,
Mar 8, 2012, 6:58:21 AM3/8/12
to rail...@googlegroups.com
A security vulnerability was recently discovered that made it possible for an attacker to add new SSH keys to arbitrary GitHub user accounts. This would have provided an attacker with clone/pull access to repositories with read permissions, and clone/pull/push access to repositories with write permissions. As of 5:53 PM UTC on Sunday, March 4th the vulnerability no longer exists.

While no known malicious activity has been reported, we are taking additional precautions by forcing an audit of all existing SSH keys.

# Required Action

Since you have one or more SSH keys associated with your GitHub account you must visit https://github.com/settings/ssh/audit to approve each valid SSH key.

Until you have approved your SSH keys, you will be unable to clone/pull/push your repositories over SSH.

# Status

We take security seriously and recognize this never should have happened. In addition to a full code audit, we have taken the following measures to enhance the security of your account:

- We are forcing an audit of all existing SSH keys
- Adding a new SSH key will now prompt for your password
- We will now email you any time a new SSH key is added to your account
- You now have access to a log of account changes in your Account Settings page
Sincerely, The GitHub Team

Marcelo Henrique

unread,
Mar 8, 2012, 6:59:54 AM3/8/12
to rail...@googlegroups.com
Na verdade e so aprovar as chaves geradas. ou rejeitar 

2012/3/8 Marcelo Henrique <marce...@gmail.com>

Petterson Faria

unread,
Mar 8, 2012, 7:12:30 AM3/8/12
to rail...@googlegroups.com

Sobre mudar a porta use :

git remote add nome-do-remote ssh://usuario@host:porta/caminho-do-repositorio

--
Atenciosamente,
Petterson Faria

Stephen Eilert

unread,
Mar 8, 2012, 11:35:44 AM3/8/12
to rail...@googlegroups.com
2012/3/8 Marcelo Henrique <marce...@gmail.com>

Voce tem que gerar outra key... o GIT enviu email pra todo mundo pedindo pra gera uma nova. 


O *GITHUB*, não o GIT, mandou um email para todo mundo para *checar* se você reconhece todas as chaves que estão lá.

Não precisa mudar, precisa ver se existe alguma chave estranha, que você não reconheça.



-- Stephen

"Kids these days.
Whatever happened to hard work?"

       -- Joel Spolsky, The perils of javaschools

 
Reply all
Reply to author
Forward
0 new messages