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

backport summer tests to iclab/centinel #59

Closed
ben-jones opened this issue Sep 24, 2014 · 8 comments
Closed

backport summer tests to iclab/centinel #59

ben-jones opened this issue Sep 24, 2014 · 8 comments
Assignees

Comments

@ben-jones
Copy link
Contributor

No description provided.

@ben-jones ben-jones self-assigned this Sep 24, 2014
@ben-jones ben-jones added this to the Alpha release milestone Sep 24, 2014
@ben-jones
Copy link
Contributor Author

Test primitives to migrate:

  1. SSL/TLS MITM attack test
  2. SSL Stripping test
  3. HTTP primitive migration (should be its own issue because there are other issues here, like browser emulation)
  4. more robust dns stuff (i.e chaos queries)
  5. traceroute (is this a primitive or a test? we should use the underlying os implementation)
  6. iran
  7. indonesia
  8. israel

#60 backports 1 and 2, 3-5 should probably be their own issues because they affect primitives, and we still need to migrate 6-8.

@gsathya, @rpanah, are you ok with including 6-8 in the alpha release, but pushing 3-5 back? 3-5 are basically redesigning our DNS, HTTP, and traceroute? primitives and I want to take the time to weigh the pros and cons of different options. Please comment below with your thoughts.

@gsathya
Copy link
Contributor

gsathya commented Sep 24, 2014

@gsathya, @rpanah, are you ok with including 6-8 in the alpha release, but pushing 3-5 back?

No. I vote for removing this from alpha release.

@ben-jones
Copy link
Contributor Author

@gsathya , to clarify, you vote for not including these tests?

@gsathya
Copy link
Contributor

gsathya commented Sep 24, 2014

@gsatha, to clarify, you vote for not including these tests?

Yes

@ben-jones
Copy link
Contributor Author

@gsathya, @rpanah, actually, looking at these tests, we will need to build the traceroute, HTTP, and DNS primitives to make this work, so I agree that we should push back so that we can have extra time to reflect on how to best build the measurement primitives.

@rpanah
Copy link
Collaborator

rpanah commented Sep 24, 2014

@ben-jones I vote for not including 6-8 as they aren't actual tests. These were toy experiments to test functionality and to see what we can detect. There is no reason for them to be included in the alpha release.

@phillipa
Copy link

I'd say include include whatever basic DNS/HTTP Get/Traceroute we have now and then iterate to add more features/make them better (e.g., headless browsing).

@rpanah has been meeting with a student here with some experiments that would benefit from the platform so we're getting some more concrete items that would be useful to implement (e.g., HTTP Proxy traceroute etc.)

Also for CitLab's purposes a good HTTP Get is absolutely required and should be a very high priority feature/task. That is their bread and butter (along with logging DNS results, and tcpdumps to a lesser extent).

@rpanah
Copy link
Collaborator

rpanah commented Feb 23, 2015

At this point, we have 1-4 (HTTP, DNS, traceroute, TLS). Iran, Indonesia, and Israel never had their own custom experiments in the older code base.
@ben-jones, I think this issue needs to be closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants