Session A session is a set of options that are assigned to a connection to a remote machine. The term host is often used as a synonym for server. Often the computer on which a server program runs is also called a server. Server A computer program that provides services to other computer programs (called clients). This dialog allows you to view and manage the public keys that are installed for the current user on the remote : RECV: SERVICE_ACCEPT - OKThe Public-Key Assistant dialog is accessed from the Public-Key Assistant toolbar button or from the Public-Key Assistant. : Changing state from STATE_EXPECT_NEWKEYS to STATE_CONNECTION : Changing state from STATE_READY_FOR_NEW_KEYS to STATE_EXPECT_NEWKEYS : Changing state from STATE_KEY_EXCHANGE to STATE_READY_FOR_NEW_KEYS : Changing state from STATE_EXPECT_KEX_INIT to STATE_KEY_EXCHANGE : Available Remote Decompressors = : Selected Decompressor = none : Available Remote Compressors = : Selected Compressor = none : Available Remote Recv Macs = : Selected Recv Mac = hmac-sha2-512 : Available Remote Send Macs = : Selected Send Mac = hmac-sha2-512 : Available Remote Recv Ciphers = : Selected Recv Cipher = aes256-ctr : Available Remote Send Ciphers = : Selected Send Cipher = aes256-ctr : Available Remote Host Key Algos = rsa-sha2-512,rsa-sha2-256,ssh-rsa,ecdsa-sha2-nistp256,ssh-ed25519 : Available Remote Kex Methods = : Selected Kex Method = ecdh-sha2-nistp521 : The following key exchange method has been filtered from the key exchange method list because it is not supported: gss-gex-sha1-toWM5Slw5Ew8Mqkay+al2g= : The following key exchange method has been filtered from the key exchange method list because it is not supported: gss-group1-sha1-toWM5Slw5Ew8Mqkay+al2g= : GSS : Could not load library 'gssapi64.dll': The specified module could not be found. : GSS : SPN : : GSS : InitializeSecurit圜ontext() failed. : SSPI : The specified target is unknown or unreachable : SSPI : SPN : : SSPI : InitializeSecurit圜ontext() failed. : CAP : Remote correctly handles : SSPI : Requesting full delegation : CAP : Remote x.509v3 uses ASN.1 encoding for DSA signatures : CAP : Remote uses SHA1 hash in RSA signatures for x.509v3 : CAP : Remote correctly uses connected addresses in forwarded-tcpip requests : CAP : Remote correctly encodes OID for gssapi : CAP : Remote correctly handles unknown SFTP extensions : CAP : Remote supports new diffie-hellman group exchange messages : CAP : Remote uses 160 bit keys for SHA1 MAC : CAP : Remote includes port number in x11 open packets : CAP : Remote sends name in service accept packets : CAP : Remote sends error text in open failure packets : CAP : Remote sends algorithm name in signatures : CAP : Remote sends algorithm name in public key packets : CAP : Remote sends algorithm name in PK_OK packets : CAP : Remote sends language in password change requests : RECV : Remote Identifier = 'SSH-2.0-OpenSSH_7.9p1 Debian-10+deb10u2' : Changing state from STATE_NOT_CONNECTED to STATE_EXPECT_KEX_INIT this is the 1st part of the trace log, followed by the root/user abc's trace above. the rest of the trace log, which is the same for root and abc user.: SEND: Pty Request (rows: 68, cols: 189) : /root/.ssh/authorized_keys:1: key options: agent-forwarding port-forwarding pty user-rc x11-forwarding Only the log difference (from the user abc's trace) is shown ![]() : Connected for 3 seconds, 2698 bytes sent, 2233 bytes received : Changing state from STATE_SEND_DISCONNECT to STATE_CLOSED : Changing state from STATE_CONNECTION to STATE_SEND_DISCONNECT : SEND: Disconnect packet: The user canceled authentication. : RECV : USERAUTH_FAILURE, continuations Only the log difference (from the root's trace) is shown ssh/authorized_keys /home/abc/.ssh/authorized_keys Can you help? I ran out of ideas.ĪuthorizedKeysFile. I also checked very carefully the keys in the authorized_key files, the public key (opened in notepad, copied, then pasted into the container authorized_key file) matched. ssh/authorized_keys is owned by abc user. ssh/authorized_keys permissions correct with chmod 700 (i also tried 744), also. Somehow, the /home/abc/.ssh/authorized_keys file isn't read correctly. I also got public key authentication working for non-root user 123 on the docker host itself, along with root. Again, the abc user is within the container. Here is current setting, and the secureCRT trace log. So frustrating, since I already tried so many ways from googling. I couldn't figure why it's not working for non-root users (ie, abc). I have a Debian linux 10 container (docker host is oracle linux 7), which is setup for public key authentication.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |