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

Update Init7 rules - #9707

Merged
jeremyn merged 5 commits into
EFForg:masterfrom
J0WI:init7
Nov 6, 2017
Merged

jeremyn merged 5 commits into
EFForg:masterfrom
J0WI:init7

Conversation

@J0WI

@J0WI J0WI commented Apr 29, 2017 •

Copy link
Copy Markdown
Contributor

@Hainish Hainish added the top-1m label Apr 29, 2017
@cschanaj cschanaj mentioned this pull request Apr 30, 2017
@jeremyn jeremyn closed this Oct 30, 2017
@jeremyn jeremyn reopened this Oct 30, 2017
@J0WI

J0WI commented Oct 31, 2017

Copy link
Copy Markdown
Contributor Author

I rebased my branch, so tests are passing now.

@jeremyn

jeremyn commented Nov 1, 2017 •

Copy link
Copy Markdown
Contributor

Fiber7.ch.xml:

  • This ruleset should be merged into Init7.xml. All of the covered domains redirect to somewhere under https://www.init7.net.

Init7.xml:

@jeremyn jeremyn self-assigned this Nov 1, 2017
@J0WI

J0WI commented Nov 4, 2017

Copy link
Copy Markdown
Contributor Author

https://ipv6.init7.net should be Refused, not Mismatch

Nope, it's accessible, but only over IPv6.
I've addressed all other points.

@jeremyn

jeremyn commented Nov 4, 2017

Copy link
Copy Markdown
Contributor

I've updated the checklist through 20b9bca.

I'm not able to easily test https://ipv6.init7.net but I marked it as okay anyway because it doesn't really matter.

I think we can remove the *.fiber7.init7.net domains and Customers comment entirely. The *.fiber7.init7.net domains time out with both HTTPS and plain HTTP, which is enough to leave them out.

@J0WI

J0WI commented Nov 4, 2017

Copy link
Copy Markdown
Contributor Author

I think we can remove the *.fiber7.init7.net domains and Customers comment entirely. The *.fiber7.init7.net domains time out with both HTTPS and plain HTTP, which is enough to leave them out.

This depends on whether the customer have configured a public HTTP service or not.

@jeremyn

jeremyn commented Nov 4, 2017

Copy link
Copy Markdown
Contributor

I'm confused by the PTR comment. If I test one of the *.fiber7.init7.net domains found by Sublist3r with dig [some IP].fiber7.init7.net any, I only get an A record, and no PTR record. So I'm not really sure what you're saying with the comment.

Also the comments in this section should be testable and I'm not sure what a test case is for this.

@J0WI

J0WI commented Nov 4, 2017

Copy link
Copy Markdown
Contributor Author

Use dig -x [smoe IP]

@jeremyn

jeremyn commented Nov 4, 2017

Copy link
Copy Markdown
Contributor

Okay, the PTR record is actually for host [reverse of some IP].in-addr.arpa and can be found with dig [reverse of some IP].in-addr.arpa any. I'm still not sure what you're trying to say with the comment.

@J0WI

J0WI commented Nov 4, 2017

Copy link
Copy Markdown
Contributor Author

This host are managed by the customers, so it' up to them if they want to support HTTPS or not. It's impossible to list all of them.

@jeremyn

jeremyn commented Nov 6, 2017

Copy link
Copy Markdown
Contributor

How about instead of "Customers (PTR Resource Records)" we say "User-controlled subdomains not covered here"?

@J0WI

J0WI commented Nov 6, 2017

Copy link
Copy Markdown
Contributor Author

Like so?

@jeremyn
jeremyn merged commit 93883ae into EFForg:master Nov 6, 2017
@jeremyn

jeremyn commented Nov 6, 2017

Copy link
Copy Markdown
Contributor

That's fine, thanks. Merged.

@jeremyn jeremyn removed their assignment Nov 6, 2017
@J0WI
J0WI deleted the init7 branch November 6, 2017 22:29
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants