-
Notifications
You must be signed in to change notification settings - Fork 20
do not use os-homedir #12
base: master
Are you sure you want to change the base?
Conversation
os-homedir hard codes paths which does not work reliably and is a security issue.
remove from os-homedir from package.json
Can't accept this until Node.js 0.10 support is dropped AND we're prepared to break anyone using it. |
@iarna I created this polyfill since we use Will you consider using this in place of os-homedir? I think it would just require updating this PR. |
@doowb So if I understand correctly, your polyfill differs in that it checks
This isn't true for OSX anymore. (Which I'm guessing you're aware given the later construction of It's not guaranteed to be true on Linux either, if you have, for instance, an LDAP based user directory. As @pravi considers ever guessing at a homedir a security issue, I'm not sure that improves things any? It's not really for me to say though. The existing |
Hi @iarna
Yes, because I'm following the steps that I found in the
I didn't know that, thanks for point it out. I followed what
|
@doowb I'd like to hear from @pravi if your polyfill actually resolves their concerns? 'cause I don't see how it would? I mean, if you view this as a legitimate security issue of course. The main difference between your code and libuv, is that libuv gets to call |
We use |
Does #19 address this PR? |
Its hard coded paths are a serious security issue. Closes: #11