Your periodic reminder that #microsoft is not a competent or serious company:
blog.orange.tw/posts/2025-01-w…
(@bagder is remarkably restrained in the quoted responses. I would have gone off the rails, but do not need to, because we decided on day one that #varnishcache would not run on Windows).
If you think that is not bad enough, read the Cyber Safety Review Board's report about the Microsoft Exchange clowncar:
cisa.gov/sites/default/files/2…
WorstFit: Unveiling Hidden Transformers in Windows ANSI!
📌 This is a cross-post from DEVCORE. The research was first published at Black Hat Europe 2024. Personally, I would like to thank splitline, the co-author of this research & article, whose helpOrange Tsai
daniel:// stenberg://
in reply to Poul-Henning Kamp • • •I suppose I just don't get surprised or upset anymore when another proprietary vendor does something silly but we have to survive in their environment.
I think this is entirely a Microsoft problem, even if I fear that we might need to patch something ugly into curl to mitigate the worst risks.
Poul-Henning Kamp
in reply to daniel:// stenberg:// • • •It is absolutely, entirely and 100% a Microsoft problem.
And it is a prime example of "Marcitecture":
"Whatever you do with this Unicode thing, DO NOT UPSET PROGRAMMERS so much the might look at other platforms! All existing code SHALL JUST WORK!!1!"
But what really amazes me, is how and why anybody still takes them seriously about /anything/ ?!
vsz
in reply to daniel:// stenberg:// • • •vsz
in reply to daniel:// stenberg:// • • •curl: re-enable UNICODE by default · curl/curl-for-win@357bc12
GitHubPeter Krefting
in reply to daniel:// stenberg:// • • •Command line parsing on Windows is a pain; I haven't used Windows compilers in over a decade, so I don't know if you can get a
int main(int argc, wchar_t* argv[])
entry point these days. Using that should parse the command line as Unicode text and then one can convert each argument to UTF-8 or whatever and call the real "main" with that.