Intel® DevCloud
Help for those needing help starting or connecting to the Intel® DevCloud
820 Discussions

Can't connect via corpo proxy

kraszkow
Employee
565 Views

○ → ssh -v devcloud-via-proxy
OpenSSH_7.6p1 Ubuntu-4ubuntu0.3, OpenSSL 1.0.2n 7 Dec 2017
debug1: Reading configuration data /home/kraszkow/.ssh/config
debug1: /home/kraszkow/.ssh/config line 18: Applying options for devcloud-via-proxy
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug1: Executing proxy command: exec nc -x proxy-dmz.intel.com:1080 devcloud.intel.com 22
debug1: key_load_public: No such file or directory
debug1: identity file /home/kraszkow/.ssh/devcloud-access-key.txt type -1
debug1: permanently_drop_suid: 1000
debug1: key_load_public: No such file or directory
debug1: identity file /home/kraszkow/.ssh/devcloud-access-key.txt-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3
debug1: Remote protocol version 2.0, remote software version OpenSSH_7.4
debug1: match: OpenSSH_7.4 pat OpenSSH* compat 0x04000000
debug1: Authenticating to devcloud.intel.com:22 as 'guest'
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: algorithm: curve25519-sha256
debug1: kex: host key algorithm: ecdsa-sha2-nistp256
debug1: kex: server->client cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
debug1: kex: client->server cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: ecdsa-sha2-nistp256 SHA256:A43Fccb1iM4pDwsT5OgjszJYHAJdaMmA4fV2hf1HmVo
debug1: Host 'devcloud.intel.com' is known and matches the ECDSA host key.
debug1: Found key in /home/kraszkow/.ssh/known_hosts:93
debug1: rekey after 134217728 blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: rekey after 134217728 blocks
debug1: SSH2_MSG_EXT_INFO received
debug1: kex_input_ext_info: server-sig-algs=<rsa-sha2-256,rsa-sha2-512>
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic
debug1: Next authentication method: gssapi-keyex
debug1: No valid Key exchange context
debug1: Next authentication method: gssapi-with-mic
debug1: Unspecified GSS failure. Minor code may provide more information
No Kerberos credentials available (default cache: FILE:/tmp/krb5cc_1000)

debug1: Unspecified GSS failure. Minor code may provide more information
No Kerberos credentials available (default cache: FILE:/tmp/krb5cc_1000)

debug1: Next authentication method: publickey
debug1: Trying private key: /home/kraszkow/.ssh/devcloud-access-key.txt
debug1: Authentication succeeded (publickey).
Authenticated to devcloud.intel.com (via proxy).
debug1: Local connections to LOCALHOST:4022 forwarded to remote address c009:22
debug1: Local forwarding listening on ::1 port 4022.
debug1: channel 0: new [port listener]
debug1: Local forwarding listening on 127.0.0.1 port 4022.
debug1: channel 1: new [port listener]
debug1: channel 2: new [client-session]
debug1: Requesting no-more-sessions@openssh.com
debug1: Entering interactive session.
debug1: pledge: proc
debug1: client_input_global_request: rtype hostkeys-00@openssh.com want_reply 0
debug1: Remote: Forced command.
debug1: Sending environment.
debug1: Sending env LC_MEASUREMENT = pl_PL.UTF-8
debug1: Sending env LC_PAPER = pl_PL.UTF-8
debug1: Sending env LC_MONETARY = pl_PL.UTF-8
debug1: Sending env LANG = en_US.UTF-8
debug1: Sending env LC_NAME = pl_PL.UTF-8
debug1: Sending env LC_ADDRESS = pl_PL.UTF-8
debug1: Sending env LC_NUMERIC = pl_PL.UTF-8
debug1: Sending env LC_TELEPHONE = pl_PL.UTF-8
debug1: Sending env LC_IDENTIFICATION = pl_PL.UTF-8
debug1: Sending env LC_TIME = pl_PL.UTF-8
SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3

Then typing something it returns protocol mismatch:

ok
Protocol mismatch.

 

1 Solution
kraszkow
Employee
559 Views

For others with the same problem. Should use:

 

ssh -v devcloud.proxy

instead of 

ssh -v devcloud-via-proxy

 

Using ssh devcloud.proxy I was able to connect.

 

BTW. Devcloud manual for proxy case is not clear.

View solution in original post

5 Replies
kraszkow
Employee
560 Views

For others with the same problem. Should use:

 

ssh -v devcloud.proxy

instead of 

ssh -v devcloud-via-proxy

 

Using ssh devcloud.proxy I was able to connect.

 

BTW. Devcloud manual for proxy case is not clear.

AthiraM_Intel
Moderator
526 Views

Hi,

 

Thanks for reaching out to us.

 

Glad to know that your issue got resolved.

Thanks for the feedback, we would like to know the appropriate steps that need to be clarified in the documentation.

 

Thanks.

 

AthiraM_Intel
Moderator
509 Views

Hi,


Could you please give us an update?  

It would be great if you share the steps that needs to clarify in the documentation. So that we could inform the concerned team about your feedback. 


Thanks.


kraszkow
Employee
504 Views

Hi,

if you don't see what needs to be changed I recommend you to do Usability Testing (https://www.usability.gov/how-to-and-tools/methods/usability-testing.html) with users which are behind proxy (for example intel proxy) and based on that make proper conclusions.

 

Regards,
Krzysztof

AthiraM_Intel
Moderator
478 Views

Hi,


Thanks for the feedback. We will inform the concerned team regarding this.

Since your issue is resolved, we would discontinue monitoring this thread. Please raise a new thread if you have further issues.


Thanks.




Reply