shishi_as_check_cname(3)

📦
version 1.0.3 · 2 versions
  • 1.0.3 · debian bookworm, debian trixie, nixos 26.05, nixpkgs unstable, ubuntu noble, ubuntu questing, ubuntu resolute, ubuntu stonking (latest)
  • 1.0.2 · ubuntu jammy
, in debian bookworm, debian trixie, nixos 26.05, nixpkgs unstable, ubuntu noble, ubuntu questing, ubuntu resolute, ubuntu stonking

💖 shishi_as_check_cname — the vibe check for names 💖

okay so bestie, this is a page from the shishi manual, section 3 (that's the library-functions girlypop section, iykyk). It's all about one tiny little function that does one tiny little job, and honestly? she eats. Let's get into it. 🎀

✨ NAME ✨

shishi_as_check_cname — it's an API function, bestie. That's literally her whole thing. No cap. 💅

🌸 SYNOPSIS 🌸

#include <shishi.h>

int shishi_as_check_cname(Shishi * handle, Shishi_asn1 asreq,
Shishi_asn1 asrep);

like… look at her. three arguments. returns an int. she's not complicated, she's just important. 🦋

🫶 ARGUMENTS 🫶

  • Shishi * handle — the Shishi handle, and you get one of these from shishi_init(). so like, you already have it, or you go get it. don't show up to the function empty-handed fr fr. 💜
  • Shishi_asn1 asreq — the request, and it's gotta be of type AS-REQ. that's the vibe. that's the type. no substitutions. ✨
  • Shishi_asn1 asrep — the reply structure, type AS-REP. yes, it's a structure. yes, it's the reply. we love a matched set. 🍓

👑 DESCRIPTION 👑

so here's the tea, and the tea is actually really simple: this function verifies that the fields asreq.req-body.cname and asrep.cname contain identical names.

that's it. that's the whole job. she looks at the cname in the request, she looks at the cname in the reply, and she goes "…are these the same bestie? 👀"

and like, this is not optional busywork, okay? this is one of the steps that has to be performed when you're processing an exchange of AS-REQ and AS-REP. HAS to. it's giving mandatory. it's giving "you will not skip this." 🔥

if you want the full lore on where this fits in the whole flow, go read shishi_kdc_process() — that's where the more-details live. 🌈

⭐ RETURN VALUE ⭐

she returns an int, and here's how to read her mood:

  • SHISHI_OK — yay! it worked! the names match, we're slaying, everything's fine 💖
  • SHISHI_CNAME_MISMATCH — 🚨 the names differ. something is wrong. look into it.
  • and, y'know, an error code otherwise — because life is unpredictable and sometimes it's just not about the names at all 😭

🐛 REPORTING BUGS 🐛

found a bug? don't be shy, don't suffer in silence, tell the people:

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

like, they want to know. this is a safe space. 🫶

Copyright © 2002-2022 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.

(iconic of them honestly — no royalty, any medium, just keep the notice. periodt. 👑)

🦋 SEE ALSO 🦋

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

info shishi

should give you access to the complete manual. that's the whole manual bestie, the motherlode, the main character of documentation. go read her. 📚✨

and that's the page!! mwah 💅

this was shishi version 1.0.3, and you just read shishi_as_check_cname(3) from the shishi manual. take care of your cnames and they'll take care of you 🎀💖🦋

📦 where this page comes from