os-locale calls wmic with no extension and without explicit path

[stuartbrussell-intuit]

Our Windows app that uses os-locale has been flagged as a security risk because it will launch any file named "wmic", regardless of extension, and the file can be anywhere on the PATH, including the app's own directory. It could be a vbs file, for example.

The suggested secure way (if you have to use wmic):

1. Always use the exe extension.
2. Always use the full standard path to wmic.exe.

[sindresorhus]

2. Is this path the same for all Windows version and locales?

[sindresorhus]

// @MarkTiedemann Idea for a Windows binary, if you need project ideas. A simple binary to get the locale on Windows. So we don't have to use wmic.

[MarkTiedemann]

@sindresorhus Done. See: locale. Note that it prints en-US instead of en_US.

[MarkTiedemann]

Updated locale (v0.2.0) to work for Windows < Windows Vista, too.

:: If Windows Vista or greater
$ locale
{"locale":"en-US"}

:: Else
$ locale
{"lcid":1033}

@sindresorhus Let me know if you need anything else. :)

[sindresorhus]

I don't really see the point of supporting older than Vista. Those are ancient versions and not worth our time. I'm not going to support them anyway, so I personally preferred the first version that only printed a string, but I can work with this too and only use the locale property :)

[MarkTiedemann]

I don't really see the point of supporting older than Vista.

All right. I'll switch back to locale only then. This also simplifies the build process a lot.

locale v1.0.0 now only prints en-US again.