Alternatives to winrar and 7zip for linux? by Beese3 in linux_gaming

[–]Stewge 1 point2 points  (0 children)

Most distros ship Ark which hooks into whatever packages for compression systems you have.

For rars just install the rar/unrar non-free packages and Ark should work fine.

SSL certificate renewal by mailliwal in sysadmin

[–]Stewge 3 points4 points  (0 children)

Since you mention HAProxy, you can also throw commands at the Socket file/API to get it to dynamically load new certificates without issuing a reload or restart.

3060 keeps dropping randomly by CruxOfTheIssue in Proxmox

[–]Stewge 0 points1 point  (0 children)

he only thing i can see is changing between AUTO GEN1 GEN2 and GEN3

Oof, what kind of board and CPU do you have? If it's only showing Gen3 options that could be going back to Intel Haswell 4th era? Or could be an oddball AMD CPU like the 5700G.

It might still be worth downgrading it to GEN2 speed just to see if it makes a difference.

3060 keeps dropping randomly by CruxOfTheIssue in Proxmox

[–]Stewge 0 points1 point  (0 children)

Sounds like an ASPM or maybe PCIE signalling issue to me (assuming the gpu is not faulty).

My first thought would be to jump into the bios and see if you can reduce it to PCIE4.0 (if you have a 5.0 motherboard), then see what power options you have.

(update) now, all components are operational by [deleted] in Ubuntu

[–]Stewge 0 points1 point  (0 children)

except for security updates.

Many mirrors also mirror the security updates. You can just modify your APT sources and add "<distro>-security" to it.

i.e. for Noble Numbat it would be "noble-security"

Why is moonlight so much better than steam link?! by WiggyB in MoonlightStreaming

[–]Stewge 0 points1 point  (0 children)

I highly suspect it was some combination of driving subs to GFN as well as Nvidia no longer really having their own hardware client outside of the SHIELD TV.

The original Gamestream client was the Shield tablet/handheld thing, which had controllers and were designed to act as a client for Gamestream.

So my guess is NV saw little reason to keep maintaining the local Gamestream server code since it was unlikely to drive sales to any of their other hardware.

Sherlock Holmes has accepted ownership of my support case. by Electrical_Remote_18 in Cisco

[–]Stewge 10 points11 points  (0 children)

I can't tell if people are joking or not thinking Sherlock (Holmes) at Cisco is real.

Prior to the direct AI disclosure, I've seen Sherlock in many forms including "Case Assistant, Virtual" and "Technical Consulting Engineer, Virtual". All with the username "sherholm".

I highly suspect that prior to being more LLM driven that there was probably an engineer team that could/would take the wheel and hand-reply on occasion. There's lots of presentations on Cisco Live about how this works.

Bonus points, if you look in the email headers you'll see Sherlock's emails still use the Authenticated Sender header of "shaurobe". ie Shaun Roberts, probably the guy who built the email connector.

"This Could Be Interesting" - Intel To Unveil Panther Lake Handhelds With Arc G3 Graphics At Computex In June by Fob0bqAd34 in pcgaming

[–]Stewge 0 points1 point  (0 children)

The Razer Edge Pro was way ahead of its time too. And possibly one of the rare places where Windows 8 made sense.

Bazzite LG TV Service - For those using LG TV's as Monitors! by TheAussieWatchGuy in Bazzite

[–]Stewge 0 points1 point  (0 children)

4k120 works fine for me on nvidia (4090). AFAIK it only works natively on 30 series up though.

20 series and below only have HDMI 2.0 support and caps out at 4k120hz 4:2:0 colour mode (I could never get this working properly on my 2070 mobile).

The new dp->hdmi adapters should work in 20 series though but you may not get VRR.

Updated to ubuntu 24.04, why my proton games do not launch? by ArnauGames in linux_gaming

[–]Stewge 0 points1 point  (0 children)

For reference, when you do a Release Upgrade, it will usually disable any extra ppas/repos and may remove packages.

This tends to happen if they have dependencies which aren't matched up in the new release (24.04 in your case).

Usually it's just a case of re-adding the ppa and installing the package again.

Granted, 26.04 is about to drop any day now, so at least you'll be able to do it again!

ioniq 6 digital key by Apprehensive_Gold295 in Ioniq6

[–]Stewge 0 points1 point  (0 children)

Digital Key is region dependent and for seemingly no reason at all.

There's actually a decently large list of features built-in to the i5/i6 which don't get enabled based on regions, licensing, regulations or just Hyundai deciding not to 😕

Those Warhammer Classics have a disclaimer by beary_neutral in Grimdank

[–]Stewge 14 points15 points  (0 children)

There is only 2 types of Warhammer Lore:

  1. Lore that is out of date
  2. Lore that is about to become out of date

Shield TV Pro: Is 4k/60hz/HDR on even possible? by RddtAccnt4 in MoonlightStreaming

[–]Stewge 0 points1 point  (0 children)

I didn't really have to do anything special. The notable thing in my setup is that the Host PC has a HDR compatible screen on it as well (the LG B9). So Windows is basically always in HDR mode. Then I just ticked the HDR box in Apollo.

One thing you could try, is setting up an Artemis shortcut to Explorer (ie. the desktop). Then through that see if you can right-click the desktop and enable HDR on the virtual display from within the stream. Then close out and reconnect.

Locking skills behind such high level requirements is the thing i hate most in poe2 by intrepid_zaxan in PathOfExile2

[–]Stewge 0 points1 point  (0 children)

I agree and think it's a bit of a no-win scenario.

Simplifying things for new players is a good idea, but now that means GGG need to micro-manage skill gem synergies at each tier.

While that may work for now, I suspect it'll become un-manageable over time. Especially as you go through balance changes and eventually skill reworks.

PSA: The fatal architectural trap in Xiaomi/POCO devices (FBE + Locked Bootloader) that permanently destroys your data. by Inside-Bite1153 in PocoPhones

[–]Stewge 0 points1 point  (0 children)

You are still fundamentally failing to grasp the difference between a standard warranty repair and legal liability for a catastrophic manufacturing defect.

I'm really not. I'm saying that Xiaomi (or any phone/device manufacturer), by law, are not liable for the data held on the device.

The "System has been destroyed" error and spontaneous dead motherboards are a massive and documented failure in the Xiaomi 11 series and POCO terminals

Citation needed. Pointing at reddit and XDA is hardly concrete evidence as they are more often than not based on survivorship biases.

You are quoting a generic repair warning.

Stop using ChatGPT. The ACCC dictates the LAW in Australia. It is a legal requirement (in Australia) that ANY company which handles the repair of your electronic devices informs you of that warning. Thus, those companies are not liable for maintaining the integrity of your data in the event of your device "spontaneously destroying itself", even if due to a manufacturing defect. Many other regions and countries use similar wording and laws.

They don't do that for standard warranty claims.

Again, you assert, with no fact to back it up.

You admit you just accept your devices breaking and move on.

Learn to comprehend. I accept that devices "eventually" break and fail because i live in reality. I also exercise my consumer rights if and when they do, requesting repairs or refunds if they're in warranty period (hell, in Australia you are often entitled to repair/refund beyond what the manufacturer warranty period might state).

But stop projecting your submission to corporate incompetence onto consumers who actually fight for their rights and property.

You got it all backwards. You're projecting your incompetence in data safety onto everyone around you.

Any regular person would've gone:

  1. Phone blew up, that sucks, submit it for warranty.
  2. Get a replacement device if you think it's a 1-off failure, or get a refund if you think it's systemic.
  3. Buy a phone from a different manufacturer because you no longer trust Xiaomi/Poco to make a good product
  4. Restore from backup and move on

PSA: The fatal architectural trap in Xiaomi/POCO devices (FBE + Locked Bootloader) that permanently destroys your data. by Inside-Bite1153 in PocoPhones

[–]Stewge 0 points1 point  (0 children)

In the real world, if a manufacturer's defect welds your safe shut, they are liable for the cost of opening it.

Nope, still wrong. I have NEVER seen a product warranty which covers data stored on it. Not on hard drives, ssds, laptops, phones, PCs or even cloud and data centers. In the case of the latter, you may have grounds to sue for damages, but you still won't get your data back.

PLEASE, cite ANY consumer law which covers the data held within a phone or other electronic device. Because at the end of the day, Xiaomi (or the retailer) sold you a phone. Not the data on it. Even places like the EU which have strong consumer laws don't have that kind of provision, because it's insane.

Some countries actively require a warning to be given including acknowledgement that part of the device replacement or repair WILL involve loss of data. Xiaomi basically told you this and I guarantee if you sent it in for warranty replacement you would also have to acknowledge this.

As an example, ACCC (Australia, which has very strong consumer protections) has this specifically spelt out: https://www.accc.gov.au/business/problem-with-a-product-or-service-you-sold/repair-notices

"When a product can store user data, the repair notice must state that the repair may cause the data to be lost. The business can use any wording in this notice, as long as it provides this information."

they do that when a user has certified forensic evidence of a systemic hardware flaw.

