Munin::Common::TLS(3)
π NAME π
okay bestie, the manual name up top is Munin::Common::TLS(3) β User Contributed Perl Documentation energy β¨ β but the NAME line itself says Munin::Node::TLS: the abstract base class implementing the STARTTLS protocol. Yes, those are both literally in there, and yes, we're keeping both. π
β¨ SYNOPSIS β¨
Do not call this directly, bestie β no cap. Go look at the synopsis for Munin::Common::TLSServer and Munin::Common::TLSClient instead. π«Ά
π METHODS π
πΈ new πΈ
my $tls = Munin::Common::TLSFoo->new({ # Substitute Foo with Client or Server
# Mandatory attributes:
logger => \&a_logger_func,
read_fd => fileno($socket),
read_func => \&a_socket_read_func,
write_fd => fileno($socket),
write_func => \&a_socket_read_func,
# Optional attributes DEFAULTS
DEBUG => 0, # 0
tls_ca_cert => "path/to/ca/cert.pem", # ''
tls_cert => "path/to/cert.pem", # ''
tls_paranoia => 1, # 0
tls_priv => "path/to/priv_key.pem", # ''
tls_vdepth => 5, # 0
tls_verify => 1, # 0
});
This is the constructor, and it should not be called directly. What it does document is the attributes that are in common for Munin::Common::TLSServer and Munin::Common::TLSClient. The mandatory ones are logger, read_fd, read_func, write_fd, and write_func; the optional ones and their defaults are right there in the code block, iykyk. π
π¦ read π¦
my $msg = $tls->read();
Encrypted read. That's it. That's the whole vibe. π₯
π write π
$tls->write($msg);
Encrypted write. Slay. π
β session_started β
my $bool = $tls->session_started();
Returns true if the TLS object is ready to read/write encrypted data. Basically the vibe check for "are we encrypted and ready or not." π
mwah π this page is literally perl v5.42.3, dated 1980-01-01, and the footer manual name is Munin::Common::TLS(3) β bye bestie π«Άβ¨
π¦ where this page comes from
- nixos 26.05: munin 2.0.76
- nixpkgs unstable: munin 2.0.78
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms