Forgot your password?
typodupeerror

Comment Re:For crying out loud, stop using that term. (Score 1) 35

I don't care where the term originated, but calling it "jailbreaking" just makes it sound like you're doing something illicit. No one would think twice about it if you said you were going to "enable expanded functionality mode" on their Kindle, since it's out of support now. Implying you're going to get in trouble for freely using hardware you paid for outright for is such a corpo psyop.

When you're wrongfully imprisoned, jailbreak may be your only recourse.

Comment Re:Just what we need (Score 2) 98

So we're taking a superior, simpler power source and drive chain and adding a fake clutch to make it simulate an older, inferior power source and drive chain. Brilliant. In 25 years people will look at these and wonder "what the hell were they thinking?"

Frankly I'm thinking... whatever it takes to sell bikers on replacing their painfully noisy kill-me machines with silent kill-me machines is worth it.

As for the "it's loud so car drivers know I'm there", sorry but the only times I've ever not known a bike was near me is when they were doing something illegal, unsafe, and unpredictable. People who refuse to wear high-vis reflective clothing don't get to pick how loud their vehicles are.

Comment Re:MFA (Score 1) 106

If the desktop/laptop/phone isn't registered in the client's MDM

We gotta have your cell phone number. Because security, you know.

As it happens, MDM doesn't (necessarily) need that. AFAIK you can use a tablet or a phone with Wifi only. And I mentioned MDM-managed desktops and laptops.

While yes, situations like your anecdote exist, MDM isn't some excuse for capturing employee data.

Comment Re:MFA (Score 4, Interesting) 106

With MFA, it should not be a catastrophe if someone obtains your password. That's the point of it.

MFA is - to a certain degree - compromised.

There are real-world exploits for - for instance M365 - that work like this:

A user gets a malicious, disposable link via e-mail.
The user clicks the link.
The link takes them to a carefully crafted web site, and asks for their username & password.
The user has been partially phished.
The web site initiates an logon call back to M365 in the background and harvests the two-digit code that the end-user needs.
The web site displays the two-digit code.
The user's authenticator app is asking the user for the code... for the bad guy's login session.
The user enters the two-digit code they're seeing.
The bad guys are now in, add their own MFA device and exploit everything they can.

The same thing can happen with TOTP. Anything that an end-user can do can be repeated in near real-time. The phishing site asking for your OTP just re-uses it and feeds it into the real place.

We've been shifting our clients to a "compliant device" position. If the desktop/laptop/phone isn't registered in the client's MDM, it isn't allowed to log on. Yes it's got some overhead to it and yes, getting client buy-in is a struggle. But the days of allowing logons from anywhere, any device are dwindling.

Here's a video about how this works: https://www.youtube.com/watch?...

Submission + - AI finds signs of pancreatic cancer before tumors develop (nbcnews.com)

fjo3 writes: An AI model developed at the Mayo Clinic in Rochester, Minnesota, detected abnormalities on patients’ CT scans up to three years before they were diagnosed with pancreatic cancer, according to research published this week in the journal Gut.

The scientists behind the model, which is now being evaluated in a clinical trial, trained it by feeding it CT scans from patients who had been screened for other medical conditions then were later diagnosed with pancreatic cancer. The team then had radiologists review the scans and compared their ability to find early signs of cancer to that of the AI model. The model was found to be three times better at identifying the early signs.

Submission + - Copy Fail exploit lets 732 bytes hijack Linux systems and quietly grab root (nerds.xyz)

BrianFagioli writes: A newly disclosed Linux kernel vulnerability called Copy Fail (CVE-2026-31431) allows an unprivileged user to gain root access using a tiny 732-byte script, and it works with unsettling consistency across major distributions. Unlike older exploits that relied on race conditions or fragile timing, this one is a straight-line logic flaw in the kernelâ(TM)s crypto subsystem. It abuses AF_ALG sockets and splice to overwrite a few bytes in the page cache of a target file, such as /usr/bin/su. Because the kernel executes from the page cache, not directly from disk, the attacker can inject code into a setuid binary in memory and immediately escalate privileges.

