Hacker News new | past | comments | ask | show | jobs | submit login

You can also do http(s) over DNS: http://code.kryo.se/iodine/ . Nice way to avoid paying captive portals, although probably not legal.



Why not?


In USA and UK at least unauthorised access or use of a computer is criminalised. On some situations you can argue for assumed consent, the law doesn't operate on "if I can do it then it's authorised". Unless you can show you have permission then it's not authorised, ergo not legal.

AIUI; not legal advice.


But the premise was to circumvent crap such as captive portals. Doing that on your own computer (mostly in a public wlan), I don't see any reason against it.


You're still circumventing security measures to use somebody else's hardware in a way they clearly don't want you to. That's illegal in most cases.


Who is the "someone else" in your case? Where does the someone else's hardware come from? OP mentioned this to get rid off e.g captive portals.

Iodine requires a client and a server. Both belong to you, what is the problem here? That I use a network to transmit packets? We are not talking about installing iodine on someone else's computer!


Not sure if you're trolling, but the network is being accessed by bypassing the captive portal. The network is being accessed in a way that isn't permitted.


So the network is not password protected, DNS (or ICMP) works normally, but somehow using it in a particular way is not permitted? Then why does it work at all?


And how should I know that there is a captive portal? I connect (connection is established after receiving IP address!) and use iodine (or similar).


I'm sure the jury will be delighted to hear your explanation.


"I used iodine all the time, so I can't even notice the presence of a captive portal, if any."

"My son handles the computer stuff for me, I don't even know about that logging page you're talking about."

"I thought restricted networks had a WPA-2 password? That's what they use at my workplace."


"The door to the house was open, move of the stuff was tied down, how could i be expected to know I wasn't authorised to use it??"

Judges just aren't that stupid.


Here's the thing: I never give my real name to captive portals. I don't even give a real email address.

Who can tell me with a straight face that this is criminal behaviour


Only that the comparison is stupid.


Why should this go to court? I'm not sure if you have understood what this thread was about.


> That I use a network to transmit packets?

Maybe I'm not understanding this correctly, but if a coffee shop has wifi and you need to enter info into a captive portal before you can use their network, by circumventing it, the "Someone else" is the coffee shop owner, and the hardware is their router.

"Please get off my router if you don't agree to my conditions". "Nah I'm just using DNS, it's fine" probably is not an admissible excuse.


The assumption from the coffee shop is that wifi == internet == browser, which is not true. Why should I open the browser if I don't need it?


Do you dispute that a coffee shop providing WiFi with a captive portal only intends to provide web access through that portal? Just as they only intend customers to take sugar packets for use in their coffee, etc..

If the shop don't intend the use its not authorised. Your ethical framework may not put any value on that lack of authorisation, but you see the action is unauthorised, surely?


In this case, you're potentially using the public wlan's router in an unauthorized manner.


What is authorized and what is not? It is (usually) not presented.


Especially when the network is open, because for instance Android devices automatically connect to networks like that


Can I do HTTP over DNS over HTTP over DNS over HTTP over DNS over HTTP over DNS over HTTP over DNS?


You do realize DNS is not a fully featured protocol right...


What does this shady technique (dns tunneling) have to do with dns-over-ssl?


why shady? (assuming that shady is meant in a negative way)


It's unfit for general use and abuses the DNS protocol to stealthily convey data, hence the shadiness. You're right, it needn't be used in a negative way. DNS tunneling is slow, needs polling for incoming traffic (due to the way dns works over udp) and is usually used to circumvent firewalls for both good (censorship) and bad reasons (exfiltrating data).


It's clearly to evade a security control.. As if you approached a door, to find it locked, but then discovered the front window was unlocked and let yourself in.. Clearly the occupant didn't want you to enter, and just failed to secure the entire building. Pretty sure nobody would ever suggest it was okay for you to enter in such a way.


I doubt that. If DNS traffic is not filtered or blocked, it is clearly intended to transmit data that way.

On a public wlan I first try to use VPN with port 53 (not DNS). If it works, I'll use it that way.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: