▲ 886 ▼ Microsoft admits Windows 11 has a GDID tracker with no off switch, first documented publicly in an FBI hacker complaint (www.windowslatest.com) submitted 4 months ago by inclementimmigrant@lemmy.world to c/technology@lemmy.world 201 comments fedilink hide all child comments
[–] DevDave@piefed.social 19 points 4 months ago (10 children) also there's the TPM chip. permalink fedilink source parent hideshow 10 child comments replies: [–] Septimaeus@infosec.pub 18 points 4 months ago* (last edited 4 months ago) (8 children) Upvoting both comments for awareness, since Linux is the first of a multi-step process, not a privacy panacea. But we must be clear that in both theory and practice there’s little comparison between systemd and modern Windows machine-user association. Someone using Windows regularly has a gaping wound, is actively bleeding out. Switching to Linux is just a tourniquet, but every other treatment is at best no-effect until that tourniquet is applied. E: transpose systemd/Windows for clarity permalink fedilink source parent hideshow 8 child comments replies: [–] DevDave@piefed.social 5 points 4 months ago (7 children) Also as a life long programmer, I have this feeling it is possible to just go in and make some changes so I can have the system just make shit up about the TPM while indeed also doing the equivalent of having system-d decide to respond with random bullshit. Don't even need to be a programmer, just find a community of them that you trust that distribute their own "fixes". Definitely not doing that with anything else because its both hidden in compilation and buried like herpes across multiple components. Probably/hopefully not directly related but I really want to know what they changed to break the clipboard service. permalink fedilink source parent hideshow 7 child comments replies: [–] Septimaeus@infosec.pub 3 points 4 months ago (6 children) And you’d be technically correct, the best kind of correct. To the inquisitor:any distro that’s fully OSS can be fully compiled from scratch with any modifications you choose). Though yes, if you’re still using Windows, the learning curve may look like a wall. I really want to know what they changed to break the clipboard service Guessing the X11 [X]Wayland migration KDE Plasma bug report? Should be fixed in 6.5.2. permalink fedilink source parent hideshow 6 child comments replies: [–] DevDave@piefed.social 3 points 4 months ago (1 child) Adjacent comment. I've found working in a true posix environment is drastically better than the oddities I dealt with Win32. One annoyance is Microsoft has never been able to implement fork(). Though i never messed with x11 as I was never motivated to see what it was like under the figurative hood. permalink fedilink source parent hideshow 1 child comment replies: [–] Septimaeus@infosec.pub 2 points 4 months ago It really is a hell of a lot more sane, instantly missed once you don’t have it. And yeah Fork’s a blessing when used with care lol permalink fedilink source parent [–] DevDave@piefed.social 3 points 4 months ago (3 children) Sorry, switched contexts there. Microsoft broke their clipboard service recently which makes me think they added "telemetry" collecting logic somewhere in there. permalink fedilink source parent hideshow 3 child comments replies: [–] Septimaeus@infosec.pub 1 point 4 months ago (2 children) Oh right, I misread. And yeah not sure (my win32 repro targets have all been locked for a while) but with all the facepalm regressions I’ve read about lately it really could be anything. permalink fedilink source parent hideshow 2 child comments replies: [–] DevDave@piefed.social 3 points 4 months ago (1 child) From my experience, the number one culprit of legacy code breaking is someone asking if anyone knows how it works. Second most common culprit is someone making a "quick patch" to legacy code. permalink fedilink source parent hideshow 1 child comment replies: [–] Septimaeus@infosec.pub 1 point 4 months ago lol damn, flinched at both even though I was prepared permalink fedilink source parent [–] mic_check_one_two@lemmy.dbzer0.com 3 points 4 months ago Yeah, motherboard-level tracking is scary because even the OS won’t be able to detect it. The truly paranoid people (and security researchers) go as far as desoldering chips to ensure nothing phones home. permalink fedilink source parent
[–] Septimaeus@infosec.pub 18 points 4 months ago* (last edited 4 months ago) (8 children) Upvoting both comments for awareness, since Linux is the first of a multi-step process, not a privacy panacea. But we must be clear that in both theory and practice there’s little comparison between systemd and modern Windows machine-user association. Someone using Windows regularly has a gaping wound, is actively bleeding out. Switching to Linux is just a tourniquet, but every other treatment is at best no-effect until that tourniquet is applied. E: transpose systemd/Windows for clarity permalink fedilink source parent hideshow 8 child comments replies: [–] DevDave@piefed.social 5 points 4 months ago (7 children) Also as a life long programmer, I have this feeling it is possible to just go in and make some changes so I can have the system just make shit up about the TPM while indeed also doing the equivalent of having system-d decide to respond with random bullshit. Don't even need to be a programmer, just find a community of them that you trust that distribute their own "fixes". Definitely not doing that with anything else because its both hidden in compilation and buried like herpes across multiple components. Probably/hopefully not directly related but I really want to know what they changed to break the clipboard service. permalink fedilink source parent hideshow 7 child comments replies: [–] Septimaeus@infosec.pub 3 points 4 months ago (6 children) And you’d be technically correct, the best kind of correct. To the inquisitor:any distro that’s fully OSS can be fully compiled from scratch with any modifications you choose). Though yes, if you’re still using Windows, the learning curve may look like a wall. I really want to know what they changed to break the clipboard service Guessing the X11 [X]Wayland migration KDE Plasma bug report? Should be fixed in 6.5.2. permalink fedilink source parent hideshow 6 child comments replies: [–] DevDave@piefed.social 3 points 4 months ago (1 child) Adjacent comment. I've found working in a true posix environment is drastically better than the oddities I dealt with Win32. One annoyance is Microsoft has never been able to implement fork(). Though i never messed with x11 as I was never motivated to see what it was like under the figurative hood. permalink fedilink source parent hideshow 1 child comment replies: [–] Septimaeus@infosec.pub 2 points 4 months ago It really is a hell of a lot more sane, instantly missed once you don’t have it. And yeah Fork’s a blessing when used with care lol permalink fedilink source parent [–] DevDave@piefed.social 3 points 4 months ago (3 children) Sorry, switched contexts there. Microsoft broke their clipboard service recently which makes me think they added "telemetry" collecting logic somewhere in there. permalink fedilink source parent hideshow 3 child comments replies: [–] Septimaeus@infosec.pub 1 point 4 months ago (2 children) Oh right, I misread. And yeah not sure (my win32 repro targets have all been locked for a while) but with all the facepalm regressions I’ve read about lately it really could be anything. permalink fedilink source parent hideshow 2 child comments replies: [–] DevDave@piefed.social 3 points 4 months ago (1 child) From my experience, the number one culprit of legacy code breaking is someone asking if anyone knows how it works. Second most common culprit is someone making a "quick patch" to legacy code. permalink fedilink source parent hideshow 1 child comment replies: [–] Septimaeus@infosec.pub 1 point 4 months ago lol damn, flinched at both even though I was prepared permalink fedilink source parent
[–] DevDave@piefed.social 5 points 4 months ago (7 children) Also as a life long programmer, I have this feeling it is possible to just go in and make some changes so I can have the system just make shit up about the TPM while indeed also doing the equivalent of having system-d decide to respond with random bullshit. Don't even need to be a programmer, just find a community of them that you trust that distribute their own "fixes". Definitely not doing that with anything else because its both hidden in compilation and buried like herpes across multiple components. Probably/hopefully not directly related but I really want to know what they changed to break the clipboard service. permalink fedilink source parent hideshow 7 child comments replies: [–] Septimaeus@infosec.pub 3 points 4 months ago (6 children) And you’d be technically correct, the best kind of correct. To the inquisitor:any distro that’s fully OSS can be fully compiled from scratch with any modifications you choose). Though yes, if you’re still using Windows, the learning curve may look like a wall. I really want to know what they changed to break the clipboard service Guessing the X11 [X]Wayland migration KDE Plasma bug report? Should be fixed in 6.5.2. permalink fedilink source parent hideshow 6 child comments replies: [–] DevDave@piefed.social 3 points 4 months ago (1 child) Adjacent comment. I've found working in a true posix environment is drastically better than the oddities I dealt with Win32. One annoyance is Microsoft has never been able to implement fork(). Though i never messed with x11 as I was never motivated to see what it was like under the figurative hood. permalink fedilink source parent hideshow 1 child comment replies: [–] Septimaeus@infosec.pub 2 points 4 months ago It really is a hell of a lot more sane, instantly missed once you don’t have it. And yeah Fork’s a blessing when used with care lol permalink fedilink source parent [–] DevDave@piefed.social 3 points 4 months ago (3 children) Sorry, switched contexts there. Microsoft broke their clipboard service recently which makes me think they added "telemetry" collecting logic somewhere in there. permalink fedilink source parent hideshow 3 child comments replies: [–] Septimaeus@infosec.pub 1 point 4 months ago (2 children) Oh right, I misread. And yeah not sure (my win32 repro targets have all been locked for a while) but with all the facepalm regressions I’ve read about lately it really could be anything. permalink fedilink source parent hideshow 2 child comments replies: [–] DevDave@piefed.social 3 points 4 months ago (1 child) From my experience, the number one culprit of legacy code breaking is someone asking if anyone knows how it works. Second most common culprit is someone making a "quick patch" to legacy code. permalink fedilink source parent hideshow 1 child comment replies: [–] Septimaeus@infosec.pub 1 point 4 months ago lol damn, flinched at both even though I was prepared permalink fedilink source parent
[–] Septimaeus@infosec.pub 3 points 4 months ago (6 children) And you’d be technically correct, the best kind of correct. To the inquisitor:any distro that’s fully OSS can be fully compiled from scratch with any modifications you choose). Though yes, if you’re still using Windows, the learning curve may look like a wall. I really want to know what they changed to break the clipboard service Guessing the X11 [X]Wayland migration KDE Plasma bug report? Should be fixed in 6.5.2. permalink fedilink source parent hideshow 6 child comments replies: [–] DevDave@piefed.social 3 points 4 months ago (1 child) Adjacent comment. I've found working in a true posix environment is drastically better than the oddities I dealt with Win32. One annoyance is Microsoft has never been able to implement fork(). Though i never messed with x11 as I was never motivated to see what it was like under the figurative hood. permalink fedilink source parent hideshow 1 child comment replies: [–] Septimaeus@infosec.pub 2 points 4 months ago It really is a hell of a lot more sane, instantly missed once you don’t have it. And yeah Fork’s a blessing when used with care lol permalink fedilink source parent [–] DevDave@piefed.social 3 points 4 months ago (3 children) Sorry, switched contexts there. Microsoft broke their clipboard service recently which makes me think they added "telemetry" collecting logic somewhere in there. permalink fedilink source parent hideshow 3 child comments replies: [–] Septimaeus@infosec.pub 1 point 4 months ago (2 children) Oh right, I misread. And yeah not sure (my win32 repro targets have all been locked for a while) but with all the facepalm regressions I’ve read about lately it really could be anything. permalink fedilink source parent hideshow 2 child comments replies: [–] DevDave@piefed.social 3 points 4 months ago (1 child) From my experience, the number one culprit of legacy code breaking is someone asking if anyone knows how it works. Second most common culprit is someone making a "quick patch" to legacy code. permalink fedilink source parent hideshow 1 child comment replies: [–] Septimaeus@infosec.pub 1 point 4 months ago lol damn, flinched at both even though I was prepared permalink fedilink source parent
[–] DevDave@piefed.social 3 points 4 months ago (1 child) Adjacent comment. I've found working in a true posix environment is drastically better than the oddities I dealt with Win32. One annoyance is Microsoft has never been able to implement fork(). Though i never messed with x11 as I was never motivated to see what it was like under the figurative hood. permalink fedilink source parent hideshow 1 child comment replies: [–] Septimaeus@infosec.pub 2 points 4 months ago It really is a hell of a lot more sane, instantly missed once you don’t have it. And yeah Fork’s a blessing when used with care lol permalink fedilink source parent
[–] Septimaeus@infosec.pub 2 points 4 months ago It really is a hell of a lot more sane, instantly missed once you don’t have it. And yeah Fork’s a blessing when used with care lol permalink fedilink source parent
[–] DevDave@piefed.social 3 points 4 months ago (3 children) Sorry, switched contexts there. Microsoft broke their clipboard service recently which makes me think they added "telemetry" collecting logic somewhere in there. permalink fedilink source parent hideshow 3 child comments replies: [–] Septimaeus@infosec.pub 1 point 4 months ago (2 children) Oh right, I misread. And yeah not sure (my win32 repro targets have all been locked for a while) but with all the facepalm regressions I’ve read about lately it really could be anything. permalink fedilink source parent hideshow 2 child comments replies: [–] DevDave@piefed.social 3 points 4 months ago (1 child) From my experience, the number one culprit of legacy code breaking is someone asking if anyone knows how it works. Second most common culprit is someone making a "quick patch" to legacy code. permalink fedilink source parent hideshow 1 child comment replies: [–] Septimaeus@infosec.pub 1 point 4 months ago lol damn, flinched at both even though I was prepared permalink fedilink source parent
[–] Septimaeus@infosec.pub 1 point 4 months ago (2 children) Oh right, I misread. And yeah not sure (my win32 repro targets have all been locked for a while) but with all the facepalm regressions I’ve read about lately it really could be anything. permalink fedilink source parent hideshow 2 child comments replies: [–] DevDave@piefed.social 3 points 4 months ago (1 child) From my experience, the number one culprit of legacy code breaking is someone asking if anyone knows how it works. Second most common culprit is someone making a "quick patch" to legacy code. permalink fedilink source parent hideshow 1 child comment replies: [–] Septimaeus@infosec.pub 1 point 4 months ago lol damn, flinched at both even though I was prepared permalink fedilink source parent
[–] DevDave@piefed.social 3 points 4 months ago (1 child) From my experience, the number one culprit of legacy code breaking is someone asking if anyone knows how it works. Second most common culprit is someone making a "quick patch" to legacy code. permalink fedilink source parent hideshow 1 child comment replies: [–] Septimaeus@infosec.pub 1 point 4 months ago lol damn, flinched at both even though I was prepared permalink fedilink source parent
[–] Septimaeus@infosec.pub 1 point 4 months ago lol damn, flinched at both even though I was prepared permalink fedilink source parent
[–] mic_check_one_two@lemmy.dbzer0.com 3 points 4 months ago Yeah, motherboard-level tracking is scary because even the OS won’t be able to detect it. The truly paranoid people (and security researchers) go as far as desoldering chips to ensure nothing phones home. permalink fedilink source parent