Kyle Evans

FreeBSD 14.4-RELEASE is now available: lists.freebsd.org/archives/freeb…

@XNUniverse What did you have in mind? I think, ideally, we'd integrate some jail descriptor rights(4) that you can revoke prior to passing it. We still do a priv(9) check, but that probably just means a right not granted when the descriptor is synthesized.

I’m going to hold off on implanting jail descriptors in SwiftBSD. It doesn’t make sense that you can hand a descriptor to a less privileged process with the capability to kill everything in the jail. I’ll work on getting the upstream FreeBSD kernel fixed first.

The (uninstrumented thing) could be anything. Consider scenarios like: I want to fuzz a thing that receives data over the network. I can take a lot of liberties with how it's started, but I'd rather not modify it more than adding the necessary instrumentation.

... to have a fuzzer that splits input from the feedback. Ideally: (input server) -> (uninstrumented thing) -> (instrumented binary)

Does the kind of fuzzer I want exist? AFL and libFuzzer typically (exclusively?) operate in a model where (hand-wave) they're expcted to immediately run (or be resident in) the instrumented program, but I've run into two separate scenarios where it'd be incredibly useful...

@cperciva Ah, saw a video earlier of someone referring to the Epstein files for their copy of the bash reference manual and man page, too

Apparently I'm in the Epstein files. Actually, a lot of open source software developers are; there's a 205 page PDF with licenses of software used in an unnamed Apple product. Also, Sesame Street appears in 31 files, Winnie-the-Pooh appears in 9 files, and Reading Rainbow in 1.

@bexcran wat

Just chatted with Tesla about my PowerWall not taking over when I flip my main breaker. He told me not to flip that one but to turn off the smaller ones - 30A etc. instead. 😂 Then he ran a backup test after asking me to reduce load - which only tested that I can run off solar.

@cperciva @awsmarketplace Is this a change in policy that actually negatively impacts us, or a change in enforcement of a policy that shouldn't affect us?

@awsmarketplace Ok, @awsmarketplace just rejected FreeBSD 15.0 because "Customers must be able to easily get help with issues, such as using the services, troubleshooting, and requesting refunds (if applicable). Support contact options must be specified on the fulfillment landing page."

Adding FreeBSD 15.0 to the @awsmarketplace. First I have to click through a list of 1048 instance types selecting the ones FreeBSD runs on (no, there's no "select all"). Then it asks me what the refund policy is for the free product.

@depach @cperciva @BSDCan They're typically livestreamed and later published to YouTube, fwiw

@cperciva @BSDCan Bit far to attend but I am very interested in release engineering processes and would enjoy the talk if I could attend 👍

Would anyone be interested in hearing me talk at @BSDCan about the process behind FreeBSD 15.0? Release engineering and generally all the "behind the scenes" stuff which doesn't show up in a git repository.

@cperciva Sorry to hear that. =\

I have no intention of quitting the job of FreeBSD release engineering lead, but I never want to do a release like 15.0 again. This has been a huge undertaking, even by "major FreeBSD release" standards.

The human body exhibits a wonderful homeostatic effect: If you try to work too much, the stress and sleep deprivation suppress your immune system until you get sick and are forced to stop working so much.

@real_redp @_Felipe @michael__ni @FFmpeg sure, but at that volume I could see the temptation to just let the fuzzer raise the alarm if it crops back up. I can't speak for professional fuzzing setups, but for me, on something like this the case would get added to my corpus and thus, very regularly re-tested by my fuzzers

@_Felipe @michael__ni @FFmpeg sure I am old and dumb but tests anyway should be placed somewhere to avoid bugs in next versions, no?

I am the main developer fixing security issues in FFmpeg. I have fixed over 2700 google oss fuzz issues. I have fixed most of the BIGSLEEP issues. And i disagree with the comments @ffmpeg (Kieran) has made about google. From all companies, google has been the most helpfull & nice

I will be at the FreeBSD vendor summit in San Jose, California, on November 6-7. If you're in the area and your company uses FreeBSD, you should probably be there too. freebsdfoundation.org/news-and-event…

FreeBSD 15.0-ALPHA4 is now available: lists.freebsd.org/archives/freeb… As with ALPHA3, *do not use freebsd-update to upgrade yet*. An Errata Notice will be coming out shortly to fix a critical bug in freebsd-update.

@cperciva Favorite function I've named in the past N years: pkg_is_pkg_pkg in pkg(7)

Language gets hard when the packaging tool and the package CDN both share the name "pkg" (pronounced "package"): "We have to build a package package from the ports tree because we don't have a package package on package dot freebsd dot org yet."

@Andrath1975 @kuntal_kundu @freebsd @netflix "Blame"? I tend to think we're more productive that way, eh? "Shit, I'm bored, what do I do now?" -> not watch Netflix, apparently- I guess we'll just hack on something instead.

@kuntal_kundu @freebsd @netflix Blame widevine, not FreeBSD

Irony is #Netflix uses #FreeBSD as it's back-end but doesn't permit end users to watch it's content in a freebsd computer. End user must have setup linux-drm to watch Netflix in FreeBSD 🙂 @freebsd @netflix howtogeek.com/bsds-worth-try…

@freebsdfrau des@f.o blew my mind with this a few weeks ago in an rc(8) change. I don't think I'm fond of it working just as well to break out of just a single loop, but I understand why -- it just feels a bit error-prone / sensitive to a context change that would change the meaning

Who knew that “break 2” could be used to break out of 2 loops? For example: while : forever1; do while : forever2; do break 2; done; done # breaks immediately from both loops 🤯

FreeBSD 15.0-CURRENT is dead. Long live FreeBSD 15.0-PRERELEASE! (For the next 4 weeks; after that I'll branch stable/15, which will be 15.0-ALPHA1, and main will become 16.0-CURRENT.)

@XNUniverse Can you be a little more specific about your interests outside of security, within the kernel, please?

Where do I connect with FreeBSD kernel and security developers? My interest is in security but I don’t see a whole lot of activity in that mailing list. I’m a terrible kernel developer since I’m new but I’m eager and want mentorship.

@Jaku @NoiceStreaming *glances at # likes over 18h later* Criminally underappreciated

@NoiceStreaming This is unfortunate, you all had something that will eventually be a big part of streaming but the space wasn’t ready for it. It was noice knowing ya.

Important message to our community