Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Broker: investigate non-domain-fronting secure client / proxy registrations #13

Closed
keroserene opened this issue Jan 21, 2016 · 2 comments
Closed

Comments

Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
@keroserene
Copy link
Owner

@keroserene keroserene commented Jan 21, 2016

No description provided.

@arlolra arlolra self-assigned this Jan 22, 2016
@arlolra
Copy link
Collaborator

@arlolra arlolra commented Mar 22, 2016

Pasting discussion from email,

in the Flashproxy case, registration wasn't
bidi, and I think they imagined using insecure
channels to register like OSSes. In Snowflake,
the client is making TLS connections with the
broker, which amounts to the same thing as
encrypting the payload with the facilitator's
public key.

Also,

There's also the case where an adversary DOSes the facilitator with a
bunch of fake client or proxy registrations and things like that.

This is now #25

Also, there is the potential that in the future we might need some
sort of non-domain-fronting rendezvous. It seems that right now we
have an ecosystem of tools growing that assumes domain-fronting will
always be available & effective. May be worth considering how to
prepare for regions where this might not work as well in the future.

So this ticket should probably be for that.

@arlolra arlolra removed their assignment Mar 22, 2016
@keroserene keroserene changed the title Broker: more secure client / proxy registrations, similar to flashproxy facilitator Broker: investigate non-domain-fronting secure client / proxy registrations Dec 17, 2016
@arlolra
Copy link
Collaborator

@arlolra arlolra commented Mar 22, 2018

@arlolra arlolra closed this Mar 22, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment