Issue 1516 in google-caja: Ses.UnsafeError should not be accessible

[googl...@googlecode.com]

Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 1516 by justinlp...@gmail.com: Ses.UnsafeError should not be
accessible
http://code.google.com/p/google-caja/issues/detail?id=1516

What steps will reproduce the problem?

1. Initialize Ses
2. Evaluate Ses.UnsafeError

What is the expected output? What do you see instead?

You get a reference to the _unfrozen_ Error primordial. This should not be
accessible after Ses has initialized.

Quoth Mark Miller, "That's a good point about ses.UnsafeError. Really, that
shouldn't be accessible after initialization even to SES privileged code.
Please file this as a bug, though not a security hole."

[googl...@googlecode.com]

Updates:
Labels: SES

Comment #1 on issue 1516 by erights: Ses.UnsafeError should not be
accessible
http://code.google.com/p/google-caja/issues/detail?id=1516

(No comment was entered for this change.)

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[googl...@googlecode.com]

Updates:
Owner: erights

Comment #3 on issue 1516 by eri...@google.com: Ses.UnsafeError should not
be accessible
https://code.google.com/p/google-caja/issues/detail?id=1516

[googl...@googlecode.com]

Updates:
Status: Started

Comment #4 on issue 1516 by erights: Ses.UnsafeError should not be