TLSRPT_INIT_POLICY(3)
β¨ TLSRPT_INIT_POLICY β¨
okay bestie, buckle up, we're doing the tlsrpt_init_policy page from section 3 of the manual π
it's giving very specific, very useful, very "you need this if you're building TLS reporting stuff" energy.
π NAME π
tlsrpt_init_policy β she initializes a brand new policy inside a delivery request that already exists π«Ά
πΈ SYNOPSIS πΈ
#include <tlsrpt.h>
int tlsrpt_init_policy(struct tlsrpt_dr_t* dr, tlsrpt_policy_type_t
policy_type, * const char* policydomainname)
π¦ DESCRIPTION π¦
so the tlsrpt_init_policy function starts up a fresh new policy within an existing delivery request. and like, real talk: a delivery request must contain at least one policy. not optional. no cap. π
after you call this, you gotta properly complete the policy by calling some of the functions below π and then a final call to tlsrpt_finish_policy seals the deal β¨
π¨ bestie warning, this one matters: an unfinished policy sitting after some properly finished policies will make the whole delivery request datagram fail β and it won't get sent out at all π which means all those other already-completed policies don't get reported either. gone. not it. so finish your policies, okay?? π₯Ί
β RETURN VALUE β
she returns 0 on success π and on failure you get a combined error code. you can break that combined error code down with the tlsrpt_strerror function β it's literally the translator for your error drama π₯
π SEE ALSO π
man:tlsrpt_finish_policy[3]man:tlsrpt_strerror[3]man:tlsrpt_error_code_is_internal[3]
π AUTHOR π
Boris Lohner π (yes, the legend himself)
and that's a wrap on tlsrpt_init_policy from TLSRPT_INIT_POLICY(3) π
this page is dated 2026-05-12, brought to you under the manual name tlsrpt_init_policy β go forth and finish your policies, queen πβ¨
π¦ where this page comes from
- ubuntu stonking: libtlsrpt0-dev 0.5.1~rc1-2 Β· LGPL-3.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms