Skip to content
This repository has been archived by the owner on Nov 6, 2020. It is now read-only.

Handle syncing attack vectors. #1079

Closed
arkpar opened this issue May 12, 2016 · 3 comments
Closed

Handle syncing attack vectors. #1079

arkpar opened this issue May 12, 2016 · 3 comments
Assignees
@arkpar
Labels
F1-security 🛡 The client fails to follow expected, security-sensitive, behaviour. P2-asap 🌊 No need to stop dead in your tracks, however issue should be addressed as soon as possible.
Milestone
1.2 Security

Comments

@arkpar
Copy link
Collaborator

arkpar commented May 12, 2016

@arkpar arkpar added the F1-security 🛡 The client fails to follow expected, security-sensitive, behaviour. label May 12, 2016
@gavofyork gavofyork added the P2-asap 🌊 No need to stop dead in your tracks, however issue should be addressed as soon as possible. label May 21, 2016
@gavofyork gavofyork added this to the 1.2 Civility milestone May 21, 2016
@gavofyork
Copy link
Contributor

Maybe helped by #1095 ?

@gavofyork gavofyork modified the milestones: 1.3 Civility, 1.2 Security May 31, 2016
@gavofyork
Copy link
Contributor

All in, now.

@gavofyork gavofyork reopened this Jun 18, 2016
@arkpar
Copy link
Collaborator Author

arkpar commented Jun 20, 2016

#345 to track tests

@arkpar arkpar closed this as completed Jun 20, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@arkpar arkpar

Labels
F1-security 🛡 The client fails to follow expected, security-sensitive, behaviour. P2-asap 🌊 No need to stop dead in your tracks, however issue should be addressed as soon as possible.
Projects
None yet
Milestone
1.2 Security
Development

No branches or pull requests
2 participants
@gavofyork @arkpar