Autoblock Blocked Peers #182

sarah · 2019-01-08T19:00:23Z

sarah commented

2019-01-08 19:00:23 +00:00

Start using the underlying ricochet block to autoblock. Add explicit Deprecation notes and functionality to V2 Peers.

buildbot commented

2019-01-08 19:08:25 +00:00

Drone Build Status: success

https://build.openprivacy.ca/cwtch.im/cwtch/338

Drone Build Status: success https://build.openprivacy.ca/cwtch.im/cwtch/338

dan commented

2019-01-09 20:27:21 +00:00

what do the "LookupContactV3" funcs do? cus they've only ever returned hard coded values. doesnt seem like we're using them like we wanted? can we drop them entirely?

sarah commented

2019-01-09 20:43:49 +00:00

They determine whether an incoming connection is allowed or not. In the case of a blocked peer, we want to deny them a connection as soon as they attempt to authenticate (we may also want to provide functionality to autoblock any peer not on a list)

They are in ricochet to allow contact management, in Cwtch we have not yet dived into it completely, this is the start of that process.

They determine whether an incoming connection is allowed or not. In the case of a blocked peer, we want to deny them a connection as soon as they attempt to authenticate (we may also want to provide functionality to autoblock *any* peer not on a list) They are in ricochet to allow contact management, in Cwtch we have not yet dived into it completely, this is the start of that process.

dan closed this pull request

2019-01-09 22:09:14 +00:00

sarah referenced this issue from a commit

2019-01-13 23:53:03 +00:00

Merge branch 'autoblock' of cwtch.im/cwtch into master...

Sign in to join this conversation.

No reviewers