Skip to content

Intercept and track MessagePort traffic #301

@BurningEnlightenment

Description

@BurningEnlightenment

The current electron documentation suggests implementing communication between the main world and context isolated renderer worlds via MessageChannels / MessagePorts1.

However, this extension isn't really helpful if we apply the above advice as all relevant IPC traffic does not flow through the ipcMain / ipcRenderer interfaces.

Therefore I suggest additionally tracking all MessagePort instances which have been transferred through the relevant ipc interfaces. This would require either intercepting the postMessage calls or the message events.

Footnotes

  1. https://www.electronjs.org/docs/latest/tutorial/message-ports#communicating-directly-between-the-main-process-and-the-main-world-of-a-context-isolated-page

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions