Remix.run Logo
▲ sippingabonedry 4 hours ago

I see the OpenBSD guys are all over the PR (deservedly) shitting all over the proposed fixes so I assume LibreSSL may be impacted? Or are they just providing free advice and color commentary?

▲collinfunk 4 hours ago | parent | next [-]

I'm not really involved in OpenSSL, aside from a few tiny changes and commenting on a few things that affected GNU coreutils. However, I have seen Bob, whom I assume you are referring to based on the profile picture, participate in many discussions. I wouldn't infer too much from it.

▲bentley 2 hours ago | parent | next [-]

Bob is a member of the Engineering & Standards team at the OpenSSL Corporation.

https://openssl-corporation.org/leadership.html

▲ 23 minutes ago | parent [-]
[deleted]
▲sippingabonedry 4 hours ago | parent | prev [-]

Do the projects collaborate closely since the split? My history is admittedly fuzzy.

Sometimes the fix can be worse than the bug. Like patching a hole in the wall.

▲wahern 2 hours ago | parent [-]

Yes, they collaborate. BoringSSL and libressl especially, which IIRC share some of the same developers. But OpenSSL has it's own priorities and vision, which sometimes (often?) clashes with the sensibilities of the BoringSSL and libressl developers. Because OpenSSL is still the de facto standard bearer and developer target, it can get frustrating for the libressl and BoringSSL developers, especially when they zig and OpenSSL decides to zag.

▲aaronbwebber an hour ago | parent | prev | next [-]

Describing the comments on this PR as "shitting all over the proposed fixes" seems wildly out of proportion? This is direct, productive feedback on a PR that led to a consensus and approval on an appropriate fix in ~a week, we don't need to make the OS process sound worse than it is.

▲bvttf 4 hours ago | parent | prev [-]

I think the second, LibreSSL was forked before OpenSSL v3 and this only impacts OpenSSLv4.