Conversation

Notices

1. Embed this notice
   Poul-Henning Kamp (bsdphk@fosstodon.org)'s status on Friday, 10-Jan-2025 22:38:48 JST Poul-Henning Kamp

   • daniel:// stenberg://

   Your periodic reminder that #microsoft is not a competent or serious company:

   https://blog.orange.tw/posts/2025-01-worstfit-unveiling-hidden-transformers-in-windows-ansi/

   (@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:

   https://www.cisa.gov/sites/default/files/2024-04/CSRB_Review_of_the_Summer_2023_MEO_Intrusion_Final_508c.pdf

   • Embed this notice
     Peter Krefting (nafmo@social.vivaldi.net)'s status on Friday, 10-Jan-2025 22:38:51 JST Peter Krefting

     in reply to

     • daniel:// stenberg://

     @bagder @bsdphk 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.

   • Embed this notice
     daniel:// stenberg:// (bagder@mastodon.social)'s status on Friday, 10-Jan-2025 22:38:52 JST daniel:// stenberg://

     in reply to

     @bsdphk 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.