R2NorthstarTools / R2NorthstarTools/FlightCore
Communicating security concerns about plugins when installing
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 94
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Description
Unlike Squirrel mods which are limited to SQVM, plugins have full userspace access (basically anything Northstar has access to, just like any binary).
As such, it's trivial to create a plugin that is essentially just a virus so one should use caution when installing plugins and only install them from trusted sources. At the same time, most other modding communities (BeatSaber, BoneLab, ...) do mods via DLLs by default and they seem to be handling everything just fine...
So how do we communicate caution to the player installing a plugin while also avoiding to completely cannibalise plugins?
Contributor guide
No contributing guide indexed for this repository
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
No files, tests, or entry points are identified in the issue. First clarify the desired warning, its placement in the plugin installation flow, and how completion will be evaluated; then locate the relevant installer UI and add tests for the agreed behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, tauri
- Domain
- desktop, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100