pskc_get_device_issueno(3)

πŸ’– pskc_get_device_issueno(3) πŸ’–

okay so bestie, welcome to the pskc_get_device_issueno page β€” part of the libpskc manual, and honestly? it's giving "small function, big main character energy" ✨


🌸 NAME 🌸

pskc_get_device_issueno β€” the API function that grabs a device's issue number for u πŸ’…


✨ SYNOPSIS ✨

#include <pskc.h>

const char * pskc_get_device_issueno(pskc_key_t * key);

πŸŽ€ ARGUMENTS πŸŽ€

  • pskc_key_t * key β€” a pskc_key_t handle, and you get it from pskc_get_keypackage(). that's the whole vibe, no cap 🫢

πŸ¦‹ DESCRIPTION πŸ¦‹

Get the PSKC KeyPackage DeviceInfo IssueNo value. literally what it says on the tin πŸ’…

so like, this element holds the issue number β€” and here's the iykyk part: it's for when you've got devices with the same serial number, so the issue numbers are what let you tell them apart. two devices, same serial, different issue number β†’ distinguished, periodt πŸ‘‘


⭐ RETURNS ⭐

a constant string (must not be deallocated, bestie, do not free it, I'm serious 😭) holding the content β€” or NULL if it's not set. simple as that 🌈


πŸ”₯ REPORTING BUGS πŸ”₯

found a bug? don't suffer in silence, report it to <oath-toolkit-help@nongnu.org> πŸ“¬

libpskc home page: https://oath-toolkit.codeberg.page/

General help using GNU software: http://www.gnu.org/gethelp/


Copyright Β© 2009-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. iconic, honestly 🫢


<div align="center">🌸 πŸ’– 🌸</div>

k that's the whole page, mwah πŸ’‹ β€” brought to you by libpskc version 2.6.15, aka the pskc_get_device_issueno(3) era. go forth and distinguish those serial-number twins πŸ§šβ€β™€οΈβœ¨

πŸ“¦ where this page comes from