#1880: Parrot_new should not need to be passed previously-created interps
----------------------+-----------------------------------------------------
Reporter: dukeleto | Owner: whiteknight
Type: RFC | Status: new
Priority: normal | Milestone: 2.11
Component: none | Version: 2.10.0
Severity: medium | Keywords:
Lang: | Patch:
Platform: |
----------------------+-----------------------------------------------------
Currently Parrot_new requires being passed in the 1st interp that was ever
created to create subsequent interpreter objects.
In PL/Parrot, many interps must be created, some are trusted, some are
not. But they all need to know about the 1st interp that was created,
which, from a security standpoint, is suboptimal. Here is a snippet from
PL/Parrot's plparrot.c :
{{{
untrusted_interp = Parrot_new(NULL);
/* Must use the first created interp as the parent of subsequently
created interps */
trusted_interp = Parrot_new(untrusted_interp);
}}}
--
Ticket URL: <https://trac.parrot.org/parrot/ticket/1880>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets
