Jul 23 2008
JailBroke my 1st Gen 2.0 iPhone.
|
And the first thing i did with it….
|
Jun 11 2008
|
This is nice. There’s a how-to on how to convert an xbox 360 into a laptop at Engadet. The Nintendo DS sucks now. Shoot, add 3G, and I won’t even want a new iPhone. The same gentleman, Benjamin Heckendorn, also recently posted about converting a PS3 into a laptop. |
Mar 31 2008
|
Apparently Creative just dropped the last straw on the camels back. After a *year* of not supporting it’s flagship soundcard, the X-Fi, on Vista, a gentleman with handle Daniel_K decided to take it upon himself to release drivers that allow the card to work. I do understand that the reason Creative has not released these drivers is for legal reasons, but a year?!?! That is just unacceptable in the tech world. Any world, really. It just seems Creative did not conform to due diligence to get these cards licensed to work in Vista. Thanks for sending this over, Richard! |
Feb 29 2008
|
Article #1 here Article #2 here
Late in the (UTC) day on 24 February 2008, Pakistan Telecom (AS 17557) began advertising a small part of YouTube’s (AS 36561) assigned network. This story is almost as old as BGP. Old hands will recognize this as, fundamentally, the same problem as the infamous AS 7007 from 1997, a more recent ConEd mistake of early 2006 and even TTNet’s Christmas Eve gift 2004. Just before 18:48 UTC, Pakistan Telecom, in response to government order to block access to YouTube (see news item) started advertising a route for 208.65.153.0/24 to its provider, PCCW (AS 3491). For those unfamiliar with BGP, this is a more specific route than the ones used by YouTube (208.65.152.0/22), and therefore most routers would choose to send traffic to Pakistan Telecom for this slice of YouTube’s network. Since BGP relies on a transitive trust model, validation between customer and provider is important. In this case, PCCW (3491) did not validate Pakistan Telecom’s (17557) advertisement for 208.65.153.0/24. By accepting this advertisement and readvertising to its peers and providers PCCW was propagating the wrong route. Those who saw this route from PCCW selected it since it was a more specific route. YouTube was advertising 208.65.152.0/22 before the event started and the /24 was a smaller (and more specific) advertisement. According to usual BGP route selection process, the /24 was then chosen, effectively completing the hijack. Because of the fast detection and reaction of the YouTube staff and cooperation with other providers, service for their (sub-) prefix was interrupted for about an hour and forty minutes for some lucky customers and, at most, a bit more than two hours. The exact duration of the outage depends on your vantage point on the Internet. So, it’s heartwarming to know that two things are still true. It is still trivially possible to hijack prefixes (whether maliciously or inadvertently). I can go to sleep knowing that my neighbors are happily watching their LOLCATS. |
Jan 08 2008
|
Now this is a good idea. Security best practices define that in order to access a system, the user must know something, like username and password, and have something, traditionally something like a RSA SecurID keyfob, or smart card. However, if you get to the authentication phase, you’ve already established a TCP connection to the server, which is a risk in of itself. shimmer (via slashdot) is a project that requires you to have something, in this case, the shimmer client and public key of the server, to establish a TCP connection. The server has a set of ports, and only one of them is forwarded to the real server daemon. The port changes frequently, and to know which one will get you connected, you need the public key. Connect to the wrong one, and your IP is banned. Neat-o!
|
Jan 04 2008
Dec 28 2007
|
http://www.youtube.com/v/H5YB1Mmx7E4 The dipshits don’t want embedding of videos. :-\ |
Dec 20 2007
|
They want you to pay for it in every format you want it in. Fuck that! |