Repository navigation
Need helping finding some key areas of the source code (for sandboxing) #2789
Description
Activity
- 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
- Yes this was helpful thanks…On Sun, Oct 18, 2020 at 12:53 PM Pooja D P ***@***.***> wrote: @wysisoft <https://github.com/wysisoft> - is this issue still outstanding? did @addaleax <https://github.com/addaleax> 's suggestion help you to resolve your issue? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2789 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADTZR3D7KLU5JS647IH6ORTSLM2TDANCNFSM4OEBLMYA> .
closing the issue as it resolved.
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