[Webkit-unassigned] [Bug 158778] New: Don't leak the names of [private] functions in JS built-ins

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed Jun 15 01:51:28 PDT 2016


            Bug ID: 158778
           Summary: Don't leak the names of [private] functions in JS
    Classification: Unclassified
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Bindings
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: adam.bergkvist at ericsson.com
                CC: cdumez at apple.com

If I implement a function add() as a JS built-in based on a private function @privateAdd(), I need to duplicate all type checking done in @privateAdd() to prevent error messages to reveal the "privateAdd" name.

For example: "Argument 1 ('item') to Bar.privateAdd must be an instance of FooItem"

The approach with adding a native JS function to both a 'name' and a '@name' slot,  mentioned in [1], makes this less of an issue.

[1] https://bugs.webkit.org/show_bug.cgi?id=158777

You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20160615/d7b1cb6b/attachment.html>

More information about the webkit-unassigned mailing list