libssh2_session_methods(3)

✨ libssh2_session_methods — bestie, let's find out which algorithms are ACTUALLY running 💅

ok so real talk: this is the libssh2 function that tells you which algorithms your session ended up using. Like, you asked for a whole menu of options and SSH picked one — this is how you find out which one. Iconic behaviour fr fr. 🦋

🌸 SYNOPSIS 🌸

#include <libssh2.h>

const char *
libssh2_session_methods(LIBSSH2_SESSION *session, int method_type);

💖 DESCRIPTION 💖

So you pass in two things, bestie:

• session — the session instance, aka the thing you got back from libssh2_session_init_ex(3). You know her. 👑
• method_type — literally just one of these method type constants, pick your fighter:
  • LIBSSH2_METHOD_KEX
  • LIBSSH2_METHOD_HOSTKEY
  • LIBSSH2_METHOD_CRYPT_CS
  • LIBSSH2_METHOD_CRYPT_SC
  • LIBSSH2_METHOD_MAC_CS
  • LIBSSH2_METHOD_MAC_SC
  • LIBSSH2_METHOD_COMP_CS
  • LIBSSH2_METHOD_COMP_SC
  • LIBSSH2_METHOD_LANG_CS
  • LIBSSH2_METHOD_LANG_SC
  • LIBSSH2_METHOD_SIGN_ALGO

And what does it do?? It returns the actual method negotiated for that particular transport parameter. Not the list you offered. Not the list they offered. The one that actually got picked. The main character. 🌟

🎀 RETURN VALUE 🎀

You get the negotiated method back as a string. 💫

But — and this is the plot twist — you get NULL if the session has not yet been started. Like, girl hasn't even shown up to the party yet, there's nothing to report. 😭

💀 ERRORS 💀

• LIBSSH2_ERROR_INVAL — the requested method type was invalid. You handed it a constant that doesn't exist, bestie, that's on you. 🙈
• LIBSSH2_ERROR_METHOD_NONE — no method has been set. Empty. Void. Nothing there. 💀

🌈 SEE ALSO 🌈

• libssh2_session_init_ex(3)

and that's the whole vibe check, babe — go forth and inspect your transport parameters, you absolute legend 🫶✨

mwah 💋 this page lives in libssh2 1.11, dated 8 Nov 2021, and it's part of the libssh2 manual — now go slay some SSH 💅👑