n0-computer / n0-computer/sendme

Feature request: More secure blob ticket

Open
#130 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
1.2k
Forks
78
PR merge metrics
No merged PRs in 30d

Description

What would you like to see?

More secure blob ticket or a more private way to share tickets that do not expose private information

Why would this be helpful?

Currently the ticket contains super vital infromation (engraved in the ticket itself, forever):
Public IPV4 and opened port
PRIVATE IPV4 and opened port
Public IPV6 and opened port
PRIVATE IPV6 and opened port
Same hash everytime if sharing the same file

Meaning that if someone gets hands on the ticket, they could easily decode it and extract super private information from your network, as well as link the file shared that is created using the filename and filesize (meaning it is always the same if trying to share the same file).

The only thing that really changes is port and public key.

Maybe we could change it so the user can select which Ips to add to the string? Like only public ipv4?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files, tests, or entry points. First locate how blob tickets encode network addresses, file identity, and keys, then clarify the desired privacy model and address-selection behavior. Done should mean tickets no longer expose unintended private network information while preserving the required file-sharing workflow.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
cli, networking, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.