Used to work in the DNS business. "It will take up to 24 hours to propagate" is a way to manage expectations and prevent support calls from coming in within the first 24 hours after a DNS change, not a reflection of actual DNS propagation times.
I don't know how things work now, but at least a few years ago there were plenty of DNS server that would take basically the full 48hours to update, regardless of TTL.
I think the rise of no-fixed-IP load balancers like Amazon ELB has dramatically reduced that.
I think Chrome is able to do this because it separates tabs into processes, but I don't think there's a good way for Firefox to do it since everything is in a single process. https://bugzilla.mozilla.org/show_bug.cgi?id=486262
I don't think this has to do with multiprocess. The instance of HTML engine (geckk?) just needs to track who used the audio API.
I think the problem with that is it doesn't work with Flash audio. With multiprocess browsers, the Flash audio can be associated with a tab, but that's awkward/not possible if everything is in the same process.
Yes but you gain a lot of interesting information about what's going on, plus you are back in control. Whitelist places you trust. Keep things blocked that you don't like. If that breaks the experience, walk.
Sure. I used script blockers for a while. But after having to whitelist a huge number of them and loosing very long and precious time, I gave in. I do not put sensitive and important data on my computer. (Actually I was not doing that for a very long time even before giving in.) I always work on remote hosts. Therefore I treat my desktop as a security research one. Of course I would not do that on my desktop I were r…
Regarding "I do not put sensitive and important data on my computer" and "I always work on remote hosts", I must respectfully disagree. Never mind the fact that you set a bad example for newbies, being so caviler with your own safety harms the security of the rest of us. Downloading and executing random software off the Internet---the raison d'être of modern web browsers---is a good way to get owned. Just because you don't use your computer for anything important doesn't mean that it cannot be compromised and used to attack me. Plus, if you use your computer to log into other computers to do real work, then your computer is extremely important! A successful compromise would give attackers all the same remote access you have. Admittedly, that's not what your everyday, ordinary malware is after, but it's the principal of the thing that bothers me.
I am half serious, but how about making HTML served in TXT records a standard trick for serving small web pages very quickly? There are way fewer network round trips: 1. DNS query for TXT record for example.com 2. DNS reply with HTML content Compared with the traditional 7 steps: 1. DNS query for A record for example.com 2. DNS reply with x.x.x.x 3. TCP SYN to port 80 4. TCP SYN/ACK 5. TCP ACK 6. HTTP GET 7. HTTP rep…
For another fantastic abuse of DNS, the Iodine* project uses DNS to tunnel IP which is just obscene. http://code.kryo.se/iodine/ (Why? Lots of captive portal wifi hotspots (think hotel/train etc) seem to allow DNS resolutions before stopping your other traffic.) * DNS uses port 53 which is the same as the atomic number for Iodine ;)
Woah, awesome. I've used the http://dnstunnel.de/ tunneling scripts before, and they're a bit of a pain to setup (mostly because of the perl library requirements).
Meh, interesting thought, but a few things come to mind: - It could take multiple days to update the website for the entire world - It would be very easy to spoof the entire site - It would probably slow down the rest of the queries the DNS server would be responding to at the time. Also, updating DNS can be a pain for sites that aren't managing their own records.
Used to work in the DNS business. "It will take up to 24 hours to propagate" is a way to manage expectations and prevent support calls from coming in within the first 24 hours after a DNS change, not a reflection of actual DNS propagation times.
I hate the term "DNS propagation". It confuses people, and makes them think things that aren't true, like a new domain isn't usable until it "propagates" through the Internet.
Sure. I used script blockers for a while. But after having to whitelist a huge number of them and loosing very long and precious time, I gave in. I do not put sensitive and important data on my computer. (Actually I was not doing that for a very long time even before giving in.) I always work on remote hosts. Therefore I treat my desktop as a security research one. Of course I would not do that on my desktop I were r…
Regarding "I do not put sensitive and important data on my computer" and "I always work on remote hosts", I must respectfully disagree. Never mind the fact that you set a bad example for newbies, being so caviler with your own safety harms the security of the rest of us. Downloading and executing random software off the Internet---the raison d'être of modern web browsers---is a good way to get owned. Just because you…
I'm not telling my setup is bullet proof. I'm just saying I gave in on some threats. I do not try to protect against all threats via all possible ways. I try to make my sensitive data to be unattractive and harder to get.
Latest part that you edited out was a question I would raise but it seems like you also think that would not hold.
Even though this setup is not secure. It's more secure than many everyday usage patterns. In a way at least..
I am half serious, but how about making HTML served in TXT records a standard trick for serving small web pages very quickly? There are way fewer network round trips: 1. DNS query for TXT record for example.com 2. DNS reply with HTML content Compared with the traditional 7 steps: 1. DNS query for A record for example.com 2. DNS reply with x.x.x.x 3. TCP SYN to port 80 4. TCP SYN/ACK 5. TCP ACK 6. HTTP GET 7. HTTP rep…
For another fantastic abuse of DNS, the Iodine* project uses DNS to tunnel IP which is just obscene. http://code.kryo.se/iodine/ (Why? Lots of captive portal wifi hotspots (think hotel/train etc) seem to allow DNS resolutions before stopping your other traffic.) * DNS uses port 53 which is the same as the atomic number for Iodine ;)
dam, that got downvoted into oblivion haha. honest question... although i dont believe it should be, a third party injecting javascript to demonstrate an exploit might be...
What a bunch of nonsense. TXT records were intended for arbitrary use. Why in the world are these companies pulling data from unknown sources and dumping it RAW into their output? Wow. Good find, IMO.
Sure. I used script blockers for a while. But after having to whitelist a huge number of them and loosing very long and precious time, I gave in. I do not put sensitive and important data on my computer. (Actually I was not doing that for a very long time even before giving in.) I always work on remote hosts. Therefore I treat my desktop as a security research one. Of course I would not do that on my desktop I were r…
Additionally to then there's also the various things that track identity and behaviour. Tell me what you search and click, and I'll tell you what you think? (That's not fixed with a simple add-on of course.)
There is also google. But we use them in a way or not.
There are some nut-jobs or bad-ass people out there not using google, going with security enhanced phones and ddg. This does not make average or the 95percentile bad behaved.
This makes us only low security sensitive and targets.