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

Already on GitHub? Sign in to your account

Properly intercept network-related access #6

leto opened this Issue May 5, 2010 · 1 comment


None yet
2 participants

leto commented May 5, 2010

See what we need to do to intercept network-related access. It seems that the Socket PMC inherits from FileHandle, which we already intercept, so that is good for us.

Tests should be added to show that, for instance, PIR subroutines are not allowed to bind to network ports by default.


theory commented May 5, 2010

PL/ParrotU should be able to do anything, FWIW. I think I'd just focus on that for now, in absence of any Parrot security infrastructure, and not worry about keeping it from doing stuff. My $0.02.

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