@wild1145

Does your system show stats about how many transactions connections serviced before they closed? Or, alternatively, what the lifetimes of established connections are?

I'm asking because I'm putting the occasional knob into the HTTP server in #djbwares and you've made me think about transaction caps and what's reasonable when one is under attack from an LLM scraper; when one really doesn't want the attacker to be able to hold existing connections open indefinitely.

#httpd

@BastilleBSD

So you're not interested in those who go the whole hog and run their own private root content DNS servers. (-:

http://jdebp.info/Softwares/djbwares/guide/dns-private-root.html

#DomainNameSystem #djbwares

@ska

Scarily, Bing's bloody LLM seems to know exactly what the mechanism is 9 months after I put it in.

How the Hell has it found that out? I haven't even put it in the Guide. I did the search to see if I'd ever mentioned it.

Here's the Guide, which does tell you that you need redo.

http://jdebp.info/Softwares/djbwares/guide/building-from-source.html

And here's the mechanism. Perhaps Bing somehow matched the name of the variable.

https://github.com/jdebp/djbwares/blob/trunk/source/cc.do#L8

#djbwares

@ska

Actually, it's the same source tree just compressed differently, and multiply-redundant copies across the repository sites. There's only one set of source for everything.

It would actually be the same compression if everyone's pax supported bzip2. (-:

There's also a simple bypass mechanism if the GCC or clang desired aren't the ones found in PATH, for cross-compiling and whatnot. Someone here asked for it.

#djbwares

@ska

Well you should be done with that. It's about time. (-:

It's been a long time since the world was *anything like* that.

I've been actively maintaining #djbwares for 13 years. Erwin Hoffmann has been maintaining #djbdnscurve6 for I think 8 years.

We both provide source in one go, zero patching involved. I've provided Debian and FreeBSD binaries packages for years, too. djbdnscurve6 has been in pkgsrc since 2019.

Hell, even the kids just fork ndjbdns entirely now. Patches⁈ (-:

@ska

Sugar for AAAA records was done in 2025 by me. Felix von Leitner did it differently 25 years earlier, but I didn't like that it required two parallel toolsets and sets of record types. My way, it's just an IPv6 address in the same '+' records.

That's been available for a *long* time.

#djbdns #djbwares

@ska

Anyway, who the Hell is this community that thinks that the original #djbdns is the be-all and end-all?

Let me know, and I'll show them #djbwares, where I've got a whole long list of things that have been improved, from IPv6 support through a non-hexdump way of doing SRV records to not letting ANY queries be amplification attack puppets.

http://jdebp.info/Softwares/djbwares/guide/changes.html

@ska

An additional fun factor is that wildcards in #djbdns by design don't work like wildcards in BIND. The difference was much discussed a quarter of a century ago.

So any bug reports that assume that wildcards in djbdns databases are supposed to behave like they do in BIND's 'zone' files need to be checked for proper foundation.

And with RFC 4592 an even greater divergence then happened.

#djbwares #DNS #shibari

@arstechnica @dangoodin

Not to be confused with #daemontools, a different (and older) piece of software entirely that is approaching 30 years old, still going, and probably really hard to perform a supply chain attack on.

http://jdebp.info/FGA/daemontools-family.html
#djbwares