dnsjit.output.tlscli(3)

💅 dnsjit.output.tlscli — the manual page, but make it cute

okay bestie, welcome to dnsjit.output.tlscli(3) from the dnsjit library, section 3 of the manual. it's literally a Simple TLS client and i'm obsessed. let's get into it 🎀

---

✨ NAME ✨

dnsjit.output.tlscli — a Simple TLS client, no cap 💖

---

🌸 SYNOPSIS 🌸

local output = require("dnsjit.output.tlscli").new("127.0.0.1", "853")

look at her. two strings in, an output object out. iconic behavior. 👑

---

🦋 DESCRIPTION 🦋

so basically: it's a Simple TLS client that attempts to do a TLS handshake — and bestie, listen — without certificate verification. i'm just the messenger, that's what the page says. 🙈

it behaves the same way as tcpcli, except all the data is sent over the encrypted channel. same energy, but make it secure-ish. 🔥

⭐ Attributes

• timeout — a core.timespec that gets used when producing objects. that's it, that's the whole attribute. she's simple, she's effective. 💅

💜 Functions

• Tlscli.new() — create a new Tlscli output. fresh out the box, brand new, main character energy. ✨
• Tlscli:timeout(seconds, nanoseconds) — set the timeout for when objects are being produced. give her seconds and nanoseconds, she'll handle the rest. ⏰
• Tlscli:connect(host, port) — connect to the host and port, perform a TLS handshake, and return 0 if it worked. that 0 is the little "slay, we're in" signal. 🫶
• Tlscli:receive() — return the C functions and context for receiving objects. and these objects? they get sent. 📤
• Tlscli:produce() — return the C functions and context for producing objects. these objects are received. the producer will wait for data, and if it times out (see timeout, bestie, she's back) it will return a payload object with length zero.

and now the important part: if a timeout happens during the first stage — getting the length — it will fail and return nil. 😭 additional calls will continue retrieving the payload. and the producer returns nil on error too. so if you see nil, something said no. fr fr.

• Tlscli:packets() — return the number of "packets" sent. and yes, the quotes around "packets" are doing a lot of work here, because it's actually the number of completely sent payloads. 🎀
• Tlscli:received() — return the number of "packets" received, which is actually the number of completely received DNS messages. see what i mean? quotes carrying the whole team. 😌
• Tlscli:errors() — return the number of errors when sending. hopefully 0, but she's keeping count either way. 💀

---

👑 AUTHORS and CONTRIBUTORS 👑

the legends behind this:

• Jerry Lundström (DNS-OARC)
• Tomáš Křížek (CZ.NIC)
• Petr Špaček (ISC)

Maintained by DNS-OARC

https://www.dns-oarc.net/

the way they maintain it… periodt. 🌈

---

🍓 BUGS 🍓

found a bug? need a feature? bestie, please use:

https://codeberg.org/DNS-OARC/dnsjit/issues

got a question, or just need a hand? use:

admin@dns-oarc.net

they're nice, i promise. go say hi. 💖

---

okay that's the whole page, no skips, no shortcuts, every flag and every function accounted for. 🧚

this was dnsjit version 1.5.1, and the page you just read is dnsjit.output.tlscli(3). mwah, take care of her 💅✨