Agreed. How about ADVAPI.DLL ? ( http://www.whale.to/b/nsa3.html )
Now all you need to do is get hardware manufactures to include the necessary wireless hardware somewhere (say in a USB hub chip or wifi chip) and of course given that the drivers for these are binary blobs (it's the MOST secure way sir! (I'm joking)) who knows what code the NSA has asked them include in that driver ? (NSA talking to NEC (or some other chip fab): Include our binary blob in you binary blob or we will fuck you up m'kay ?) Now how do you feel about running your 'binary blob' driver in linux ?
yea, same ISP as I use (A&A ISP) and I picked them for having *exactly* that kind of an attitude. Oh yea and they understand the word 'linux' and provide really proper support:)
Try an Revo R3600 (~ £150 GBP) and XBMC live. The Revo is excellent, very very quite (much quieter than my sky+ PVR), about the size of an original apple tv, has HDMI and VGA output AND comes with a VESA stand that that you can use to hang it directly on the back of your TV (unless it's wall mounted).
XMBC live installs very easily and quickly, once you've found a usb cd/dvdrom to boot it from:)
The only other thing I needed was a remote / usb receiver but I just bought the cheapest windows media centre one I could find.
HTH
1) DNS server receives request to resolve x.com
2) DNS server ask for it to be resolved by root server
3) poison DNS server responds first, poisoning the DNS server
4) connection closed
5) root server responds, response is ignored
Why can't we just:
1) DNS server receives request to resolve x.com
2) DNS server ask for it to be resolved by root server
3) poison DNS server responds first (with correct id etc), poisoning the DNS server
4) After first response is received (DNS server assumes it *could* be false) it keeps the port open for a time (say 5 seconds) waiting for a second response
5) If no other response is received then it assumes the first response is genuine and uses it.
6) If a second response is received it discards both as 'potentially bad' and trys again.
Obviously this will mean any DNS request will take as long as we wait in step 4 above (5 seconds in this example), but this is on the initial query which can then be cached so the performance hit should not as bad as it first seems.
What about if each device (and disc) has say for example, 100 keys ? 1 gets compromised and removed form future discs releases and the players still work with the other 99. Also there's no reason why new players can't be updated from 'tinternet with new keys.
Slashdot Mirror
what about http://www.ipfire.org/ ? Needs a bit more grunt than dd-wrt but it is very easy to upgrade....
unless you also have software on the PC
Agreed. How about ADVAPI.DLL ? ( http://www.whale.to/b/nsa3.html ) Now all you need to do is get hardware manufactures to include the necessary wireless hardware somewhere (say in a USB hub chip or wifi chip) and of course given that the drivers for these are binary blobs (it's the MOST secure way sir! (I'm joking)) who knows what code the NSA has asked them include in that driver ? (NSA talking to NEC (or some other chip fab): Include our binary blob in you binary blob or we will fuck you up m'kay ?) Now how do you feel about running your 'binary blob' driver in linux ?
correct link: http://en.m.wikipedia.org/wiki/Key_disclosure_law
so if I down loaded this in the uk, I could be sent to prison for not giving the authorities the password that I don't have... http://en.m.wikipedia.org/wiki/Key_disclosure_lawt
yea, same ISP as I use (A&A ISP) and I picked them for having *exactly* that kind of an attitude. Oh yea and they understand the word 'linux' and provide really proper support :)
http://hardware.slashdot.org/story/13/07/09/0214225/former-valve-hardware-designer-recounts-management-difficulties
Jeri pissed ( understandably ) , asks and gets given tech she was working on, moves on to form startup.
I think this story is *way off* the mark. If you have the time then listen to this podcast to understand why: http://www.theamphour.com/the-amp-hour-147-absorptive-augmented-actuality/
Try an Revo R3600 (~ £150 GBP) and XBMC live. The Revo is excellent, very very quite (much quieter than my sky+ PVR), about the size of an original apple tv, has HDMI and VGA output AND comes with a VESA stand that that you can use to hang it directly on the back of your TV (unless it's wall mounted). XMBC live installs very easily and quickly, once you've found a usb cd/dvdrom to boot it from :)
The only other thing I needed was a remote / usb receiver but I just bought the cheapest windows media centre one I could find.
HTH
Isn't there a simple solution to this ?
Current situation:
1) DNS server receives request to resolve x.com
2) DNS server ask for it to be resolved by root server
3) poison DNS server responds first, poisoning the DNS server
4) connection closed
5) root server responds, response is ignored
Why can't we just:
1) DNS server receives request to resolve x.com
2) DNS server ask for it to be resolved by root server
3) poison DNS server responds first (with correct id etc), poisoning the DNS server
4) After first response is received (DNS server assumes it *could* be false) it keeps the port open for a time (say 5 seconds) waiting for a second response
5) If no other response is received then it assumes the first response is genuine and uses it.
6) If a second response is received it discards both as 'potentially bad' and trys again.
Obviously this will mean any DNS request will take as long as we wait in step 4 above (5 seconds in this example), but this is on the initial query which can then be cached so the performance hit should not as bad as it first seems.
Or have I missed something ?
What about if each device (and disc) has say for example, 100 keys ? 1 gets compromised and removed form future discs releases and the players still work with the other 99. Also there's no reason why new players can't be updated from 'tinternet with new keys.