Discussion · bonfire.cafe

@BastilleBSD@fosstodon.org · 2 weeks ago

I'm not getting much traction on a couple of reported issues in #FreeBSD ports.

Can some ports maintainers / committers take a look at these please?

These changes fully BROKE every adguardhome installation and need to be FULLY reverted. I've reported as such, but have not seen any responses.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=294574

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=294711

#FreeBSD #ports #adguardhome

294711 – www/adguardhome: revert broken portacl inclusions

#ports #AdGuardHome #freebsd

JdeBP

@JdeBP@tty0.social · 2 weeks ago

@BastilleBSD

Making #AdGuardHome capable of receiving its listening socket, already created and bound, from the thing that invoked it has been on its issues list for a year without any seeming motion at all.

https://github.com/AdguardTeam/AdGuardHome/issues/7859

JdeBP

@JdeBP@tty0.social · 2 weeks ago

@BastilleBSD

Yes, there exist #FreeBSD tools that can set up the socket and the environment variable. I wrote one such tool years ago, and have been running a DNS server that accepts pre-created listening sockets and itself runs wholly unprivileged for almost as long.

Tell any naysayers that it can be done. (-:

http://jdebp.info/Softwares/nosh/guide/commands/udp-socket-listen.xml

http://jdebp.info/Softwares/djbwares/guide/commands/dnscache.xml

#dnscache #nosh #AdGuardHome

David Chisnall (*Now with 50% more sarcasm!*)

@david_chisnall@infosec.exchange · 2 weeks ago

@JdeBP @BastilleBSD

Do you have a TCP / UNIX socket version? I’d been planning on writing one to use with Docker storage plugins that all expect socket activation.

JdeBP

@JdeBP@tty0.social · 2 weeks ago

@david_chisnall

dnscache, as you can see from that manual, needs both TCP and UDP listening sockets, so there's a TCP tool. The service ./run script for the DNS server chains through both tools.

There are also the three different kinds of AF_LOCAL listener tools.

http://jdebp.info/Softwares/nosh/guide/commands.html#UCSPIChainLoading

@BastilleBSD
#nosh

Jason Tubnor 🇦🇺

@tubsta@social.bsdlab.au · 2 weeks ago

@BastilleBSD I think the #FreeBSD project/core team need to look at improving how the ports team interact with the community and be on top of the portfolio more, especially in light of the influx of Linux users escaping the hellscape occurring over there.

I don't buy the whole, "we have limited resources" as I have seen gate-keeping at its finest.

Personally I have proposed and provided patches the correct documented way that sat in the bug tracker for almost 2.5 years, with no way to escalate or get them committed, so I had to carry them myself until someone with some clout was able to get something done. This should not happen.

My experience with #OpenBSD is polar opposite, propose a patch, post it in ports@, gets reviewed and it is in the tree in a couple of days. If the maintainer doesn't respond, someone else does it. No ifs, no buts, stuff happens and things move forward.

I'd like to point out that the above case with FreeBSD ports is not a reflection on the rest of the project. The team that work on base, kernel and security/errata are very receptive, are easy to communicate with don't leave users out to dry when issues arise.

cc: @dch

AkkomaBSD Lab Australia/Oceania

Vysogota

@petko@social.petko.me · 3 hours ago

@tubsta @dch @BastilleBSD I am against complaining against volunteers.

Jason Tubnor 🇦🇺

@tubsta@social.bsdlab.au · 2 hours ago

@petko @dch @BastilleBSD Totally. Especially when volunteering efforts go unnoticed when people put in the time and effort and it is totally ignored.

Vysogota

@petko@social.petko.me · 2 hours ago

@tubsta @dch @BastilleBSD I think that's entitled behaviour. The rights you are actually entitled to are limited to having the source at your disposal to review, modify, and share.

You are not entitled to the maintainers' time and attention. This means you are not entitled to have your changes merged, or even considered and reviewed.

~1 more replies

Jason Tubnor 🇦🇺

@tubsta@social.bsdlab.au · 1 hour ago

@petko @dch @BastilleBSD No problems. We can agree to disagree. But if you are the active maintainer, relinquish it and let someone else do it.

dch :flantifa: :flan_hacker:

@dch@bsd.network · 1 hour ago

@tubsta it’s super frustrating all round.

As a contributor I hate seeing stuff languish.

As a committer I feel bad that it doesn’t get done.

That said I have seen exactly the same issues with every open source project I’ve worked with from open and free BSD through large Apache projects & random github stuff.

After seeing this frustration for over 25 years now I have a simple way of getting my attention on this matter: a contract.

https://m.youtube.com/watch?v=jVkLVRt6c1U

@petko @BastilleBSD