Correctly Handle Messages from Unknown Peers #332
No reviewers
Labels
No Label
applications
BLOCKED
bug
design
duplicate
enhancement
fixed?
funding-needed
help wanted
infrastructure
invalid
payments
qubes
question
ready-for-implementation
refactor
spam
tapir-server
testing
tor
wontfix
No Milestone
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: cwtch.im/cwtch#332
Loading…
Reference in New Issue
No description provided.
Delete Branch "first_contact"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Drone Build Status: success
https://build.openprivacy.ca/cwtch.im/cwtch/916
discussion was had about permissions, tracking unknowns, and querying vals of unknowns and changes were made to protect getVal requests, and since the meaning of isApproved is changing to rename isAllowed.
this is to smooth the introduction process of new peers, following a twitter DM style. Protection is still affored for anyone with BlockUnknownPeers enabled.
Previously descreibed schemes in the 2020 Feb doc on getVal and new peer experience around this that still haven't been implemented are futher shelved for now
Drone Build Status: success
https://build.openprivacy.ca/cwtch.im/cwtch/918