Skip to content

Feature request: More private blob ticket #192

Description

@FerLuisxd

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 add an optional key to the ticket to make it harder to extract that information?
Or use a temporal relay (adding extra layer of security/complexity) that returns a smaller ticket, but at least guarantees that the original ticket text string is deleted.

Maybe it is a bit overeacting but this is one more step towards more truly private transfers

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions