New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fully qualify shutdown command #702

Closed
ferventcoder opened this Issue Apr 22, 2016 · 0 comments

Comments

Projects
None yet
1 participant
@ferventcoder
Member

ferventcoder commented Apr 22, 2016

Shutdown.exe is called to handle the canceling of any shutdown/restart operations in progress.

It was recently discovered that a user can thwart shutdown by placing it in the path before the actual shutdown.exe.

https://groups.google.com/d/msgid/chocolatey/35853b3e-1d64-4c9b-91fa-59773046f16b%40googlegroups.com

@ferventcoder ferventcoder self-assigned this Apr 22, 2016

@ferventcoder ferventcoder added this to the 0.9.10 milestone Apr 22, 2016

ferventcoder added a commit to ferventcoder/choco that referenced this issue Apr 22, 2016

(chocolateyGH-702) Fully qualify shutdown.exe
Previously, choco would use the first shutdown that it came across in
the path, which may not be the shutdown that it should be looking to
use. This could cause issues.

With this change, choco will fully qualify the path to the
shutdown.exe. If a user is running under SysWOW, the shutdown they will
find will be in the redirected path, but it is still valid to handle
the canceling of any shutdown/restart operations in progress.

ferventcoder added a commit that referenced this issue Apr 22, 2016

Merge branch 'stable'
* stable:
  (GH-702) Fully qualify shutdown.exe
  (maint) Suggest ignore checksum switch on error
  (GH-435) Get-FileName enhancements
  (maint) ignore .vscode folder
  (GH-535) install template information
  (GH-696) Approved/Failing statuses on install
  (maint) Provide better warning on non-admin prompt

@ferventcoder ferventcoder added 3 - Done and removed 2 - Working labels Apr 22, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment