Holy crap! Will it ever end? Is there a safe website in the world?!
http://www.theregister.co.uk/2011/06/10/codemasters/
http://www.theregister.co.uk/2011/06/10/spain_anonymous_arrests/
http://www.theregister.co.uk/2011/06/10/rsa_chief_security_officer/
http://www.theregister.co.uk/2011/06/09/banks_replacing_tokens/
http://www.theregister.co.uk/2011/06/09/citibank_hack_attack/
http://www.theregister.co.uk/2011/06/08/data_breach_bill/
http://www.theregister.co.uk/2011/06/08/password_re_use_survey/
http://www.theregister.co.uk/2011/06/08/sony_brazilian_site_suspended/
http://www.theregister.co.uk/2011/06/06/lockheed_martin_securid_hack/
http://www.theregister.co.uk/2011/06/06/lulzsec_fbi_affiliates_hack/
http://www.theregister.co.uk/2011/06/03/sony_pictures_hacked/
http://www.theregister.co.uk/2011/06/02/nato_warned_over_anonymous/
http://www.theregister.co.uk/2011/06/02/friendster_password_hack_fears/
http://www.theregister.co.uk/2011/06/01/military_contractor_2nd_rsa_securid_hack/
http://www.theregister.co.uk/2011/05/31/pbs_hacked/
http://www.theregister.co.uk/2011/06/10/ico_tmobile_data/
http://www.theregister.co.uk/2011/06/10/codemasters/
http://www.theregister.co.uk/2011/05/27/lockheed_securid_hack_flap/
http://www.theregister.co.uk/2011/05/25/more_sony_hacks/
http://www.theregister.co.uk/2011/05/24/comodo_reseller_hacked/
http://www.theregister.co.uk/2011/05/24/sony_playstation_breach_costs/
http://www.theregister.co.uk/2011/05/23/sony_bmg_greece_hacked/
http://www.theregister.co.uk/2011/05/21/sony_subsidiary_hacked/
http://www.theregister.co.uk/2011/05/20/norway_military_computer_attack/
http://www.theregister.co.uk/2011/05/20/sony_phishing/
http://www.theregister.co.uk/2011/05/18/sony_playstation_account_hijacking/
http://www.theregister.co.uk/2011/05/17/french_piracy_monitor_hacked/
http://www.theregister.co.uk/2011/05/17/oz_cop_vuln_seize/
http://www.theregister.co.uk/2011/05/16/hacker_duo_sentenced/
http://www.theregister.co.uk/2011/05/16/square_enix_website_hack/
http://www.theregister.co.uk/2011/05/14/playstation_network_attack_from_amazon/
http://www.theregister.co.uk/2011/05/13/veracode_playstation_hack_analysis/
http://www.theregister.co.uk/2011/05/10/supposed_anonymous_hack/
http://www.theregister.co.uk/2011/05/08/sony_psn_saga_snowballs/
http://www.theregister.co.uk/2011/05/05/lastpass_password_reset/
http://www.theregister.co.uk/2011/05/04/sony_implicates_anonymous/
http://www.theregister.co.uk/2011/05/03/sony_hack_exposes_more_customers/
http://www.theregister.co.uk/2011/05/03/korea_hack_bank/
http://www.theregister.co.uk/2011/04/28/latvia_hack_attack/
http://www.theregister.co.uk/2011/04/18/esa_hack_follow_up/
http://www.theregister.co.uk/2011/04/18/esa_website_hack/
http://www.theregister.co.uk/2011/04/18/byzantine_hades_cyber_espionage/
http://www.theregister.co.uk/2011/04/13/wordpress_hack_attack/
http://www.theregister.co.uk/2011/04/11/barracuda_networks_attack/
http://www.theregister.co.uk/2011/03/29/oz_govt_email_hack/
http://www.theregister.co.uk/2011/03/30/comodo_gate_latest/
http://www.theregister.co.uk/2011/03/18/fbi_hollywood_celeb_hack_probe/
Culminating in...
http://www.theregister.co.uk/2011/06/10/spain_anonymous_arrests/
Have hackers been getting better, more mischievous, or more public? Are we just getting better at detecting hacks? Are there more or more public white hat hackers? Has everyone suddenly realized how much important information lives in the cloud and finally started reporting on hacking?
WTF is going on?
Personally, I think it's a combination but mostly people are being more vigilant about hacking attempts (and detecting footprints from successful intrusions) and the hackers are getting better and more brazen.
UPDATE:
Here's another from today: http://kotaku.com/5810939/the-latest-victim-of-the-account-hacking-horde-is-epic-games
UPDATE 2:
Aaaaaand another: http://kotaku.com/5811372/i-guess-it-was-bethesdas-turn-to-get-hacked
I am a student studying computer science (programming) and networking. These are my notes.
Friday, June 10, 2011
Wednesday, May 11, 2011
Fun Fact of the Day
I read somewhere a few weeks ago that Erlang took up 500K for a new "thread." I also read from the same source that programs could easily chew up massive (read: 16GB "server memory" costing ~$500 today from Newegg) amounts of memory. Well, using back of the envelope calculations I figured out that (assuming a 1MB thread size instead of 512KB) a server receiving 1Gbps would need:
Gbit = 1024 Mbit
Mbit ~= 1000Kbit
Kbit ~= 1000 Bits
1,024,000,000 bits downstream
DIVIDED BY
8 bits per byte
EQUALS
128,000,000 MegaBytes downstream
128,000,000
DIVIDED BY
650 Bytes (roughly the size of a request packet in a DOS attack with a long string name attached to the URL)
EQUALS
196,923 (and some change) <-- This approximates the number of request packets coming in
Now we're going to assume each request creates it's own thread so that we don't have to worry about privacy or code or variables spilling over from other users...
196,923 packets incoming
MULTIPLIED BY
1024 (1 MegaByte and roughly double the minimum space required to open a new thread)
EQUALS
201,649,230 (and some change)
Of course all this assumes that our packet queue takes up 0 memory and our processor is able to handle the memory allocations, etc. and we aren't even beginning to count things like memory overhead from pointers BUT it's the best estimation I've seen. And it indicates that I can very easily handle 1 Gbps DDoS attack on my server by writing it in extremely lightweight Erlang.
The design of my implementation of the server will GREATLY influence the amount of memory it chews up with each request and the stability of the server and where the performance bottlenecks will be. I believe designing to survive a DDoS attack would be an excellent choice for most servers and should be attempted.
Gbit = 1024 Mbit
Mbit ~= 1000Kbit
Kbit ~= 1000 Bits
1,024,000,000 bits downstream
DIVIDED BY
8 bits per byte
EQUALS
128,000,000 MegaBytes downstream
128,000,000
DIVIDED BY
650 Bytes (roughly the size of a request packet in a DOS attack with a long string name attached to the URL)
EQUALS
196,923 (and some change) <-- This approximates the number of request packets coming in
Now we're going to assume each request creates it's own thread so that we don't have to worry about privacy or code or variables spilling over from other users...
196,923 packets incoming
MULTIPLIED BY
1024 (1 MegaByte and roughly double the minimum space required to open a new thread)
EQUALS
201,649,230 (and some change)
Of course all this assumes that our packet queue takes up 0 memory and our processor is able to handle the memory allocations, etc. and we aren't even beginning to count things like memory overhead from pointers BUT it's the best estimation I've seen. And it indicates that I can very easily handle 1 Gbps DDoS attack on my server by writing it in extremely lightweight Erlang.
The design of my implementation of the server will GREATLY influence the amount of memory it chews up with each request and the stability of the server and where the performance bottlenecks will be. I believe designing to survive a DDoS attack would be an excellent choice for most servers and should be attempted.
Wednesday, March 16, 2011
Personal Issues (or RemoteFX)
So after a solid week of research, installation, reinstallation, and troubleshooting (and not necessarily in that order) I discovered why I couldn't get my server to work even when following some excellent step by step instructions.
RemoteFX actually requires two physical GPU's. Nowhere is this mentioned in the documentation because on servers chipset (and now integrated CPU) GPU's are basically at 100% penetration. RemoteFX needs the discrete GPU that will power the VM's and enable resource sharing. RemoteFX also needs a secondary display adapter to run the video capture software on. Why this is not mentioned anywhere or had to be implemented in this way I have no idea but there you have it.
RemoteFX actually requires dual GPU's even if one is extremely weak or even software based.
Hope you aren't stuck with an adapted Dell workstation without a video out and only one PCIe x16 slot :(
RemoteFX actually requires two physical GPU's. Nowhere is this mentioned in the documentation because on servers chipset (and now integrated CPU) GPU's are basically at 100% penetration. RemoteFX needs the discrete GPU that will power the VM's and enable resource sharing. RemoteFX also needs a secondary display adapter to run the video capture software on. Why this is not mentioned anywhere or had to be implemented in this way I have no idea but there you have it.
RemoteFX actually requires dual GPU's even if one is extremely weak or even software based.
Hope you aren't stuck with an adapted Dell workstation without a video out and only one PCIe x16 slot :(
Tuesday, March 1, 2011
It's a beautiful day in the neighborhood!
It always feels like it's been ages since I did an update. Today I thought again of Mr. Rogers (aka Fred Rogers) and decided to name this post in his honor even though it has nothing to do with him. RIP Fred. ;_;
Today I worked out a better way to configure my VM's. I was working the walkthrough on setting up Citrix's XenDesktop Express (which by-the-by, does not have a time limit but rather user limit) when I noticed the walkthrough video included on the DVD talked about an article with several suggestions and among them was disabling SuperFetch. After a few days of digesting the info and finding a good place to try it (school of course, not work) I figured out some of the magic :) We run a VMWare ESXi/vSphere 4.1 server at school and (long story short) have bunches of verrrry slow VM's on there that would be much more useful if they required less time. For example, an update to an instance of an Exchange server running on the machine might take 30 minutes or more. Frankly that's unacceptable. After some testing I came a few conclusions about maximizing performance of virtual machines and have written them up here.
Windows 7 VM's:
Not sure where the perfect balance lies but somewhere between 1 and 1.5 GB's of RAM the VM goes from slow and choppy to silky smooth.
Suggestions:
Set RAM at 1.5GB
Disable SuperFetch
Turn off the page file
Minimize video RAM
Exchange 2010 SP1 on 2008 R2:
Have not done much testing here but here's what I've got so far...
Suggestions:
Set RAM to 4GB
Turn off the page file
Minimize video RAM
Windows Server 2008 R2 with Global Catalog or Local Domain Controller functions:
Testing done on a Citrix XenServer install. Notably performance actually improved after disabling the page file.
Suggestions:
Set RAM to 1.5GB
Turn off the page file
Minimize video RAM
That's it for now folks, maybe I'll update this in the future (hopefully!) but probably not. I at least hope it was helpful for someone :) Thanks for reading!
Today I worked out a better way to configure my VM's. I was working the walkthrough on setting up Citrix's XenDesktop Express (which by-the-by, does not have a time limit but rather user limit) when I noticed the walkthrough video included on the DVD talked about an article with several suggestions and among them was disabling SuperFetch. After a few days of digesting the info and finding a good place to try it (school of course, not work) I figured out some of the magic :) We run a VMWare ESXi/vSphere 4.1 server at school and (long story short) have bunches of verrrry slow VM's on there that would be much more useful if they required less time. For example, an update to an instance of an Exchange server running on the machine might take 30 minutes or more. Frankly that's unacceptable. After some testing I came a few conclusions about maximizing performance of virtual machines and have written them up here.
Windows 7 VM's:
Not sure where the perfect balance lies but somewhere between 1 and 1.5 GB's of RAM the VM goes from slow and choppy to silky smooth.
Suggestions:
Set RAM at 1.5GB
Disable SuperFetch
Turn off the page file
Minimize video RAM
Exchange 2010 SP1 on 2008 R2:
Have not done much testing here but here's what I've got so far...
Suggestions:
Set RAM to 4GB
Turn off the page file
Minimize video RAM
Windows Server 2008 R2 with Global Catalog or Local Domain Controller functions:
Testing done on a Citrix XenServer install. Notably performance actually improved after disabling the page file.
Suggestions:
Set RAM to 1.5GB
Turn off the page file
Minimize video RAM
That's it for now folks, maybe I'll update this in the future (hopefully!) but probably not. I at least hope it was helpful for someone :) Thanks for reading!
Thursday, February 24, 2011
I think I just figured out UBB (usage based billing)
See I've been reading about this via DSL Reports and Ars Technica and between their posts and a post by Peter Nowak I do believe I have this figured out.
1) ISP's will not disclose data on congestion.
It's complicated but basically I believe congestion is created for political reasons. Not to support UBB mind you but to leverage the most money out of content delivery networks like LimeLight and Akamai. You'd have to do a lot of reading to see why I came to that conclusion but all my information stems from the discussion on NANOG around the Level(3)/Comcast dispute.
2) Marginal cost for ISP's is falling. Fixed costs are fixed.
High users of broadband don't really cost an ISP more money and we already know that. Netflix and (many) others claim a cost of less than 3cents/GB and falling to deliver traffic. So we know the ISP's are not proposing this to help cover the marginal cost of delivering a GB. On the other hand fixed costs are probably not decreasing as fast as ISP's would like.
3) ISP costs are tied to the price consumers pay.
I could look up a million economics theses supporting this or I could leave that as an exercise to the reader.
4) The more subscribers an ISP has then the less each pays (since almost all costs are fixed).
5) This encourages ISP's to pursue as many customers as possible at as high a density as possible.
Let's say it costs $250,000 to hook up a neighborhood. Each house costs another $250 to set up individually. Each GB costs 3cents (and falling!) to deliver. Hmmm... I wonder which cost the ISP is most concerned with recovering?
6) An ISP will deploy whatever methods it deems necessary to increase subscribers.
See this is arguably one of the great parts of capitalism. The ISP actually wants to spread its costs out as much as possible so it will continue lowering its prices (and reaching new customers!) until...
7) The bean-counters say it we go lower we might start losing money (or not making as much altogether).
Since the hardware costs cannot be lowered (I'm certain they've tried this approach as its the cheapest and least resistant) the ISP moves on to business strategies.
8) Someone says "Hey, what if we charged some users more and some less?"
The conversation might go something like this:
Executive A: "That's a great idea! How do we do it?"
Executive B: "It'll be like a toll road. You already pay taxes but the more you use the more you pay."
Conclusion: So the ISP in attempting to broaden its reach and connect the most households (subsidizing its costs and lowering its risk through a greater pool of customers) has developed what it describes as a "fair" billing system. There are other details like how an ISP wouldn't want wholesale customers competing with itself but this is basically the situation and the motivations as far as I can tell. Whether this is fair or an appropriate solution to the ISP's incessant search for improved efficiency is ultimately up to you.
1) ISP's will not disclose data on congestion.
It's complicated but basically I believe congestion is created for political reasons. Not to support UBB mind you but to leverage the most money out of content delivery networks like LimeLight and Akamai. You'd have to do a lot of reading to see why I came to that conclusion but all my information stems from the discussion on NANOG around the Level(3)/Comcast dispute.
2) Marginal cost for ISP's is falling. Fixed costs are fixed.
High users of broadband don't really cost an ISP more money and we already know that. Netflix and (many) others claim a cost of less than 3cents/GB and falling to deliver traffic. So we know the ISP's are not proposing this to help cover the marginal cost of delivering a GB. On the other hand fixed costs are probably not decreasing as fast as ISP's would like.
3) ISP costs are tied to the price consumers pay.
I could look up a million economics theses supporting this or I could leave that as an exercise to the reader.
4) The more subscribers an ISP has then the less each pays (since almost all costs are fixed).
5) This encourages ISP's to pursue as many customers as possible at as high a density as possible.
Let's say it costs $250,000 to hook up a neighborhood. Each house costs another $250 to set up individually. Each GB costs 3cents (and falling!) to deliver. Hmmm... I wonder which cost the ISP is most concerned with recovering?
6) An ISP will deploy whatever methods it deems necessary to increase subscribers.
See this is arguably one of the great parts of capitalism. The ISP actually wants to spread its costs out as much as possible so it will continue lowering its prices (and reaching new customers!) until...
7) The bean-counters say it we go lower we might start losing money (or not making as much altogether).
Since the hardware costs cannot be lowered (I'm certain they've tried this approach as its the cheapest and least resistant) the ISP moves on to business strategies.
8) Someone says "Hey, what if we charged some users more and some less?"
The conversation might go something like this:
Executive A: "That's a great idea! How do we do it?"
Executive B: "It'll be like a toll road. You already pay taxes but the more you use the more you pay."
Conclusion: So the ISP in attempting to broaden its reach and connect the most households (subsidizing its costs and lowering its risk through a greater pool of customers) has developed what it describes as a "fair" billing system. There are other details like how an ISP wouldn't want wholesale customers competing with itself but this is basically the situation and the motivations as far as I can tell. Whether this is fair or an appropriate solution to the ISP's incessant search for improved efficiency is ultimately up to you.
Friday, February 18, 2011
Either it is or it is not.
Two possible reasons for running across the "error: Error parsing XML: unbound prefix" issue on building your Android app.
1) You have not properly specified an XML namespace for Android to use. Fixing this is easy, just add
"
xmlns:android="http://schemas.android.com/apk/res/android"
"
immediately after the opening of the first LinearLayout tag at the top of your document. This will allow the interpreter to parse the rest of your document and recognize the android: properties.
2) You have an error in your XML that is very likely a spelling mistake. When I was searching for this I was confused because it repeatedly specified the opening of the XML tag which was on a seperate line from the actual misspelling. I had to go down three lines to where I had specified andriod:id rather than android:id.
Hopefully this helps someone! :)
1) You have not properly specified an XML namespace for Android to use. Fixing this is easy, just add
"
xmlns:android="http://schemas.android.com/apk/res/android"
"
immediately after the opening of the first LinearLayout tag at the top of your document. This will allow the interpreter to parse the rest of your document and recognize the android: properties.
2) You have an error in your XML that is very likely a spelling mistake. When I was searching for this I was confused because it repeatedly specified the opening of the XML tag which was on a seperate line from the actual misspelling. I had to go down three lines to where I had specified andriod:id rather than android:id.
Hopefully this helps someone! :)
Thursday, December 23, 2010
At least someone reported on the real Wikileaks story
http://www.theregister.co.uk/2010/12/23/wikileaks_and_data_theft/
I read somewhere that it was likely the communication channels opened after 9/11 that enabled this security atrocity. Kudos to "the media" though for overlooking this blatantly obvious and genuinely interesting story of security officers unconcerned with the well-being of either their own soldiers or Iraqi civilians (see this chat transcript for more).
The amazing thing is this lasted for months! Wired published that article on June 10, 2010 and El Reg (I hope they don't mind me calling them that) has only JUST reported on it. I don't know that I would call this a conspiracy but I have a hard time believing that this was just conveniently "missed."
Although perhaps I give them too much credit. After all, this wasn't even reported on in such a security conscious manner until 6+ months later when someone gave a report sounding the China/cyberwarfare alarm.
I read somewhere that it was likely the communication channels opened after 9/11 that enabled this security atrocity. Kudos to "the media" though for overlooking this blatantly obvious and genuinely interesting story of security officers unconcerned with the well-being of either their own soldiers or Iraqi civilians (see this chat transcript for more).
The amazing thing is this lasted for months! Wired published that article on June 10, 2010 and El Reg (I hope they don't mind me calling them that) has only JUST reported on it. I don't know that I would call this a conspiracy but I have a hard time believing that this was just conveniently "missed."
Although perhaps I give them too much credit. After all, this wasn't even reported on in such a security conscious manner until 6+ months later when someone gave a report sounding the China/cyberwarfare alarm.
Subscribe to:
Posts (Atom)