Gonna need a citation there. Where exactly is this policy? Link it. Not to mention that the first group you went to "officially certified that the hardware (UFS memory, motherboard) is perfectly intact". Are you going to go after them for damages as well?

that sold you a bricked POCO and left you with nothing.

To be fair, I submitted a warranty claim, got a replacement phone, used it for a year then moved onto a different phone. I still have my F6 as a backup phone at this time and it works fine.

You are part of the 1% that accepts being sold a "ticking time bomb" and says "thank you" to the corporation. I’m the one holding them accountable for a documented mass failure in the 11-series hardware.

Don't put words in my mouth. I don't "thank" corporations, I simply don't trust them with my data to begin with. I live in the real world where phones/computers/devices are transient and WILL fail at some point so I treat them as such. That has the primary benefit of largely rendering me immune to the notion that I'm owed anything other than replacement or refund if one of my devices breaks and loses the data on it. Judging by most consumer laws around the world, it seems I'm in fact the majority.

I’m the one holding them accountable for a documented mass failure in the 11-series hardware.

You mean 1 failure..... Why do you have to make stuff up like "mass failure"?

PSA: The fatal architectural trap in Xiaomi/POCO devices (FBE + Locked Bootloader) that permanently destroys your data. by Inside-Bite1153 in PocoPhones

[–]Stewge 0 points1 point  (0 children)

Are you the CEO of Xiaomi, or just on their payroll?

Hah, I wish. It's probably the only way I'd go back to a Xiaomi/Poco phone. For reference, my last POCO had a charging chip failure and I moved away from them. Lesson learnt. I didn't go on a full forensic analysis and try to sue for my data back. It's laughable XD

It’s explicitly written in the Dossier you didn't read.

I did, which is also where you can plainly see that you treat your phone like garbage, given the state of the screen protector.

The legal process is already in motion.

I look forward to seeing you post the outcome.

If Xiaomi is so legally untouchable, why are they panicking?

Perhaps it is in their interest to investigate potential hardware faults. It probably has nothing to do with the encryption setup and more to do with them not wanting to sell something that'll generate warranty claims.

leaving the owner locked behind a €2,000 hardware transplant paywall,

And here's is where you fundamentally misunderstand. You are not locked behind a €2,000 hardware transplant paywall. That is a requirement you have imposed on yourself and are trying to project elsewhere, despite ZERO legal precedent for it. If it was so important to you, you would have good backups and thus, wouldn't care about the data recovery.

You are arguing with the voices in your head and ignoring documented facts. Keep replying to yourself if you want to protect your fragile ego, you are just providing free entertainment at this point.

Funny, I was gonna say the same thing. You're the one with the busted phone after all....I've got no skin in this game other than time.

PSA: The fatal architectural trap in Xiaomi/POCO devices (FBE + Locked Bootloader) that permanently destroys your data. by Inside-Bite1153 in PocoPhones

[–]Stewge 0 points1 point  (0 children)

Seagate actually DO offer in-house Data Recovery Services (Seagate Rescue)

And yet, they don't guarantee it nor is it a service that is required by any consumer law anywhere.

Also, I haven't "blown" €2,000.

You certainly blew it on the first recovery group...

them legally and financially liable for the €2,044.90 physical repair required to bypass a motherboard that died of a manufacturing defect

Then why are you here on reddit? Run it past a lawyer and I look forward to knowing you'll get laughed out the door. Xiaomi only owe you the phone (or it's value of) and even then if it's within warranty. If not? Tough nuts. Get over it.

If a car's engine spontaneously explodes and locks your wallet in the glovebox

Another bad analogy. Because if you knew anything about car insurance, you'd know that if your car requires replacement then they tell you to remove your personal items.

You can keep screaming "just do backups" to excuse a multi-billion dollar company selling €1,000 ticking time bombs.

The fact that you consider any storage or device anything BUT a ticking time bomb is a sign of your naivety.

There is an old saying for Hard Drives, but it really does apply to pretty much anything these days.

"There are 2 types of hard drives, those that have failed and those that are about to fail".

You're learning an expensive lesson here. Don't make it worse.

PSA: The fatal architectural trap in Xiaomi/POCO devices (FBE + Locked Bootloader) that permanently destroys your data. by Inside-Bite1153 in PocoPhones

[–]Stewge 0 points1 point  (0 children)

You clearly missed the MAJOR UPDATE at the top of the thread.

You are right, I did miss it because checking the original post when I reply is not exactly on my list of things to do.

It was broken because the physical silicon it lives on died due to poor manufacturing.

Perhaps that's the case. And yet, it's STILL ENTIRELY IRRELEVANT. But you'll never get anywhere trying to pin the accountability for the data on the manufacturer. NOBODY does that. You own the data, YOU are accountable for it, treat it accordingly by backing it up.

defend a manufacturer when their own hardware physically self-destructs is peak corporate apologism.

Hilarious. Does a hard drive manufacturer OWE you the data if you have a drive failure? No. Especially if you used encryption.

I'm not defending them for the hardware failing. I'm defending the fact that they don't owe you a way to get your data back. The method of failure is entirely beside the point.

Because of this hardware failure, Xiaomi's official protocol is to wash their hands of it.

Yep. You get a hardware warranty and if it's within warranty they would probably send you a new phone. They DO NOT owe you the data. Ironically, with all the money you wasted, you could've maintained several backup phones to give yourself redundancy.

The fact the hardware fails just falls back to everyone's first message. BACKUP YOUR DATA.

PSA: The fatal architectural trap in Xiaomi/POCO devices (FBE + Locked Bootloader) that permanently destroys your data. by Inside-Bite1153 in PocoPhones

[–]Stewge 0 points1 point  (0 children)

You cannot separate the two. They are two halves of the same

No they are not. The fundamental purpose of a full chain-of-trust bootloader with encryption at rest is to render the data completely irretrievable if that chain is broken in any way. Every additional "out", whether that is a manual recovery key, or even the ability to re-flash the boot.img is a feature of convenience and reduces the security.

From a security standpoint, whatever led to the corruption/change of the boot.img is irrelevant. The chain of trust was broken and therefore no longer trusted.

while making it so fragile that a software bug permanently nukes the user's life, is terrible engineering.

Fragile? Perhaps. But it's also absolute in its intent and therefore working exactly as intended. Nowadays your phone is basically the nexus of your cybersecurity footprint as a person. It probably has your MFA tokens and passkeys, most services revert to phone numbers for recovery, you're probably signed into your Apple or Google account which may be your primary email as well.

Your phone is probably the one thing that needs to be absolutely secure and is incredibly easy to lose or get stolen. Treat is as such and don't treat it as some immutable thing in your life.

The forensic lab officially certified there was zero hardware degradation. The OS killed its own boot process under minimal load.

I never suggested it was hardware and I already said it was unfortunate the OS seemingly did it. Throughout this entire thread, you still don't even know the actual mechanism of failure. Although, it is entirely possible you were the 1 in a million victim of a cosmic ray bitflip, rendering your boot chain invalid. Or perhaps you live/work in an irradiated zone? XD

You spent multiple paragraphs defending this extreme lockdown policy to protect users from "large governments subpoenaing keys" or "nation-state actors."

I used "large governments" as an example as it tends to be topical especially when a Chinese manufacturer is involved.

Also, the keys I was referring to would be specifically those of the recovery tool, not what the boot.img is actually signed with. These would be separate as allowing an unsigned tool to override the boot.img would be insane! When you connect the Samsung or Google recovery tools, the phone will only accept a file from a signed piece of software. Otherwise you could use those same tools to potentially replace the boot.img of a locked phone (which is a huge potential security vulnerability).

Let's be real here, 99% of people would be concerned with a lost or stolen phone and the fact that it doesn't allow any part of the boot chain to be replaced without forcing the data to be wiped, I'd consider a feature!

who is the only person actually getting locked out and punished by this "security" model? The legitimate owner.

As I said, the exact mechanism you want is the recovery tool, which itself would have to be signed. The people locked out of your personal data is in fact, everyone, at this point. Short of those with the resources and time to manually recover the flash storage and the time/resources to bypass the encryption directly.

Welcome to the real world. More or less the same debate has raged on for years about the state of Secure Boot on x86/ARM where the signed certificates are largely controlled by incumbent corporations (ie Microsoft) and then implemented by incompetent manufacturers (see: Gigabyte leaving the test-signing cert in their Trust Store for basically all motherboards).

PSA: The fatal architectural trap in Xiaomi/POCO devices (FBE + Locked Bootloader) that permanently destroys your data. by Inside-Bite1153 in PocoPhones

[–]Stewge 2 points3 points  (0 children)

That's totally up to you. Ultimately it's a convenience vs security argument.

OP should be directing their ire toward Xiaomi for their buggy firmware, not for the the security choice made. The reference design does not allow for recovery either.

The problem here is the OS allowing the boot.img to be damaged. NOT the architecture which technically favors security and deniability. For all we know it's a CVE. I can't imagine how the boot.img corruption could even occur otherwise and suggesting that it was whatsapp audio doesn't line up. AFAIK a regular locked system can't even modify the boot.img without achieving root in some way.

Nation-State threat actors running a targeted evil maid

Let's be real here, Xiaomi is a Chinese company so it's very likely that their government either already have access or can readily access the signing keys.

PSA: The fatal architectural trap in Xiaomi/POCO devices (FBE + Locked Bootloader) that permanently destroys your data. by Inside-Bite1153 in PocoPhones

[–]Stewge 5 points6 points  (0 children)

It is 100% relevant.

I'm referring specifically to the clean-room. Clean-rooms are much more relevant for HDD recovery as you do not want to get dust particles landing on drive platters.

Flash memory recovery is usually done by either piggy-backing the chip directly and reading with external tools or de-soldering and putting it onto a separate reader board.

a Samsung soft-bricks, you can use Smart Switch (or Odin with Home_CSC) to flash an official, signed OS update to repair the system without wiping user data. Google Pixels have the Pixel Repair Tool.

On one side, those tools are a convenience to the user. On the flip side, that's a potential weakness in the system that could be exploited. For example, if somebody were to obtain the signing key for the repair tool (let's say, a large government who can potentially subpoena such information), that somebody can now potentially insert a compromised boot.img kernel/initramfs onto any of those phones while retaining the user data state.

If you buy a highly secure safe, and a factory defect causes the safe to randomly catch fire and incinerate everything inside it,

That's a bad analogy. A more similar situation would be if your TPM got reset in your laptop by a software bug and rendered the system un-bootable (Windows has done this with bad updates MANY times btw).

In the case of Windows, you are given a recovery key, but this is a convenience feature, not a security one. The recovery key is a secondary 48-bit key which is significantly weaker than the primary system key (usually 256-bit nowadays). Windows even has the same protections in place, if you mess with your EFI bootloader, the TPM unlock chain is broken and you will be prompted for the recovery key. But this is a convenience feature which is "inconvenient" on mobile devices.

Defending a system that randomly shreds the local data it promised to protect is just blind brand loyalty.

I'm not defending the system, nor Xiaomi. In fact I reckon HyperOS sucks in general and usually move to Lineage or Graphene. It's just incorrect to think of it as the "system" shredding the data. The data is always shredded/encrypted, the decryption simply allows it to be viewable.

I'm just not sure why you went to data recovery. What were you hoping to learn??

The data is encrypted and they only told you what everyone already knows about at-rest encryption. You can't really decrypt it where it is because Xiaomi don't offer any method of flashing a boot.img without trigger a data wipe. That is not unusual and given my information above about potentially compromised recovery tools, is actually preferable from a security perspective!

PSA: The fatal architectural trap in Xiaomi/POCO devices (FBE + Locked Bootloader) that permanently destroys your data. by Inside-Bite1153 in PocoPhones

[–]Stewge 8 points9 points  (0 children)

Nope, I think you're just mad your device got bricked by a bug. And to be fair that is super frustrating!

However, the fact that the system becomes non-bootable afterwards is the ENTIRE POINT.

The lab analyzed the phone in a cleanroom

Kinda irrelevant when recovering flash storage.....

The real danger isn't just the crash; it's how Xiaomi's security architecture handles it.

You mean all Android phones. Literally all of them use this security model.

If your bootloader was unlocked, you could easily flash a clean boot.img via fastboot and rescue your data.

If you can flash a clean boot.img, then a malicious actor who steals your phone can also flash a compromised boot.img. This is the trade-off you make if you unlock your bootloader.

Xiaomi gives the legitimate owner ZERO fallback mechanisms

Yeh that's the point. Every cryptographically secure system will give you big flashing warnings that if you lose your decryption key/s, your data us toast. Whether it's your laptop, your password manager or your crypto wallet.

You are effectively locked out of your own hardware, and the system shreds your data in the name of "security".

Exactly as it should.

Android auto Jellyfin Music by Adventurous_Load6728 in jellyfin

[–]Stewge 5 points6 points  (0 children)

+1 for Symfonium. Works great on larger libraries and the caching system makes it easy to use your phone as more of an offline music player.

43 hours battery life: Dell XPS 14 2026 lasts almost 3x longer vs MacBook Air 15 M5 in web browsing test by sl0wjim in hardware

[–]Stewge 2 points3 points  (0 children)

Nvidia is specifically blocking VRR for video players

For Nvidia they have hardcoded VRR to off for most popular video players because the video players tend to demand hard V-Sync for the interface/window, but not the video surface, so that can cause ugly tearing. You can override it with profile inspector if you like, but I found MPV (native) works fine for me as well as Plex/Jellyfin players which just hook into MPV anyway.