Skip to content
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

FIX Ensuring composer can write to it's cache directory #122

Conversation

ScopeyNZ
Copy link
Contributor

Resolves #121 . This pulls and slightly modifies the logic linked in the issue. In addition to that code this patch will check that the provided HOME environment variable is also writable before blindly assuming it's okay.

This fix is not compatible with the SS3 line of this module and although we're in "Security fixes only" for that line I'll still PR a SS3 fix for this as it's a fairly critical bug.

@robbieaverill
Copy link
Contributor

It might be worth making this PR for SS3 first so we can merge it up through to SS4

@robbieaverill
Copy link
Contributor

What's the justification for adding this here? This module doesn't actually use Composer at all, just parses the lock files

@ScopeyNZ
Copy link
Contributor Author

What's the justification for adding this here? This module doesn't actually use Composer at all, just parses the lock files

Good point. I'll double check the original cause of the issue was the fact that HOME was unreliable opposed to "update checker" was not installed.

@ScopeyNZ
Copy link
Contributor Author

I'll close this and update the update-checker module. It seems the issue here is that HOME is being used blindly.

@ScopeyNZ ScopeyNZ closed this Sep 13, 2018
@ScopeyNZ
Copy link
Contributor Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants