5 ms·
At this point, a "free to use" license for XP or better yet win2k up to win7, would be worth it for m$ for the PR and goodwill. "you can get it if you want it"
by h2odragon 6y ago
At this point, a "free to use" license for XP or better yet win2k up to win7, would be worth it for m$ for the PR and goodwill.
"you can get it if you want it" is just lame.
m$ should, ideally, bite the bullet and do a (stripped if need be) source release of what they can, explain what they can't release. Everyone will then benefit from the relief from worry and lack of friction things like emulation and software archeology and etc will gain.
- vb6sp6 6y agosounds like a security nightmare
- beervirus 6y agoPlenty of that code is still (one assumes) in use in Windows 10. Why make it easier for someone to find a zero-day?
- vbrandl 6y agoBy that logic, you can't use any open source software...
- Bancakes 6y agoYou can, but it's your problem if you don't stringently configure SELinux and have clear policies for yourself. If you use Linux like Windows thinking it's more secure, and run everything with 'sudo' "Just to make sure it doesn't crash or pop an annoying prompt.", you're worse off.
- Someone1234 6y agoThey should release software with known security problems, that they have said they won't be fixing? Please no... Botnets are large enough as-is. Plus a lot of people under-estimate the cost and difficulty in releasing the source code of previously proprietary software. You don't just slap it onto Github and everyone goes home, you often need a team of lawyers to look at third party licensing and go through the code file by file looking for potential liabilities. Code that started out open source software has to narrow third parties to only specific licenses/waivers. Code that has for tens of years been closed source may contain licensed source code (e.g. decoder libraries) that they don't own the license to publish for just one example.
- anticensor 6y agoStrip those parts then.
- cycloptic 6y ago>They should release software with known security problems, that they have said they won't be fixing? Please no... Botnets are large enough as-is. The source code has already been leaked, and I would bet that malware authors have no problem with acquiring it illegally. While security researchers working within the law may not be able to look at it at all. The current situation does a lot more to help botnets than it does to help honest customers. >Plus a lot of people under-estimate the cost and difficulty in releasing the source code of previously proprietary software. You don't just slap it onto Github and everyone goes home, you often need a team of lawyers to look at third party licensing and go through the code file by file looking for potential liabilities. [...] Code that has for tens of years been closed source may contain licensed source code (e.g. decoder libraries) that they don't own the license to publish for just one example. I'm sorry, I just have no sympathy for the trillion dollar company that trapped themselves in restrictive license agreements and then wants to cheap out on lawyers. It is entirely a problem of their own making, and I would expect them to pay to fix it.
- intern4tional 6y agoThe issue isn't malware authors acquiring it the source, the issue is that other people would then build said source and run it (XP) or worse, build products on it as XP was very stable. Those systems would then get infected and become botnets. You don't see people flying in trijets anymore as they are dangerous, likewise you don't want to encourage or incentivize people to use or build products on an insecure OS. Sympathy doesn't matter in the business world, costs do. No normal company is going to undertake a legal review of an unsupported product; it simply isn't worth it.
- a5withtrrs 6y agoI'd never heard of trijets being dangerous before and I can't find anything to support that claim. I thought the issue with them was the expenses around building and maintaining them.
- ThrowawayR2 6y agoEven if somehow the leaked XP code were legitimized, it wouldn't do anybody much good since the driver model has changed significantly since XP and none of the hardware OEMs are going to go back to producing XP compatible drivers again.
- deleted 6y ago[deleted]
- Kuraj 6y ago> m$ What is it, 2000?
- h2odragon 6y agono, my grudge against them goes back to the days of 16bit and their kneecapping DOS era comms software. its only childish for so long, then its "quirky"
- sumtechguy 6y agoMS outsourced/bought a lot of stuff so they may not have a clear line of release it without a bunch of legal work. Something like that can be done I am sure. But the cost would be decently high. Also some interesting portions of the OS are under a 'view but do not touch' license already. Such as MFC, ATL, and the CRT and others. Depending on which SDK or Visual C++ you grab you can get whole examples of interesting bits of the code. I know for example one of the fun ones is the pipes screen saver code is an example in one of the Visual C++ disks (5.0 I think). I recompiled it years ago to make every joint a teapot and the hard one to find was the bend.
- mook 6y agoI was under the impression that at least the CRT part was fine to modify. At least, Firefox used to ship a custom version with jemalloc, I think (with the necessary patches checked in as ed scripts so that they could avoid having the original source in the repository).
- sumtechguy 6y agoThat may be true. I would have to go back and re-read the licence. In practice I do not think they minded too much so long as you were not claiming it as your own and were just changing it for your program only and not overwriting the ones in the system32 dir.
- easton 6y agoWhy wouldn't they just release Windows 10 instead? They don't "need" the money (because any self-respecting IT department that has a modicum of budget will pay for Microsoft 365, where they almost give away the Windows licenses and support, or have a SA license), so the only people still really buying Windows are home users with their laptops. Enthusiasts could maybe submit pull requests, and they could get rid of even more in-house dev/QA staff. It's the latest version of the kernel, so new drivers work. And they are still patching it. The real money is in Azure/Office/MSSQL anyway.
- ko9000 6y agoor in support contracts more accurately, which would disappear if others would bring ability to support those (by access to same source code and ability to fix bugs)