And as soon as it's merged, an issue would be opened: it is critical that you immediately push a release and tag it as an emergency security fix so that everyone upgrades ASAP.
746 karma · joined September 5, 2017
And as soon as it's merged, an issue would be opened: it is critical that you immediately push a release and tag it as an emergency security fix so that everyone upgrades ASAP.
First is who is going to pay? OSS is popular because it can be adopted without any payment, removing a key piece of friction. And companies are in the business of maximizing their profits, which is often done by minimizing their expenses. Perhaps this can be implemented by the government as a tax, but then borders enter the equation, both for where businesses incorporate, and where OSS developers live, making it a nontrivial matching challenge.
But the bigger issue with payments I see is trying to allocate money to the right OSS maintainers. Once money is distributed, scams will appear pretending to be a worthy OSS project, LLMs would be churning non-stop flooding the ecosystem with knockoff projects, people will dispute contributions to take credit for the work of others, and a flood of attempts to collect payments will arrive from overseas locations where the cost of living is low and any payment can be a windfall.
My own fear is the result of the latter problem would be a disaster for OSS maintainers. The workload to collect payments, proving the contributions are worthy and not a scam, would dramatically increase the burden on OSS maintainers, in a way that could destroy the ecosystem.
> The author of the recent 'Carrot disclosure' blog post has contacted the Forgejo Security team with their findings. The issues raised concern defence-in-depth improvements and denial-of-service risks. There is no known RCE exploit possible without internal server credentials.
> We believe these findings can be addressed publicly. The security team will open issues where approaches to implement new defensive measurements will be discussed, we believe there's no single answer and as such appreciate the opinion of other Forgejo contributors on this matter.
We can build capacity to manufacturer renewable power domestically. But I suspect this administration is more interested in protecting the business interest of those that gave them the largest campaign donations than they are in long term energy sustainability.
That's a really big "if". Particularly since so many companies don't even know all of the OSS they are using, and they often use OSS to offload the cost of maintaining it themselves.
My hope is when the dust settles, we see more OSS SAST tools that are much better at detecting vulnerabilities. And even better if they can recommend fixes. OSS developers don't care about a 20 point chained attack across a company network, they just want to secure their one app. And if that app is hardened, perhaps that's the one link of the chain the attackers can't get past.
Without that, we are quickly spiraling into the dystopia where privacy is gone, and when the wrong person gets access to the data, entire populations are threatened.
Value isn't just slapping a license on something and pushing to GitHub. It's maintaining and curating that software over years, focusing the development towards a goal. It's as much telling users what features you're not willing to add and maintain as it is extending the project to interoperate with others.
And that long term commitment to maintenance hasn't come out of the vibe coded ecosystem. Commitment is exactly what they don't want, rather they want the fast sugar high before they drop it and move on to the next thing.
The biggest threat to open source is the strip mining of the entire ecosystem, destroying communities and practices that have made it thrive for decades. In the past, open source didn't win because it always had the best implementation, but because it was good enough to solve problems for enough people that it became self sustaining from the contribution of value.
I feel that will continue, but it's also going to take a set back from those that aren't interested in contributing value back into the ecosystem from which they have extracted so much.
This is made even worse by the golang.org/x packages updating their minimum Go version without any other changes to the code that require that bump. It ripples through all projects that have any dependencies on those packages, and it forces everyone to choose between security updates and backward compatibility.
I've ranted about this before in my blog [1].
Or they redirected funding that previously went to education to other budget items. If a trust fund is created to send $7B to education, but the government cuts their previous $10B in funding, the trust fund can be perfectly followed, while educators see a $3B cut in their funding.
It makes those breakages less painful. A project can eventually remove a deprecated API after notifying other projects to run `go fix`. And when projects ignore that advice (some always will), they can revert to a previous working version, run `go fix`, and then upgrade, without spending time in the code identifying how to replace each removed API.
And for those projects that routinely update and run `go fix`, they'll never notice the removal of deprecated code. Given the other benefits of `go fix`, switching to easier to read methods, and leveraging more efficient methods, in addition to security fixes that come with regular updates, this should be the workflow for most maintained projects.
But this administration wants to say everything is fine, and fires those that say otherwise. So now unemployment seems under control even though it's not great.
Now the Fed, with their dual mandate to maintain a healthy labor market and control inflation, is considering raising rates. If it turns out the job market was much worse than we realized, raising rates could tank the economy more than it already is tanking. All because they wanted to pretend everything is fine.
It's not just the timestamps you need to worry about. Tar needs to be consistent with the uid vs username, gzip compression depends on implementations and settings, and the json encoding can vary by implementation.
And all this assumes the commands being run are reproducible themselves. One issue I encountered there was how alpine tracks their package install state from apk, which is a tar file that includes timestamps. There are also timestamps in logs. Not to mention installing packages needs to pin those package versions.
All of this is hard, and the Dockerfile didn't make it easy, but it is possible. With the right tools installed, reproducing my own images has a documented process [2].
There's also a stagnation of salaries relative to inflation and a slow hiring market that has people locked into a job when they'd like to find something better. The K-shaped recoveries have people slipping out of the middle class. Combine with housing increasing faster than inflation, future generations having a lower quality of life than their parents.
The wealthy are doing what they can to try to direct the narrative elsewhere, by controlling media sources, blaming immigrants, blaming China, and blaming the government. But we really have far too much wealth concentration to be sustainable, not unlike the ending of a game of monopoly. If a more stable solution isn't found soon, I fear things will get much worse than they already are.
Reaction 2: it's open source, make the lawmakers do submit the changes.
Reaction 3: how would this ever be enforced? Would they outlaw downloading distributions, or even older versions of distributions? When there's no exchange of money, a law like this is seems like it would be suppression of free speech.
Reaction 4: Someone needs to maliciously comply, in advance, on all California government systems. Shutdown the phones, the Wi-Fi, the building access systems, their Web servers, data centers, alarm systems, payroll, stop lights, everything running any operating system. Get everyone to do it on the same day as an OS boycott. And don't turn things back on until the law is repealed.
But the real hidden power of buildkit is the ability to swap out the Dockerfile parser. If you want to see that in action, look at this Dockerfile (yes, that's yaml) used for one of their hardened images: https://github.com/docker-hardened-images/catalog/blob/main/...
My personal time frame is 4-5 years of emergency funds. You can adjust that for your own risk tolerance, but have a look at various past crashes to make an educated decision.
I'd only leave it invested if you don't actually need it, because college can be delayed or financed with student loans.
1. In a parking lot, clear behind the car, and just enough to get inside. Then back the car out of the space, clear the car off, clear the parking space out, put the car back in the parking space and clear everything you knocked off. If tried without pulling the car out of the space, you'd be trying not to ding up your neighbor's car, clearing in tight spaces under the car, and then doing it all again when you clear off the top of the car into that narrow gap.
2. Don't drive unless you absolutely need to. You may know what you're doing, but others almost certainly don't. But do make sure to clear out at least one car, just in case there's an emergency.
> you don't like the president
One of these things is not like the other. In the second case, it's expressing disagreement with a political figure that has directed multiple mass murders of vulnerable people.
But in the first, it's promoting the mass murder of vulnerable people. Free speech isn't freedom to promote hate crimes.
But using this to vouch for others as a way to indicate trust is going to be dangerous. Accounts can be compromised, people make mistakes, and different people have different levels of trust.
I'd like to see more attention placed in verifying released content. That verification should be a combination of code scans for vulnerabilities, detection of a change in capabilities, are reproducible builds of the generated artifacts. That would not only detect bad contributions, but also bad maintainers.
The second thing they can do is ensure the police force is on their side. Remove officers that would collaborate with attempts to overthrow an election. Require training, monitor social media, ensure qualified immunity cannot protect them, and make sure they are aware.