How to get Bitbucket on Nic.ru?

Question

Windows

Has anyone got this? The bottom line is that the nickname releases SSH outside only to remote ports 21, 80 and 443, but all my shamanism with switching to atlasian recommended in such cases by switching to port 443 ends with another complaint from git:

[[email protected] ~]$ ssh -vT altssh.bitbucket.org
OpenSSH_6.1p1, OpenSSL 0.9.8y 5 Feb 2013
debug1: Reading configuration data /home/clientsname/.ssh/config
debug1: /home/clientsname/.ssh/config line 1: Applying options for altssh.bitbucket.org
debug1: Connecting to altssh.bitbucket.org [131.103.20.174] port 443.
debug1: Connection established.
debug1: identity file /home/clientsname/.ssh/id_rsa type 1
debug1: identity file /home/clientsname/.ssh/id_rsa-cert type -1
debug1: Remote protocol version 2.0, remote software version OpenSSH_5.3
debug1: match: OpenSSH_5.3 pat OpenSSH_5*
debug1: Remote is not HPN-aware
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_6.1_hpn13v11 FreeBSD-20120901
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-ctr hmac-md5 none
debug1: kex: client->server aes128-ctr hmac-md5 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Server host key: RSA 97:8c:1b:f2:6f:14:6b:5c:3b:ec:aa:46:46:74:7c:40
debug1: checking without port identifier
debug1: read_passphrase: can't open /dev/tty: Permission denied
Host key verification failed.

And here is what ls -la /dev/tty says

crw--w----  1 root  4    9,  90 Sep  6 02:08 /dev/tty

As they say, "for what"? How did you manage to work this out in your favour?

Answer 1

Yes, whatever.
You can specify a network path.
Can be connected as a network drive.
There are no rules, only convenience.

Answer 2

\\FQDN\
IP ball should not be used, because in this case, intranet authorization falls down to the NTLM level with Kerberos, which in itself is less secure. Although using an ip address is acceptable, it's better not to.

Answer 3

У меня была та же проблема, с nic.ru пришел ответ:
В связи с особенностями архитектуры системы оказания услуг, исходящие соединения по протоколу SSH с веб-сервера невозможны.
Если Ваш репозиторий поддерживает работу по HTTPS, то Вы сможете им воспользоваться, однако имя пользователя и пароль для подключения к репозиторию следует указывать в URL репозитория, например, так:
https://user:[email protected]