"I would also like to inform you that your GoDaddy domains are in my possession, one fake purchase and they can be repossessed by godaddy and never seen again D:
I see you run quite a few nice websites so I have left those alone for now, all data on the sites has remained intact. Would you be willing to compromise? access to @N for about 5minutes while I swap the handle in exchange for your godaddy, and help securing your data?"
And then later the attacker explains the attack in detail.
Naoki Hiroshima, the victim, wonders "what’s more shocking, the fact that PayPal gave the attacker the last four digits of my credit card number over the phone, or that GoDaddy accepted it as verification". The answer is that GoDaddy accepting this as verification is more shocking. The last 4 digits of your credit card appear everywhere, from restaurant receipts to not-quite-logged-in-so-we'll-need-your-password-again-to-do-anything-really-important sections of websites. They are not really secure. That isn't to say that PayPal should give out these digits without significant verification, but what GoDaddy did is far worse.
GoDaddy accepted the last 4 digits as verification, but also required the first 2 digits. If you know anything about how credit cards work, you'll know that requiring the first 2 digits add almost no extra security. The first digit will be either 4 (Visa), 5 (MasterCard) or 3 (Amex) in the vast majority of cases. For Amex cards, the second digit will be 4 or 7. For Visa and MasterCard, the second digit (actually the first 4-6 digits) indicate which bank issued the card. So for most cards, there are only 22 or so pairs of starting digits, and if you know the card type or bank you can narrow things down further. To make matters (much) worse, "GoDaddy allowed him to keep trying until he nailed it. Insane."
Yet another reason I'm happy that I no longer use GoDaddy.
Apparently an art installation at the Microsoft office Studio D in Redmond, made by Devorah Sperber out of 75,000 beads.
I wonder if the beads were placed by hand. I feel like it would almost be less time consuming to make a robot to do this. Either way, awesome.
The book Commodore: A Company on the Edge by Brian Bagnall has additional details about the history of the 128. I especially liked the story about the origin of the Z80 used in the prototype 128.
Thanks, former self.
A couple of years later I realized that it would have been easy to reduce the amount of data that game had to load by almost 4 orders of magnitude. In my defense, I was 12. :-P
The emulator code is based on the Open Source Universal Amiga Emulator which is about 400k lines of C code, which were ported to Native Client. All the code is available in Open Source for anyone interested in porting their own C/C++ code to the web.
- Self2010 - present
- Staff Software Engineer, 2000 - 2010
- Oracle CorporationSoftware Engineer, 1998 - 2000
- MKSSoftware Developer (intern), 1996 - 1997
- VirtekSoftware Developer (intern), 1996 - 1996
- WatcomSoftware Developer (intern), 1994 - 1995
I'm an independent software developer, father of two, and that guy with the foam Lego head.
I like making things. By profession I'm a software developer (ie: I make code) but I also like making other kinds of things. I've dabbled in electronics, wood working, various arts and crafts and Lego robotics.
I'm also interested in science and technology in general, mathematics, computers, robots, science fiction (especially "hard" SF), video games, animation and photography.
When it comes to software development, I'm mostly a generalist, but the areas I'm especially interested in are programming languages, collaborative filtering, and graphics (both 2D and 3D). I'm also known to have opinions about web development and user interface design, though my UI designer friends would probably laugh at the latter.
I used to work at Google where I was one of the first engineers on AdWords, AdSense, and Google's billing systems. I later started Google Reader as a 20% project. Check out my LinkedIn Profile if you want a more complete picture of my CV.
- University of WaterlooComputer Science