[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: The key algorithm 'ssh-rsa' is not allowed in V 0.10.4


Hi Jakub, 

I see, thanks for the explanation.

I tested your merge request on RHEL 9 and the authentication succeeded without the use of SSH_OPTIONS_PROCESS_CONFIG = false or ssh_userauth_none().
The log is attached.
I also tested without the line:
ssh_options_set(session, SSH_OPTIONS_PUBLICKEY_ACCEPTED_TYPES, "ssh-rsa,rsa-sha2-256,rsa-sha2-512")

This also successfully chooses rsa-sha2-512.

Cheers,
Till

May 30, 2025 10:03 AM, "Jakub Jelen" <jjelen@xxxxxxxxxx (mailto:jjelen@xxxxxxxxxx?to=%22Jakub%20Jelen%22%20<jjelen@xxxxxxxxxx>)> wrote:
The RFC 8308 (extension negotiation) was added only recently on top of the existing RFCs and which libssh was built around.

You are right that the `ssh_connect()` should make sure it processes the possible extensions or the authentication functions should process outstanding packets if there are any. But the way how the specs are written does not say that the message needs to come (it just MAY come):

> A party that received the "ext-info-c" or "ext-info-s" indicator MAY send the following message

https://datatracker.ietf.org/doc/html/rfc8308#section-2.3 (https://datatracker.ietf.org/doc/html/rfc8308#section-2.3)

OTOH the SSH sends service request before authentication requests, which means that it should process outstanding messages. The problem is that this is done only after the key is being checked for compatibility right now, which is wrong. So this should be fixed. Can you try the following changes that they solve the problem (without the need for the none auth method?):

https://gitlab.com/libssh/libssh-mirror/-/merge_requests/619 (https://gitlab.com/libssh/libssh-mirror/-/merge_requests/619)

Thanks,
Jakub
On Thu, May 29, 2025 at 9:53 PM <g4-lisz@xxxxxxxxxxxx (mailto:g4-lisz@xxxxxxxxxxxx)> wrote: 
Hi Jakub

Yes, this did the trick!

But to be honest I would rather say that this is a bug in the library...
If I understand it right, it sends the request but doesn't take it into account before trying any authentication - is this in the SSH specs? IMHO this doesn't make much sense.

Cheers
Till

May 27, 2025 10:15 AM, "Jakub Jelen" <jjelen@xxxxxxxxxx (mailto:jjelen@xxxxxxxxxx?to=%22Jakub%20Jelen%22%20%3Cjjelen@xxxxxxxxxx%3E)> wrote:
Hmm. The log says the server supports extensions, the detection of the client extension support went well too, the SSH_MSG_EXT_INFO packet is also sent, so it is not clear to me why it should not work.

[2025/05/23 14:02:12.155371, 3] 10.10.10.133 - ssh_server_send_extensions: Sending SSH_MSG_EXT_INFO

The server is also sending sha2 hostkey signature which is correctly verified by the client.

Looking again at the client log, I see that the packet SSH_MSG_EXT_INFO is not being processed by the callbacks before you attempt to authenticate, which means the extension from this packet are not taken into the account.

So this, from my understanding, sounds like a bug in the client, that it sends the authentication requests before fully processing the messages sent by the server.

I think it might be possible to get over that by calling the ssh_userauth_none() first, which will get you the list of server supported authentication methods (and as a side effect, it should process all the outstanding messages, including the extension).

Looking at the tutorial, I see this is not very well described. It mostly says, "don't use this" and next section shows its use without any explanation.

https://api.libssh.org/master/libssh_tutor_authentication.html (https://api.libssh.org/master/libssh_tutor_authentication.html)

This would be probably good to improve a bit.

Please, let me know if the a above suggestion solves the problem for you. If so, I will try to update the tutorial to reflect this.

Thanks for the patience!
Jakub

On Fri, May 23, 2025 at 2:17 PM <g4-lisz@xxxxxxxxxxxx (mailto:g4-lisz@xxxxxxxxxxxx)> wrote:
Here you go (attached).

Cheers
Till

May 23, 2025 9:50 AM, "Jakub Jelen" <jjelen@xxxxxxxxxx (mailto:jjelen@xxxxxxxxxx?to=%22Jakub%20Jelen%22%20%3Cjjelen@xxxxxxxxxx%3E)> wrote:
That should not be the case. The server should be sending this message from the `session->ssh_connection_callback` so unless you override that one, it should be executed (and that one is not designed to be overridden).

Can you get the debug logs from the server for one connection to see what is going on there?

Jakub
On Thu, May 22, 2025 at 11:34 PM <g4-lisz@xxxxxxxxxxxx (mailto:g4-lisz@xxxxxxxxxxxx)> wrote:
	On 5/22/25 12:38, Jakub Jelen wrote:On Wed, May 21, 2025 at 4:26 PM <g4-lisz@xxxxxxxxxxxx (mailto:g4-lisz@xxxxxxxxxxxx)> wrote:
On 5/21/25 15:53, Jakub Jelen wrote:
On Wed, May 21, 2025 at 1:43 PM <g4-lisz@xxxxxxxxxxxx (mailto:g4-lisz@xxxxxxxxxxxx)> wrote:
	Hi
On 5/21/25 09:44, Jakub Jelen wrote:
Hi,
the strace does not show much what libssh does.
It just confirms the check is failing locally, without sending the public key to server. But the signature algorithm depends on the extensions negotiated during key exchange, which should be logged in verbose log.
I meant setting the log level using something like this:

int verbosity = SSH_LOG_TRACE;
ssh_options_set(session, SSH_OPTIONS_LOG_VERBOSITY, &verbosity);

	Ah sure, but you don't need strace to read the log ;) I disabled it on purpose so you see the essential filehandling...

	Here you go again (attached).
I think this was still log level 3, while to get all of the tracing information and packet numbers, log level 4 is required.

	I'm confused about how ssh_options_set(session, SSH_OPTIONS_LOG_VERBOSITY, ...) and ssh_set_log_level() is connected.

	I used ssh_set_log_level(SSH_LOG_PACKET) - this is not equal to ssh_options_set() with SSH_LOG_TRACE?

Sorry, the names are a bit confusing. The SSH_LOG_PACKET = SSH_LOG_DEBUG is 3, while SSH_LOG_TRACE = SSH_LOG_FUNCTIONS is 4. These aliased names have quite conflicting descriptions (and I am not even sure why we have them twice). It would be good to make it a bit more systematic ...

	My bad, for some reason I put SSH_LOG_PACKET instead of SSH_LOG_FUNCTIONS.

	Yes I was always wondering why there are these two different naming schemes... Maybe there were plans to have some kind of scopes besides the levels.
	Ah wait I see the issue: I called ssh_set_log_level() after ssh_new(). I guess that makes the difference.

	New log attached.
I am still trying to figure out if the extensions are negotiated and sent correctly to see if it is server or client issue. This is still not visible from this log. I think the code to handle this is already in 0.9.7, but it might be also affected by some configuration/options on the server side.

It is also possible that the global configuration from cryptographic policies overrides the `SSH_OPTIONS_PUBLICKEY_ACCEPTED_TYPES`. The strace log shows that the OpenSSH configuration is read before connecting:

openat(AT_FDCWD, "/etc/crypto-policies/back-ends/openssh.config", O_RDONLY) = 5

This file does not have the ssh-rsa (SHA1) mechanisms in accepted types:

$ cat /etc/crypto-policies/back-ends/openssh.config | grep ssh-rsa

	If this is the case, is there a option to keep libssh from reading systemwide configs? In my case that would be neater than enabling SHA for the whole system...

There is SSH_OPTIONS_PROCESS_CONFIG in ssh_options_set(), which if set to false, will not process any system configuration.

https://api.libssh.org/master/group__libssh__session.html#ga7a801b85800baa3f4e16f5b47db0a73d (https://api.libssh.org/master/group__libssh__session.html#ga7a801b85800baa3f4e16f5b47db0a73d)

	Yes! That did the trick:

	[2025/05/21 16:16:49.030307, 3] ssh_packet_need_rekey: rekey: [data_rekey_needed=0, out_blocks=61, in_blocks=45]
[2025/05/21 16:16:49.030405, 2] ssh_userauth_publickey_auto: Successfully authenticated using /home/useruser/id_rsa
Connected and authenticated with key!

	Cheers
Till
Good to hear it worked.

Looking at the log, I see the client correctly advertises the support for the extensions:

[2025/05/21 16:12:17.052133, 4] ssh_list_kex: kex algos: curve25519-sha256,curve25519-sha256@xxxxxxxxxx (mailto:curve25519-sha256@xxxxxxxxxx),ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,ext-info-c

But I do not see the server sending the SSH_MSG_EXT_INFO packet (RFC 8308) so its likely the server to blame for this issue. Updating to newer libssh would be good to get the newer functionality and bugfixes.

	I wrote the server 6 (?) years ago... But looking at the sources of libbssh 0.9.7 I can find the handling of SSH_MSG_EXT_INFO in ssh_server_connection_callback() (server.c:431).

	Maybe I overwrote the callback? I set the server callbacks here:

	struct ssh_server_callbacks_struct cb = {
.userdata = &info,
#ifdef WITH_PASSWORD
.auth_password_function = auth_password,
#endif
#ifdef WITH_GSSAPI
.auth_gssapi_mic_function = auth_gssapi_mic,
#endif
#ifdef WITH_PUBKEY
.auth_pubkey_function = auth_publickey,
#endif
.channel_open_request_session_function = new_session_channel,
.service_request_function = service_request
};

	All other custom callback functions are on channel level...

	Wait, there's also a custom message_callback(). But this only handles ssh_message_type(message) == SSH_REQUEST_CHANNEL_OPEN. In any other case it returns 1 (hence the lib should handle all other messages).

	Cheers,
Till
[2025/05/30 20:53:11.440431, 3] ssh_options_parse_config:  Reading configuration data from /etc/ssh/ssh_config
[2025/05/30 20:53:11.440706, 3] local_parse_file:  Reading additional configuration data from /etc/ssh/ssh_config.d/50-redhat.conf
[2025/05/30 20:53:11.440762, 3] ssh_config_parse_line:  line 3: Processing Match keyword 'final'
[2025/05/30 20:53:11.440774, 3] ssh_config_parse_line:  line 3: Unsupported Match keyword 'final', skipping
[2025/05/30 20:53:11.440781, 3] ssh_config_parse_line:  line 3: Processing Match keyword 'all'
[2025/05/30 20:53:11.440819, 3] local_parse_file:  Reading additional configuration data from /etc/crypto-policies/back-ends/openssh.config
[2025/05/30 20:53:11.440876, 4] ssh_config_parse_line:  Unknown option: GSSAPIKexAlgorithms, line: 3
[2025/05/30 20:53:11.440947, 4] ssh_config_parse_line:  Unknown option: CASignatureAlgorithms, line: 6
[2025/05/30 20:53:11.440958, 4] ssh_config_parse_line:  Unknown option: RequiredRSASize, line: 7
[2025/05/30 20:53:11.440987, 4] ssh_config_parse_line:  Unapplicable option: ForwardX11Trusted, line: 12
[2025/05/30 20:53:11.441169, 3] ssh_connect:  libssh 0.11.0 (c) 2003-2025 Aris Adamantiadis, Andreas Schneider and libssh contributors. Distributed under the LGPL, please refer to COPYING file for information about your rights, using threading threads_pthread
[2025/05/30 20:53:11.441190, 3] getai:  host 10.10.10.108 matches an IP address
[2025/05/30 20:53:11.441509, 3] ssh_socket_connect:  Nonblocking connection socket: 3
[2025/05/30 20:53:11.441598, 3] ssh_connect:  Socket connecting, now waiting for the callbacks to work
[2025/05/30 20:53:11.441615, 3] ssh_connect:  Actual timeout : 10000
[2025/05/30 20:53:11.442007, 4] ssh_socket_pollcallback:  Poll callback on socket 3 (POLLOUT ), out buffer 0
[2025/05/30 20:53:11.442022, 3] ssh_socket_pollcallback:  Received POLLOUT in connecting state
[2025/05/30 20:53:11.442028, 4] socket_callback_connected:  Socket connection callback: 1 (0)
[2025/05/30 20:53:11.442032, 3] ssh_client_connection_callback:  session_state=2
[2025/05/30 20:53:11.442153, 3] ssh_socket_unbuffered_write:  Enabling POLLOUT for socket
[2025/05/30 20:53:11.442167, 4] ssh_socket_unbuffered_write:  wrote 23
[2025/05/30 20:53:11.442176, 4] ssh_socket_pollcallback:  Poll callback on socket 3 (POLLOUT ), out buffer 0
[2025/05/30 20:53:11.444887, 4] ssh_socket_pollcallback:  Poll callback on socket 3 (POLLIN ), out buffer 0
[2025/05/30 20:53:11.444953, 4] ssh_socket_unbuffered_read:  read 910
[2025/05/30 20:53:11.444966, 3] callback_receive_banner:  Received banner: SSH-2.0-libssh_0.9.7
[2025/05/30 20:53:11.444974, 3] ssh_client_connection_callback:  session_state=3
[2025/05/30 20:53:11.444981, 3] ssh_client_connection_callback:  SSH server banner: SSH-2.0-libssh_0.9.7
[2025/05/30 20:53:11.444990, 3] ssh_analyze_banner:  Analyzing banner: SSH-2.0-libssh_0.9.7
[2025/05/30 20:53:11.448010, 3] ssh_client_select_hostkeys:  Order of wanted host keys: "ssh-ed25519,ecdsa-sha2-nistp521,ecdsa-sha2-nistp384,ecdsa-sha2-nistp256,sk-ssh-ed25519@xxxxxxxxxxx,sk-ecdsa-sha2-nistp256@xxxxxxxxxxx,rsa-sha2-512,rsa-sha2-256"
[2025/05/30 20:53:11.448136, 4] ssh_known_hosts_read_entries:  Failed to open the known_hosts file '/etc/ssh/ssh_known_hosts': No such file or directory
[2025/05/30 20:53:11.448155, 3] ssh_client_select_hostkeys:  No key found in known_hosts; changing host key method to "ssh-ed25519,ecdsa-sha2-nistp521,ecdsa-sha2-nistp384,ecdsa-sha2-nistp256,sk-ssh-ed25519@xxxxxxxxxxx,sk-ecdsa-sha2-nistp256@xxxxxxxxxxx,rsa-sha2-512,rsa-sha2-256"
[2025/05/30 20:53:11.448170, 4] ssh_send_kex:  Sending KEXINIT packet, first_kex_packet_follows = 0
[2025/05/30 20:53:11.448183, 4] ssh_list_kex:  kex algos: curve25519-sha256,curve25519-sha256@xxxxxxxxxx,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,ext-info-c,kex-strict-c-v00@xxxxxxxxxxx
[2025/05/30 20:53:11.448190, 4] ssh_list_kex:  server host key algo: ssh-ed25519,ecdsa-sha2-nistp521,ecdsa-sha2-nistp384,ecdsa-sha2-nistp256,sk-ssh-ed25519@xxxxxxxxxxx,sk-ecdsa-sha2-nistp256@xxxxxxxxxxx,rsa-sha2-512,rsa-sha2-256
[2025/05/30 20:53:11.448218, 4] ssh_list_kex:  encryption client->server: aes256-gcm@xxxxxxxxxxx,chacha20-poly1305@xxxxxxxxxxx,aes256-ctr,aes128-gcm@xxxxxxxxxxx,aes128-ctr
[2025/05/30 20:53:11.448226, 4] ssh_list_kex:  encryption server->client: aes256-gcm@xxxxxxxxxxx,chacha20-poly1305@xxxxxxxxxxx,aes256-ctr,aes128-gcm@xxxxxxxxxxx,aes128-ctr
[2025/05/30 20:53:11.448233, 4] ssh_list_kex:  mac algo client->server: hmac-sha2-256-etm@xxxxxxxxxxx,hmac-sha1-etm@xxxxxxxxxxx,hmac-sha2-512-etm@xxxxxxxxxxx,hmac-sha2-256,hmac-sha1,hmac-sha2-512
[2025/05/30 20:53:11.448240, 4] ssh_list_kex:  mac algo server->client: hmac-sha2-256-etm@xxxxxxxxxxx,hmac-sha1-etm@xxxxxxxxxxx,hmac-sha2-512-etm@xxxxxxxxxxx,hmac-sha2-256,hmac-sha1,hmac-sha2-512
[2025/05/30 20:53:11.448247, 4] ssh_list_kex:  compression algo client->server: none,zlib@xxxxxxxxxxx
[2025/05/30 20:53:11.448254, 4] ssh_list_kex:  compression algo server->client: none,zlib@xxxxxxxxxxx
[2025/05/30 20:53:11.448261, 4] ssh_list_kex:  languages client->server: 
[2025/05/30 20:53:11.448268, 4] ssh_list_kex:  languages server->client: 
[2025/05/30 20:53:11.448484, 3] ssh_socket_unbuffered_write:  Enabling POLLOUT for socket
[2025/05/30 20:53:11.448515, 4] ssh_socket_unbuffered_write:  wrote 984
[2025/05/30 20:53:11.448525, 3] packet_send2:  packet: wrote [type=20, len=980, padding_size=6, comp=973, payload=973]
[2025/05/30 20:53:11.448535, 3] ssh_send_kex:  SSH_MSG_KEXINIT sent
[2025/05/30 20:53:11.448549, 3] ssh_packet_socket_callback:  packet: read type 20 [len=884,padding=9,comp=874,payload=874]
[2025/05/30 20:53:11.448557, 3] ssh_packet_process:  Dispatching handler for packet type 20
[2025/05/30 20:53:11.448566, 4] ssh_packet_kexinit:  KEXINIT received
[2025/05/30 20:53:11.448598, 3] ssh_client_connection_callback:  session_state=5
[2025/05/30 20:53:11.448607, 4] ssh_list_kex:  kex algos: curve25519-sha256,curve25519-sha256@xxxxxxxxxx,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group18-sha512,diffie-hellman-group16-sha512,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha256,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1
[2025/05/30 20:53:11.448615, 4] ssh_list_kex:  server host key algo: rsa-sha2-512,rsa-sha2-256,ssh-rsa
[2025/05/30 20:53:11.448622, 4] ssh_list_kex:  encryption client->server: aes256-gcm@xxxxxxxxxxx,aes128-gcm@xxxxxxxxxxx,aes256-ctr,aes192-ctr,aes128-ctr,aes256-cbc,aes192-cbc,aes128-cbc,3des-cbc
[2025/05/30 20:53:11.448629, 4] ssh_list_kex:  encryption server->client: aes256-gcm@xxxxxxxxxxx,aes128-gcm@xxxxxxxxxxx,aes256-ctr,aes192-ctr,aes128-ctr,aes256-cbc,aes192-cbc,aes128-cbc,3des-cbc
[2025/05/30 20:53:11.448636, 4] ssh_list_kex:  mac algo client->server: hmac-sha2-256-etm@xxxxxxxxxxx,hmac-sha2-512-etm@xxxxxxxxxxx,hmac-sha1-etm@xxxxxxxxxxx,hmac-sha2-256,hmac-sha2-512,hmac-sha1
[2025/05/30 20:53:11.448643, 4] ssh_list_kex:  mac algo server->client: hmac-sha2-256-etm@xxxxxxxxxxx,hmac-sha2-512-etm@xxxxxxxxxxx,hmac-sha1-etm@xxxxxxxxxxx,hmac-sha2-256,hmac-sha2-512,hmac-sha1
[2025/05/30 20:53:11.448650, 4] ssh_list_kex:  compression algo client->server: none
[2025/05/30 20:53:11.448657, 4] ssh_list_kex:  compression algo server->client: none
[2025/05/30 20:53:11.448664, 4] ssh_list_kex:  languages client->server: 
[2025/05/30 20:53:11.448670, 4] ssh_list_kex:  languages server->client: 
[2025/05/30 20:53:11.448706, 3] ssh_kex_select_methods:  Negotiated curve25519-sha256,rsa-sha2-512,aes256-gcm@xxxxxxxxxxx,aes256-gcm@xxxxxxxxxxx,aead-gcm,aead-gcm,none,none,,
[2025/05/30 20:53:11.448715, 4] dh_handshake:  dh_handshake_state = 0, kex_type = 9
[2025/05/30 20:53:11.449072, 3] packet_send2:  packet: wrote [type=30, len=44, padding_size=6, comp=37, payload=37]
[2025/05/30 20:53:11.449100, 4] ssh_socket_pollcallback:  Poll callback on socket 3 (POLLOUT ), out buffer 48
[2025/05/30 20:53:11.449117, 3] ssh_socket_unbuffered_write:  Enabling POLLOUT for socket
[2025/05/30 20:53:11.449125, 4] ssh_socket_unbuffered_write:  wrote 48
[2025/05/30 20:53:11.449149, 4] ssh_socket_pollcallback:  Poll callback on socket 3 (POLLOUT ), out buffer 0
[2025/05/30 20:53:11.449157, 4] ssh_socket_pollcallback:  sending control flow event
[2025/05/30 20:53:11.449164, 4] ssh_packet_socket_controlflow_callback:  sending channel_write_wontblock callback
[2025/05/30 20:53:11.510497, 4] ssh_socket_pollcallback:  Poll callback on socket 3 (POLLIN ), out buffer 0
[2025/05/30 20:53:11.510550, 4] ssh_socket_unbuffered_read:  read 616
[2025/05/30 20:53:11.510564, 3] ssh_packet_socket_callback:  packet: read type 31 [len=612,padding=11,comp=600,payload=600]
[2025/05/30 20:53:11.510572, 3] ssh_packet_process:  Dispatching handler for packet type 31
[2025/05/30 20:53:11.511148, 3] ssh_socket_unbuffered_write:  Enabling POLLOUT for socket
[2025/05/30 20:53:11.511182, 4] ssh_socket_unbuffered_write:  wrote 16
[2025/05/30 20:53:11.511192, 3] packet_send2:  packet: wrote [type=21, len=12, padding_size=10, comp=1, payload=1]
[2025/05/30 20:53:11.511200, 4] ssh_packet_set_newkeys:  called, direction = OUT 
[2025/05/30 20:53:11.511815, 3] crypt_set_algorithms2:  Set output algorithm to aes256-gcm@xxxxxxxxxxx
[2025/05/30 20:53:11.511838, 3] crypt_set_algorithms2:  Set HMAC output algorithm to aead-gcm
[2025/05/30 20:53:11.511846, 3] crypt_set_algorithms2:  Set input algorithm to aes256-gcm@xxxxxxxxxxx
[2025/05/30 20:53:11.511853, 3] crypt_set_algorithms2:  Set HMAC input algorithm to aead-gcm
[2025/05/30 20:53:11.512002, 3] ssh_init_rekey_state:  Set rekey after 4294967296 blocks
[2025/05/30 20:53:11.512015, 3] ssh_init_rekey_state:  Set rekey after 4294967296 blocks
[2025/05/30 20:53:11.512064, 3] ssh_packet_send_newkeys:  SSH_MSG_NEWKEYS sent
[2025/05/30 20:53:11.512086, 4] ssh_socket_pollcallback:  Poll callback on socket 3 (POLLIN POLLOUT ), out buffer 0
[2025/05/30 20:53:11.512177, 4] ssh_socket_unbuffered_read:  read 16
[2025/05/30 20:53:11.512190, 3] ssh_packet_socket_callback:  packet: read type 21 [len=12,padding=10,comp=1,payload=1]
[2025/05/30 20:53:11.512197, 3] ssh_packet_process:  Dispatching handler for packet type 21
[2025/05/30 20:53:11.512205, 3] ssh_packet_newkeys:  Received SSH_MSG_NEWKEYS
[2025/05/30 20:53:11.512269, 4] ssh_pki_signature_verify:  Going to verify a rsa-sha2-512 type signature
[2025/05/30 20:53:11.512523, 4] pki_verify_data_signature:  Signature valid
[2025/05/30 20:53:11.512541, 3] ssh_packet_newkeys:  Signature verified and valid
[2025/05/30 20:53:11.512549, 4] ssh_packet_set_newkeys:  called, direction = IN 
[2025/05/30 20:53:11.512564, 3] ssh_client_connection_callback:  session_state=6
[2025/05/30 20:53:11.512574, 4] ssh_socket_pollcallback:  sending control flow event
[2025/05/30 20:53:11.512581, 4] ssh_packet_socket_controlflow_callback:  sending channel_write_wontblock callback
[2025/05/30 20:53:11.512590, 3] ssh_connect:  current state : 7
[2025/05/30 20:53:11.512606, 3] ssh_userauth_publickey_auto:  Trying to authenticate with /home/useruser/id_rsa
[2025/05/30 20:53:11.513336, 4] pki_private_key_from_base64:  Error parsing private key: error:1E08010C:DECODER routines::unsupported
[2025/05/30 20:53:11.513627, 3] ssh_socket_unbuffered_write:  Enabling POLLOUT for socket
[2025/05/30 20:53:11.513659, 4] ssh_socket_unbuffered_write:  wrote 52
[2025/05/30 20:53:11.513674, 3] packet_send2:  packet: wrote [type=5, len=32, padding_size=14, comp=17, payload=17]
[2025/05/30 20:53:11.513687, 3] ssh_service_request:  Sent SSH_MSG_SERVICE_REQUEST (service ssh-userauth)
[2025/05/30 20:53:11.513710, 4] ssh_socket_pollcallback:  Poll callback on socket 3 (POLLOUT ), out buffer 0
[2025/05/30 20:53:11.513723, 4] ssh_socket_pollcallback:  sending control flow event
[2025/05/30 20:53:11.513735, 4] ssh_packet_socket_controlflow_callback:  sending channel_write_wontblock callback
[2025/05/30 20:53:11.514235, 4] ssh_socket_pollcallback:  Poll callback on socket 3 (POLLIN ), out buffer 0
[2025/05/30 20:53:11.514276, 4] ssh_socket_unbuffered_read:  read 452
[2025/05/30 20:53:11.514303, 3] ssh_packet_socket_callback:  packet: read type 7 [len=432,padding=8,comp=423,payload=423]
[2025/05/30 20:53:11.514328, 3] ssh_packet_process:  Dispatching handler for packet type 7
[2025/05/30 20:53:11.514337, 3] ssh_packet_ext_info:  Received SSH_MSG_EXT_INFO
[2025/05/30 20:53:11.514344, 3] ssh_packet_ext_info:  Follows 1 extensions
[2025/05/30 20:53:11.514354, 3] ssh_packet_ext_info:  Extension: server-sig-algs=<ssh-ed25519-cert-v01@xxxxxxxxxxx,ecdsa-sha2-nistp521-cert-v01@xxxxxxxxxxx,ecdsa-sha2-nistp384-cert-v01@xxxxxxxxxxx,ecdsa-sha2-nistp256-cert-v01@xxxxxxxxxxx,rsa-sha2-512-cert-v01@xxxxxxxxxxx,rsa-sha2-256-cert-v01@xxxxxxxxxxx,ssh-rsa-cert-v01@xxxxxxxxxxx,ssh-dss-cert-v01@xxxxxxxxxxx,ssh-ed25519,ecdsa-sha2-nistp521,ecdsa-sha2-nistp384,ecdsa-sha2-nistp256,rsa-sha2-512,rsa-sha2-256,ssh-rsa,ssh-dss>
[2025/05/30 20:53:11.555942, 4] ssh_socket_pollcallback:  Poll callback on socket 3 (POLLIN ), out buffer 0
[2025/05/30 20:53:11.555994, 4] ssh_socket_unbuffered_read:  read 52
[2025/05/30 20:53:11.556017, 3] ssh_packet_socket_callback:  packet: read type 6 [len=32,padding=14,comp=17,payload=17]
[2025/05/30 20:53:11.556026, 3] ssh_packet_process:  Dispatching handler for packet type 6
[2025/05/30 20:53:11.556034, 3] ssh_packet_service_accept:  Received SSH_MSG_SERVICE_ACCEPT
[2025/05/30 20:53:11.556044, 3] ssh_key_algorithm_allowed:  Checking rsa-sha2-512 with list <ecdsa-sha2-nistp256,ecdsa-sha2-nistp256-cert-v01@xxxxxxxxxxx,sk-ecdsa-sha2-nistp256@xxxxxxxxxxx,sk-ecdsa-sha2-nistp256-cert-v01@xxxxxxxxxxx,ecdsa-sha2-nistp384,ecdsa-sha2-nistp384-cert-v01@xxxxxxxxxxx,ecdsa-sha2-nistp521,ecdsa-sha2-nistp521-cert-v01@xxxxxxxxxxx,ssh-ed25519,ssh-ed25519-cert-v01@xxxxxxxxxxx,sk-ssh-ed25519@xxxxxxxxxxx,sk-ssh-ed25519-cert-v01@xxxxxxxxxxx,rsa-sha2-256,rsa-sha2-256-cert-v01@xxxxxxxxxxx,rsa-sha2-512,rsa-sha2-512-cert-v01@xxxxxxxxxxx>
[2025/05/30 20:53:11.556055, 3] ssh_key_algorithm_allowed:  Checking rsa-sha2-512 with list <ecdsa-sha2-nistp256,ecdsa-sha2-nistp256-cert-v01@xxxxxxxxxxx,sk-ecdsa-sha2-nistp256@xxxxxxxxxxx,sk-ecdsa-sha2-nistp256-cert-v01@xxxxxxxxxxx,ecdsa-sha2-nistp384,ecdsa-sha2-nistp384-cert-v01@xxxxxxxxxxx,ecdsa-sha2-nistp521,ecdsa-sha2-nistp521-cert-v01@xxxxxxxxxxx,ssh-ed25519,ssh-ed25519-cert-v01@xxxxxxxxxxx,sk-ssh-ed25519@xxxxxxxxxxx,sk-ssh-ed25519-cert-v01@xxxxxxxxxxx,rsa-sha2-256,rsa-sha2-256-cert-v01@xxxxxxxxxxx,rsa-sha2-512,rsa-sha2-512-cert-v01@xxxxxxxxxxx>
[2025/05/30 20:53:11.556089, 4] ssh_userauth_try_publickey:  Trying signature type rsa-sha2-512
[2025/05/30 20:53:11.556311, 3] ssh_socket_unbuffered_write:  Enabling POLLOUT for socket
[2025/05/30 20:53:11.556341, 4] ssh_socket_unbuffered_write:  wrote 372
[2025/05/30 20:53:11.556351, 3] packet_send2:  packet: wrote [type=50, len=352, padding_size=7, comp=344, payload=344]
[2025/05/30 20:53:11.556367, 4] ssh_socket_pollcallback:  Poll callback on socket 3 (POLLOUT ), out buffer 0
[2025/05/30 20:53:11.556374, 4] ssh_socket_pollcallback:  sending control flow event
[2025/05/30 20:53:11.556381, 4] ssh_packet_socket_controlflow_callback:  sending channel_write_wontblock callback
[2025/05/30 20:53:11.557232, 4] ssh_socket_pollcallback:  Poll callback on socket 3 (POLLIN ), out buffer 0
[2025/05/30 20:53:11.557281, 4] ssh_socket_unbuffered_read:  read 324
[2025/05/30 20:53:11.557305, 3] ssh_packet_socket_callback:  packet: read type 60 [len=304,padding=8,comp=295,payload=295]
[2025/05/30 20:53:11.557314, 3] ssh_packet_process:  Dispatching handler for packet type 60
[2025/05/30 20:53:11.557323, 4] ssh_packet_userauth_pk_ok:  Received SSH_USERAUTH_PK_OK/INFO_REQUEST/GSSAPI_RESPONSE
[2025/05/30 20:53:11.557330, 4] ssh_packet_userauth_pk_ok:  Assuming SSH_USERAUTH_PK_OK
[2025/05/30 20:53:11.557402, 3] ssh_pki_import_privkey_base64:  Trying to decode privkey passphrase=false
[2025/05/30 20:53:11.557574, 3] ssh_key_algorithm_allowed:  Checking rsa-sha2-512 with list <ecdsa-sha2-nistp256,ecdsa-sha2-nistp256-cert-v01@xxxxxxxxxxx,sk-ecdsa-sha2-nistp256@xxxxxxxxxxx,sk-ecdsa-sha2-nistp256-cert-v01@xxxxxxxxxxx,ecdsa-sha2-nistp384,ecdsa-sha2-nistp384-cert-v01@xxxxxxxxxxx,ecdsa-sha2-nistp521,ecdsa-sha2-nistp521-cert-v01@xxxxxxxxxxx,ssh-ed25519,ssh-ed25519-cert-v01@xxxxxxxxxxx,sk-ssh-ed25519@xxxxxxxxxxx,sk-ssh-ed25519-cert-v01@xxxxxxxxxxx,rsa-sha2-256,rsa-sha2-256-cert-v01@xxxxxxxxxxx,rsa-sha2-512,rsa-sha2-512-cert-v01@xxxxxxxxxxx>
[2025/05/30 20:53:11.557604, 3] ssh_key_algorithm_allowed:  Checking rsa-sha2-512 with list <ecdsa-sha2-nistp256,ecdsa-sha2-nistp256-cert-v01@xxxxxxxxxxx,sk-ecdsa-sha2-nistp256@xxxxxxxxxxx,sk-ecdsa-sha2-nistp256-cert-v01@xxxxxxxxxxx,ecdsa-sha2-nistp384,ecdsa-sha2-nistp384-cert-v01@xxxxxxxxxxx,ecdsa-sha2-nistp521,ecdsa-sha2-nistp521-cert-v01@xxxxxxxxxxx,ssh-ed25519,ssh-ed25519-cert-v01@xxxxxxxxxxx,sk-ssh-ed25519@xxxxxxxxxxx,sk-ssh-ed25519-cert-v01@xxxxxxxxxxx,rsa-sha2-256,rsa-sha2-256-cert-v01@xxxxxxxxxxx,rsa-sha2-512,rsa-sha2-512-cert-v01@xxxxxxxxxxx>
[2025/05/30 20:53:11.557636, 4] ssh_userauth_publickey:  Sending signature type rsa-sha2-512
[2025/05/30 20:53:11.557649, 3] ssh_key_algorithm_allowed:  Checking rsa-sha2-512 with list <ecdsa-sha2-nistp256,ecdsa-sha2-nistp256-cert-v01@xxxxxxxxxxx,sk-ecdsa-sha2-nistp256@xxxxxxxxxxx,sk-ecdsa-sha2-nistp256-cert-v01@xxxxxxxxxxx,ecdsa-sha2-nistp384,ecdsa-sha2-nistp384-cert-v01@xxxxxxxxxxx,ecdsa-sha2-nistp521,ecdsa-sha2-nistp521-cert-v01@xxxxxxxxxxx,ssh-ed25519,ssh-ed25519-cert-v01@xxxxxxxxxxx,sk-ssh-ed25519@xxxxxxxxxxx,sk-ssh-ed25519-cert-v01@xxxxxxxxxxx,rsa-sha2-256,rsa-sha2-256-cert-v01@xxxxxxxxxxx,rsa-sha2-512,rsa-sha2-512-cert-v01@xxxxxxxxxxx>
[2025/05/30 20:53:11.561099, 3] ssh_socket_unbuffered_write:  Enabling POLLOUT for socket
[2025/05/30 20:53:11.561137, 4] ssh_socket_unbuffered_write:  wrote 660
[2025/05/30 20:53:11.561147, 3] packet_send2:  packet: wrote [type=50, len=640, padding_size=15, comp=624, payload=624]
[2025/05/30 20:53:11.561164, 4] ssh_socket_pollcallback:  Poll callback on socket 3 (POLLOUT ), out buffer 0
[2025/05/30 20:53:11.561172, 4] ssh_socket_pollcallback:  sending control flow event
[2025/05/30 20:53:11.561179, 4] ssh_packet_socket_controlflow_callback:  sending channel_write_wontblock callback
[2025/05/30 20:53:11.563565, 4] ssh_socket_pollcallback:  Poll callback on socket 3 (POLLIN ), out buffer 0
[2025/05/30 20:53:11.563614, 4] ssh_socket_unbuffered_read:  read 36
[2025/05/30 20:53:11.563636, 3] ssh_packet_socket_callback:  packet: read type 52 [len=16,padding=14,comp=1,payload=1]
[2025/05/30 20:53:11.563645, 3] ssh_packet_process:  Dispatching handler for packet type 52
[2025/05/30 20:53:11.563653, 3] ssh_packet_userauth_success:  Authentication successful
[2025/05/30 20:53:11.563660, 4] ssh_packet_userauth_success:  Received SSH_USERAUTH_SUCCESS
[2025/05/30 20:53:11.563669, 3] ssh_packet_need_rekey:  rekey: [data_rekey_needed=0, out_blocks=61, in_blocks=45]
[2025/05/30 20:53:11.563692, 3] ssh_userauth_publickey_auto:  Successfully authenticated using /home/useruser/id_rsa
[2025/05/30 20:53:11.563718, 3] ssh_packet_need_rekey:  rekey: [data_rekey_needed=0, out_blocks=62, in_blocks=46]
[2025/05/30 20:53:11.563869, 3] ssh_socket_unbuffered_write:  Enabling POLLOUT for socket
[2025/05/30 20:53:11.563888, 4] ssh_socket_unbuffered_write:  wrote 52
[2025/05/30 20:53:11.563897, 3] packet_send2:  packet: wrote [type=1, len=32, padding_size=11, comp=20, payload=20]
Connected and authenticated with key!

References:
Re: The key algorithm 'ssh-rsa' is not allowed in V 0.10.4Jakub Jelen <jjelen@xxxxxxxxxx>
Re: The key algorithm 'ssh-rsa' is not allowed in V 0.10.4g4-lisz@xxxxxxxxxxxx
Re: The key algorithm 'ssh-rsa' is not allowed in V 0.10.4g4-lisz@xxxxxxxxxxxx
Re: The key algorithm 'ssh-rsa' is not allowed in V 0.10.4g4-lisz@xxxxxxxxxxxx
Re: The key algorithm 'ssh-rsa' is not allowed in V 0.10.4Andreas Schneider <asn@xxxxxxxxxxxxxx>
Re: The key algorithm 'ssh-rsa' is not allowed in V 0.10.4Jakub Jelen <jjelen@xxxxxxxxxx>
Re: The key algorithm 'ssh-rsa' is not allowed in V 0.10.4g4-lisz@xxxxxxxxxxxx
Re: The key algorithm 'ssh-rsa' is not allowed in V 0.10.4Jakub Jelen <jjelen@xxxxxxxxxx>
Re: The key algorithm 'ssh-rsa' is not allowed in V 0.10.4g4-lisz@xxxxxxxxxxxx
Re: The key algorithm 'ssh-rsa' is not allowed in V 0.10.4Jakub Jelen <jjelen@xxxxxxxxxx>
Re: The key algorithm 'ssh-rsa' is not allowed in V 0.10.4g4-lisz@xxxxxxxxxxxx
Re: The key algorithm 'ssh-rsa' is not allowed in V 0.10.4Jakub Jelen <jjelen@xxxxxxxxxx>
Re: The key algorithm 'ssh-rsa' is not allowed in V 0.10.4g4-lisz@xxxxxxxxxxxx
Re: The key algorithm 'ssh-rsa' is not allowed in V 0.10.4Jakub Jelen <jjelen@xxxxxxxxxx>
Re: The key algorithm 'ssh-rsa' is not allowed in V 0.10.4g4-lisz@xxxxxxxxxxxx
Re: The key algorithm 'ssh-rsa' is not allowed in V 0.10.4Jakub Jelen <jjelen@xxxxxxxxxx>
Re: The key algorithm 'ssh-rsa' is not allowed in V 0.10.4g4-lisz@xxxxxxxxxxxx
Re: The key algorithm 'ssh-rsa' is not allowed in V 0.10.4Jakub Jelen <jjelen@xxxxxxxxxx>
Re: The key algorithm 'ssh-rsa' is not allowed in V 0.10.4g4-lisz@xxxxxxxxxxxx
Archive administrator: postmaster@lists.cynapses.org