Access to streams via built-in-functions cause the security checkpoint to send a STREAM message to a
security manager, if one exists.
However, it seems that if accessing streams via the .Stream class does not get supervised, as its
relevant methods are not protected. Consider, e.g. this:
REXX-ooRexx_5.2.0(MT)_64-bit 6.06 18 Apr 2026
rexxtry.rex lets you interactively try REXX statements.
Each string is executed when you hit Enter.
Enter 'call tell' for a description of the features.
Go on - try a few... Enter 'exit' to end.
say .stream~instancemethod("new")~isProtected
0
........................................... rexxtry.rex on WindowsNT
say .stream~method("init")~isProtected
0
........................................... rexxtry.rex on WindowsNT
Shouldn't there be a security checkpoint for creating stream objects in addition to using the stream
BIFs?
---rony
_______________________________________________
Oorexx-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
