Menu

#216 "be" vats shouldn't have awt__uriGetter or swing__uriGetter

Need_for_security
closed-fixed
7
2005-07-24
2005-07-15
No

FIXED
The privileged scope that a "be" vat starts out in
should not have entries for awt__uriGetter
swing__uriGetter. In addition, to preserve
vat-swing-thread safety, these should not normally be
importable (whether via import__uriGetter or
unsafe__uriGetter) into these vats. It's unclear how
best to prevent the latter.

Followups

Comment Date By
As part of fixing 125402, I also made awt__uriGetter,
swing__uriGetter, and JPanel__quasiParser unavailable
in the privileged scope of a headless vat.
2002-Mar-10 02:21 markm

Discussion

  • Steve Jenson

    Steve Jenson - 2005-07-18
    • status: open --> closed-fixed
     
  • Mark Samuel Miller

    • assigned_to: nobody --> caplet
     

Log in to post a comment.