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.

Sign up for GitHub

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

Jump to bottom

Protect Connections #226

Closed
hannahhoward opened this issue Sep 28, 2021 · 0 comments · Fixed by #229
Closed

Protect Connections #226

hannahhoward opened this issue Sep 28, 2021 · 0 comments · Fixed by #229
Labels
effort/hours Estimated to take one or several hours estuary issues identified from estuary usage or requested by code owners of estuary exp/intermediate Prior experience is likely helpful P1 High: Likely tackled by core team if no one steps up

Comments

@hannahhoward
Copy link
Collaborator

hannahhoward commented Sep 28, 2021 •
edited
Loading

What

go-graphsync should protect Libp2p connections on both the requestor and responder for the duration of the request.

because go-graphsync knows when requests begin and end, this should be fairly straight forward to do.
@hannahhoward hannahhoward added need/triage Needs initial labeling and prioritization estuary issues identified from estuary usage or requested by code owners of estuary P0 Critical: Tackled by core team ASAP P1 High: Likely tackled by core team if no one steps up effort/hours Estimated to take one or several hours exp/intermediate Prior experience is likely helpful and removed P0 Critical: Tackled by core team ASAP need/triage Needs initial labeling and prioritization labels Sep 28, 2021
@hannahhoward hannahhoward mentioned this issue Sep 29, 2021
Merged
marten-seemann pushed a commit that referenced this issue Mar 2, 2023
@aarshkshah1992
More data transfer logging (#226)
1d44c41 
* data-transfer logging

* data-transfer logging
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
effort/hours Estimated to take one or several hours estuary issues identified from estuary usage or requested by code owners of estuary exp/intermediate Prior experience is likely helpful P1 High: Likely tackled by core team if no one steps up
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Protect Libp2p Connections ipfs/go-graphsync
1 participant
@hannahhoward