tauri-apps / tauri-apps/tauri-docs
[docs] Clarification about development security
Nobody has claimed this yet.
- Dominant language
- MDX
- Stars
- 1.1k
- Forks
- 887
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 48
Description
The documentation here: https://v2.tauri.app/security/lifecycle/#development-server says the following
This is also the case for the built-in Tauri development server and exposes your frontend and assets to the local network. Additionally, this allows attackers to push their own frontend code to development devices in the same network as the attacker.
It would be nice to explain in which cases attackers are able to push their own frontend code to development devices, and how it is possible. E.g. is it possible if you just develop a desktop app? What about a mobile app?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked Development Server section at https://v2.tauri.app/security/lifecycle/#development-server and trace the documented behavior for desktop and mobile development. Determine when an attacker can push frontend code to development devices and explain the mechanism and applicable cases; the documentation is done when those scenarios are clear to readers.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100