What makes this especially concerning is how quiet it is. The file on disk remains unchanged, so standard integrity checks see nothing wrong, while the in-memory version has already been tampered with. The same primitive can also cross container boundaries since the page cache is shared, raising the stakes for multi-tenant environments and Kubernetes nodes. The underlying issue traces back to an in-place optimization added years ago, now being rolled back as part of the fix. Until patched kernels are widely deployed, this is one of those bugs that feels less like a theoretical risk and more like a practical, reliable path to full system compromise.

Submission + - Longevity Escape Velocity Achieved Within Three Years (popularmechanics.com)

frdmfghtr writes: Popular Mechanics has a story about the rate at which lifespans are being extended by medical technology will surpass actual aging.

From the article:
"There's a controversial idea floating around the futurist community of "longevity escape velocity." It sounds super sci-fi, but it's basi-
cally the idea that as our life extension technology gets better, our life expectancy could increase by more than we age over a set period of time. For example, as medical innovations continue to move forward, we would still age a year over the span of a year. But our life expectancy would go up by, say, a year and two months, meaning we would functionally get two months of life back."

Comment Re:and an exploit will be published in 3, 2, 1 ... (Score 1) 89

As a friend of mine in an uncharacteristic fit of insight once said, as long as there is a decision point that can be discovered, yes and the code goes this way, no and the code goes that way, it is in principle possible to write a patch to circumvent any DRM.

Not to disparage your friend but... that a thing is possible in principle does not necessitate it being possible in practicality.

Worse, it is unhelpful to adopt a position of "yet another restriction will inevitably" be circumvented. Side-loading is more difficult on Android than it has ever been. Jailbreaking on iOS is more difficult on Apple than it has ever been. Piracy is more difficult than it has ever been (since the inception of the Internet). Every time a convenient torrent indexer is shut down, sure, three more may pop up but they tend to be less convenient, have less content, and have more malware and fakes. When a manufacturer does something unpleasant, it is not useful to say "it's going to be okay... it is always going to be okay." It's not.

Comment Re:They're grasping. (Score 4, Interesting) 110

There isn't a shortage of water in Michigan.

They're grasping.

Good.

These datacenters are driving up electricity and water prices by increasing demand, regardless of there is currently sufficient supply to meet that demand. A community may have enough generation capacity and treatment capacity today, but when tomorrow's development of X new homes happens, the capacity either comes from today's excess or from having to add more capacity... which costs.

Datacenters don't contribute to communities financially the way home or even factories do. There are virtually no jobs, and definitely no secondary jobs. They negotiate bulk purchasing discounts and tax breaks.

The quantity of datacenters is just going to go up, dramatically over time. We need to figure out how to make their owners pay for what they really consume where they're built before there's an order of magnitude more of them.

Submission + - US government ramps up mass surveillance (theconversation.com) 2

sinij writes:

People have little choice when buying devices, using apps or opening accounts but to agree to lengthy terms that include consent for companies to collect and sell their personal data. This “consent” allows their data to end up in the largely unregulated commercial data market. The government claims it can lawfully purchase this data from data brokers. But in buying your data in bulk on the commercial market, the government is circumventing the Constitution, Supreme Court decisions and federal laws designed to protect your privacy from unwarranted government overreach.

Still nothing to hide?

Submission + - Tesla Admits Pre-2023 Hardware Will Never Achieve Full Autonomy 2

DeanonymizedCoward writes: According to Gizmodo, Tesla CEO Elon Musk has admitted on an earnings call that Tesla's "Hardware 3," used in most pre-2023 models, does not have the capability to support fully autonomous driving. “Unfortunately, Hardware 3, I wish it were otherwise, but Hardware 3 simply does not have the capability to achieve unsupervised FSD,” Musk said during the call. “We did think at one point it would, but relative to Hardware 4 it has only 1/8 the memory bandwidth of Hardware 4.”

All hope is not (yet) lost for owners of older Tesla vehicles, though: Musk proposes a "discounted trade-in" program, as well as the deployment of "mini-factories" to streamline the installation of new computers and cameras into older vehicles. It remains to be seen whether this will materialize.

Slashdot Top Deals

"Being against torture ought to be sort of a multipartisan thing." -- Karl Lehenbauer, as amended by Jeff Daiell, a Libertarian

Working...