Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(core): expose invoke key for custom IPC implementations #11235

Merged
merged 1 commit into from
Oct 6, 2024

Conversation

lucasfernog
Copy link
Member

custom IPC systems that manually call Webview::on_message must know the invoke key checked by Tauri. This exposes that key in the App/AppHandle instances.

This is safe because the key is never leaked to remote denied webview URLs

custom IPC systems that manually call Webview::on_message must know the invoke key checked by Tauri. This exposes that key in the App/AppHandle instances.

This is safe because the key is never leaked to remote denied webview URLs
@lucasfernog lucasfernog requested a review from a team as a code owner October 5, 2024 16:20
Copy link
Contributor

github-actions bot commented Oct 5, 2024

Package Changes Through abe190a

There are 5 changes which include @tauri-apps/api with patch, tauri with patch, tauri-bundler with patch, tauri-cli with patch, @tauri-apps/cli with patch

Planned Package Versions

The following package releases are the planned based on the context of changes in this pull request.

package current next
@tauri-apps/api 2.0.1 2.0.2
tauri-bundler 2.0.1 2.0.2
tauri 2.0.1 2.0.2
@tauri-apps/cli 2.0.1 2.0.2
tauri-cli 2.0.1 2.0.2

Add another change file through the GitHub UI by following this link.


Read about change files or the docs at github.com/jbolda/covector

@lucasfernog lucasfernog merged commit 03e7590 into dev Oct 6, 2024
20 checks passed
@lucasfernog lucasfernog deleted the feat/app-invoke-key branch October 6, 2024 10:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants