You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Need helping finding some key areas of the source code (for sandboxing) #2789
I would like help in finding 3 key areas of the Nodejs source code
1 - anywhere a file is written or read from the OS
2 - anywhere a network socket (or other networking item) is opened or closed
3 - anywhere a process is spawned / launched.
I can take it from there. Any help finding these .cc locations? I would like to try to remove these functionalities to better create a sandbox
changed the title [-]Need helping finding some key areas of the source code[/-][+]Need helping finding some key areas of the source code (for sandboxing)[/+]on Jun 21, 2020
Thank you for the excellent answer! I will try it out and see how it works. Am I the first to attempt something like this, or is there previous work I can borrow from?
@wysisoft I think the closest thing might be nodejs/node#33504 (and its predecessor nodejs/node#22112). Those operate at the C++ binding layer, instead of the libuv layer, though, so it’s a bit of a different approach with its own upsides and downsides
Activity
[-]Need helping finding some key areas of the source code[/-][+]Need helping finding some key areas of the source code (for sandboxing)[/+]addaleax commentedon Jun 22, 2020
@wysisoft I think the best thing you can do is look through the list of libuv functions and then grep for those in Node.js core?
wysisoft commentedon Jun 23, 2020
Thank you for the excellent answer! I will try it out and see how it works. Am I the first to attempt something like this, or is there previous work I can borrow from?
addaleax commentedon Jun 23, 2020
@wysisoft I think the closest thing might be nodejs/node#33504 (and its predecessor nodejs/node#22112). Those operate at the C++ binding layer, instead of the libuv layer, though, so it’s a bit of a different approach with its own upsides and downsides
PoojaDurgad commentedon Oct 18, 2020
@wysisoft - is this issue still outstanding? did @addaleax 's suggestion help you to resolve your issue?
wysisoft commentedon Oct 18, 2020
PoojaDurgad commentedon Oct 19, 2020
closing the issue as it resolved.