2 ms·
Samsung and every other vendor outside of China have announced lower sales as people keep their phones longer. While everyone admits that Mac keyboards are hor
by scarface74 7y ago
Samsung and every other vendor outside of China have announced lower sales as people keep their phones longer.
While everyone admits that Mac keyboards are horrible, Mac sales are so small compared to everything else Apple sells, it doesn’t really hurt their bottom line
both of my roommates who have iPhone Xs are thinking about switching to Android after being plagued with constant hardware and software issues.
Anecdote is not data.
It does not sound like you have any legitimate information about how Windows compatability increases vulnerabilites beyond vague statements.
Let me tell you a little story about how the half dozen different ways to represent and encode a string in Windows led to a security issue in IIS where you could just encode a DOS command in a browser window and have it execute remotely....
https://www.sans.org/reading-room/whitepapers/threats/paper/458 https://www.sans.org/reading-room/whitepapers/threats/paper/...
Or a DCOM vulnerability in 2019. No one uses DCOM anymore.
https://www.cvedetails.com/cve/CVE-2003-0352/ https://www.cvedetails.com/cve/CVE-2003-0352/
- edoceo 7y agoOh, crap! DCOM! I'm have trauma just seeing those letters in that order.
- icebraining 7y agoAs it says right on the URL, that CVE is from 2003, not 2019, and it doesn't affect any Windows version past XP.
- scarface74 7y agoYes and by then you already had the 7 plus versions of defining a string dating back to Windows 3 (1992). Backwards compatibility was already a problem then. Since then, MS has had 15 more years worth of cruft on top of that s d yet more ways to define a string. If backwards compatibility caused a security vulnerability back then, how much old Windows 95 code do you think is causing issues now?