gsasl_scram_sec...salted_password(3)

πŸ’– gsasl_scram_sec...salted_password β€” NAME ✨

okay bestie, this page lives in the gsasl manual, and what we're looking at here is gsasl_scram_secrets_from_salted_password β€” the API function, periodt. πŸŽ€


🌸 SYNOPSIS πŸ¦‹

#include <gsasl.h>

int gsasl_scram_secrets_from_salted_password(Gsasl_hash hash, const char
 * salted_password, char * client_key, char * server_key, char *
 stored_key);

πŸ‘‘ ARGUMENTS πŸ’…

  • Gsasl_hash hash β€” a Gsasl_hash element, like for real, e.g. GSASL_HASH_SHA256. ✨
  • const char * salted_password β€” the input array, holding your salted password. that's the starting point fr fr.
  • char * client_key β€” a pre-allocated output array that's gonna get the derived client key dropped into it. 🫢
  • char * server_key β€” another pre-allocated output array, this one catching the derived server key. πŸ’œ
  • char * stored_key β€” yep, pre-allocated output array too, and the derived stored key lands here. πŸ“

🌈 DESCRIPTION 🧚

it's a helper function, bestie β€” its whole job is deriving the SCRAM ClientKey/ServerKey/StoredKey. iconic behaviour honestly.

the client_key, server_key, and stored_key buffers must have room to hold the digest for the given hash, okay? use GSASL_HASH_MAX_SIZE, which is sufficient for all hashes. no cap. πŸ’―

Return value: it hands you GSASL_OK if everything slayed, or an error code if it did not. 😭


⭐ SINCE 🌟

1.10

like, she's been around. vintage queen. πŸ‘‘


πŸ’€ REPORTING BUGS πŸ›

found a bug? tell the people:

Report bugs to <bug-gsasl@gnu.org>.

General guidelines for reporting bugs: https://www.gnu.org/gethelp/

GNU SASL home page: https://www.gnu.org/software/gsasl/


Copyright Β© 2002-2026 Simon Josefsson.

Copying and distribution of this file, with or without modification, are permitted in any medium without royalty provided the copyright notice and this notice are preserved.


πŸ¦‹ SEE ALSO ✨

The full documentation for gsasl is maintained as a Texinfo manual. If the info and gsasl programs are properly installed at your site, the command

info gsasl

should give you access to the complete manual. As an alternative you may obtain the manual from:

https://www.gnu.org/software/libidn/gsasl/manual/

and that's the whole vibe check, bestie 🫢 this page came straight out of gsasl version 2.2.4, so go forth and derive those keys. slay. πŸ’…βœ¨πŸŽ€

πŸ“¦ where this page comes from