Re: SSH access to the SEAGrid database.

2022-07-22 Thread Bhavesh Asanabada
Hi Sudhakar,

Please find the error output upon accessing the SEAGrid database using the
SSH key.

(base) Bhavesh-MacBook:smiles_dashboard bhavesh$ ssh -vv
bhav...@gridchem.uits.iu.edu

OpenSSH_8.6p1, LibreSSL 3.3.6

debug1: Reading configuration data /Users/bhavesh/.ssh/config

debug1: /Users/bhavesh/.ssh/config line 5: Applying options for *

debug1: Reading configuration data /etc/ssh/ssh_config

debug1: /etc/ssh/ssh_config line 21: include /etc/ssh/ssh_config.d/*
matched no files

debug1: /etc/ssh/ssh_config line 54: Applying options for *

debug1: Authenticator provider $SSH_SK_PROVIDER did not resolve; disabling

debug1: Connecting to gridchem.uits.iu.edu port 22.

debug1: Connection established.

debug1: identity file /Users/bhavesh/.ssh/id_ed25519 type 3

debug1: identity file /Users/bhavesh/.ssh/id_ed25519-cert type -1

debug1: Local version string SSH-2.0-OpenSSH_8.6

debug1: Remote protocol version 2.0, remote software version OpenSSH_7.4

debug1: compat_banner: match: OpenSSH_7.4 pat
OpenSSH_7.0*,OpenSSH_7.1*,OpenSSH_7.2*,OpenSSH_7.3*,OpenSSH_7.4*,OpenSSH_7.5*,OpenSSH_7.6*,OpenSSH_7.7*
compat 0x0402

debug1: Authenticating to gridchem.uits.iu.edu:22 as 'bhavesh'

debug1: load_hostkeys: fopen /Users/bhavesh/.ssh/known_hosts2: No such file
or directory

debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts: No such file or
directory

debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts2: No such file or
directory

debug1: SSH2_MSG_KEXINIT sent

debug1: SSH2_MSG_KEXINIT received

debug2: local client KEXINIT proposal

debug2: KEX algorithms: curve25519-sha256,curve25519-sha...@libssh.org
,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group14-sha256,ext-info-c

debug2: host key algorithms: ssh-ed25519-cert-...@openssh.com,
ecdsa-sha2-nistp256-cert-...@openssh.com,
ecdsa-sha2-nistp384-cert-...@openssh.com,
ecdsa-sha2-nistp521-cert-...@openssh.com,sk-ssh-ed25519-cert-...@openssh.com
,sk-ecdsa-sha2-nistp256-cert-...@openssh.com,
rsa-sha2-512-cert-...@openssh.com,rsa-sha2-256-cert-...@openssh.com,
ssh-rsa-cert-...@openssh.com
,ssh-ed25519,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,
sk-ssh-ed25...@openssh.com,sk-ecdsa-sha2-nistp...@openssh.com
,rsa-sha2-512,rsa-sha2-256,ssh-rsa

debug2: ciphers ctos: chacha20-poly1...@openssh.com
,aes128-ctr,aes192-ctr,aes256-ctr,aes128-...@openssh.com,
aes256-...@openssh.com

debug2: ciphers stoc: chacha20-poly1...@openssh.com
,aes128-ctr,aes192-ctr,aes256-ctr,aes128-...@openssh.com,
aes256-...@openssh.com

debug2: MACs ctos: umac-64-...@openssh.com,umac-128-...@openssh.com,
hmac-sha2-256-...@openssh.com,hmac-sha2-512-...@openssh.com,
hmac-sha1-...@openssh.com,umac...@openssh.com,umac-...@openssh.com
,hmac-sha2-256,hmac-sha2-512,hmac-sha1

debug2: MACs stoc: umac-64-...@openssh.com,umac-128-...@openssh.com,
hmac-sha2-256-...@openssh.com,hmac-sha2-512-...@openssh.com,
hmac-sha1-...@openssh.com,umac...@openssh.com,umac-...@openssh.com
,hmac-sha2-256,hmac-sha2-512,hmac-sha1

debug2: compression ctos: none,z...@openssh.com,zlib

debug2: compression stoc: none,z...@openssh.com,zlib

debug2: languages ctos:

debug2: languages stoc:

debug2: first_kex_follows 0

debug2: reserved 0

debug2: peer server KEXINIT proposal

debug2: KEX algorithms: curve25519-sha256,curve25519-sha...@libssh.org
,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha256,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1

debug2: host key algorithms:
ssh-rsa,rsa-sha2-512,rsa-sha2-256,ecdsa-sha2-nistp256,ssh-ed25519

debug2: ciphers ctos: chacha20-poly1...@openssh.com
,aes128-ctr,aes192-ctr,aes256-ctr,aes128-...@openssh.com,
aes256-...@openssh.com
,aes128-cbc,aes192-cbc,aes256-cbc,blowfish-cbc,cast128-cbc,3des-cbc

debug2: ciphers stoc: chacha20-poly1...@openssh.com
,aes128-ctr,aes192-ctr,aes256-ctr,aes128-...@openssh.com,
aes256-...@openssh.com
,aes128-cbc,aes192-cbc,aes256-cbc,blowfish-cbc,cast128-cbc,3des-cbc

debug2: MACs ctos: umac-64-...@openssh.com,umac-128-...@openssh.com,
hmac-sha2-256-...@openssh.com,hmac-sha2-512-...@openssh.com,
hmac-sha1-...@openssh.com,umac...@openssh.com,umac-...@openssh.com
,hmac-sha2-256,hmac-sha2-512,hmac-sha1

debug2: MACs stoc: umac-64-...@openssh.com,umac-128-...@openssh.com,
hmac-sha2-256-...@openssh.com,hmac-sha2-512-...@openssh.com,
hmac-sha1-...@openssh.com,umac...@openssh.com,umac-...@openssh.com
,hmac-sha2-256,hmac-sha2-512,hmac-sha1

debug2: compression ctos: none,z...@openssh.com

debug2: compression stoc: none,z...@openssh.com

debug2: languages ctos:

debug2: languages stoc:

debug2: first_kex_follows 0

debug2: reserved 0

debug1: kex: algorithm: curve25519-sha256

debug1: kex: host key algorithm: ssh-ed25519

debug1: kex: server->client cipher: 

Re: SSH access to the SEAGrid database.

2022-07-13 Thread Pamidighantam, Sudhakar V
Bhavesh:

I could login into 
bhav...@gridchem.uits.iu.edu<mailto:bhav...@gridchem.uits.iu.edu> fine with my 
ssh key.

Either your key is bad or something. Can you send me another ssh public key. 
Please send the output for ssh -vv 
bhav...@gridchem.uits.iu.edu<mailto:bhav...@gridchem.uits.iu.edu>
Screen shots are not very useful to debug this.

Thanks,
Sudhakar.

From: Bhavesh Asanabada 
Date: Tuesday, July 12, 2022 at 10:32 PM
To: dev@airavata.apache.org 
Subject: SSH access to the SEAGrid database.
Hi Sudhakar,

In the last meeting, I shared the SSH key to connect to the SEAGrid database 
for the reference models. I tried to connect with the provided routes but it 
throws an error as permission is denied. Could you please confirm the access I 
have?

Thanks
Bhavesh Asanabada