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

Figure out how to handle blocking https traffic if not authenticated #4

Open
tomoconnor opened this issue Nov 4, 2012 · 2 comments

Comments

@tomoconnor
Copy link
Owner

Currently, the captive portal isn't effective against https traffic (or actually, anything other than http). Figure out how to expand the current rule set to:

a) redirect a https request to the portal landing page.

b) block https traffic until authenticated.

@cbetta
Copy link
Contributor

cbetta commented Nov 4, 2012

Shouldnt it probably just redirect all traffic to that box, on all ports?

@tomoconnor
Copy link
Owner Author

I thought about that.. Might require a subtly different ruleset.. Or some
other TCP/UDP server running on the box to intercept and so on.

On Sun, Nov 4, 2012 at 10:04 PM, Cristiano Betta
[email protected]:

Shouldnt it probably just redirect all traffic to that box, on all ports?


Reply to this email directly or view it on GitHubhttps://github.com//issues/4#issuecomment-10056112.

Tom O'Connor

http://tomoconnor.eu
[email protected]
twitter: @DevOpsTom

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

No branches or pull requests

2 participants