Become a fan of Slashdot on Facebook

 



Forgot your password?
typodupeerror

Comment Tis all a lie (Score 0) 56

Just checked USAJOBS.gov . There is not a single CISA based job listed. If they are understaffed as bad as this indicates why are there no job postings at their official site for hiring? None, Zero, Zip. Seems to be this article is fake news based on a stolen, uncheckable, email.
 

Comment Yawn (Score -1, Troll) 56

Not really news. There has been no Cyber talent in the government for a while because it won't PAY them. When you can make 2X more going contractor, or private industry, the only people in the government are people who need the ability not to get fired to have a small chance of holding a job. There is no innovation or dedication in or civil servants. Until the government is willing to meet the wages on the outside they will be unable to attract top talent.

If you think Government workers are a meritocracy and we are losing top talent, you obviously have never looked into Federal hiring practices. They self select for the worst candidate.

If you are a Govie reading this, yes I mean you.

So this move probably improved efficiency, not hurt it.

Comment Profile of the dissenting commissioner (Score 2) 131

This seems like such an obvious improvement that I was curious about the one commissioner who voted against it. It turns out he, Andrew Ferguson, is expected to be nominated and confirmed to be the head of the FTC under the upcoming administration. Some info about the anticipated new head of the FTC:

* UVA undergrad and law degrees
* worked for private firms defending against anti-trust enforcement
* clerked for Clarence Thomas
* worked for Republican senators on judicial confirmations
* solicitor general for Virginia
* appointed to FTC in 2023

We will see how things change under his leadership.

Submission + - Samba gets funding from the German Sovereign Tech Fund.

Jeremy Allison - Sam writes: The Samba project has secured significant funding (€688,800.00) from the German
Sovereign Tech Fund (STF) to advance the project. The investment was
successfully applied for by SerNet. Over the next 18 months, Samba developers
from SerNet will tackle 17 key development subprojects aimed at enhancing
Samba’s security, scalability, and functionality.

The Sovereign Tech Fund is a German federal government funding program that
supports the development, improvement, and maintenance of open digital
infrastructure. Their goal is to sustainably strengthen the open source
ecosystem.

The project's focus is on areas like SMB3 Transparent Failover, SMB3 UNIX
extensions, SMB-Direct, Performance and modern security protocols such as SMB
over QUIC. These improvements are designed to ensure that Samba remains a
robust and secure solution for organizations that rely on a sovereign IT
infrastructure. Development work began as early as September the 1st and is
expected to be completed by the end of February 2026 for all sub-projects.

All development will be done in the open following the existing Samba
development process. First gitlab CI pipelines have already been running [4]
and gitlab MRs will appear soon!

https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Fsamba.plus%2Fblog%2Fdetail...

https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Fwww.sovereigntechfund....

Comment Re:Maybe (Score 1) 104

The upstream Linux kernel doesn't differentiate between security bugs and "normal" bug fixes. So the new kernel.org CNA just assigns CVE's to all fixes. They don't score them.

Look at the numbers from the whitepaper:

"In March 2024 there were 270 new CVEs created for the stable Linux kernel. So far in April 2024 there are 342 new CVEs:"

Comment Re:Yeah (Score 1) 104

Yes ! That's exactly the point. Trying to curate and select patches for a "frozen" kernel fails due to the firehose of fixes going in upstream.

And in the kernel many of these could be security bugs. No one is doing evaluation on that, there are simply too many fixes in such a complex code base to check.

Comment Re:Maybe (Score 1) 104

You're missing something.

New bugs are discovered upstream, but the vendor kernel maintainers either aren't tracking, or are being discouraged from putting these back into the "frozen" kernel.

We even discovered one case where a RHEL maintainer fixed a bug upstream, but then neglected to apply it to the vulnerable vendor kernel. So it isn't like they didn't know about the bug. Maybe they just didn't check the vendor kernel was vulnerable.

I'm guessing management policy discouraged such things. It's easier to just ignore such bugs if customer haven't noticed.

Slashdot Top Deals

The system was down for backups from 5am to 10am last Saturday.

Working...