That does not make systems secure. It makes them less buggy. Not all security breaches are due to silly things like buffer overflows. Higher level issues like properly managing who has access to what are involved, too. Things like lost laptops that don't have everything (and I mean EVERYTHING), encrypted, are part of the problem. Security is not about just bug free code... it's the process of how you do everything.
Now if only they could do that with a programming language that doesn't suck.
There should have been a period of time to do the notifications with the DNS running "normally". At the end of that (no extension), change the DNS servers so they return an IP for ALL domains that directs everything to a single page that tells them that their computers and/or network is infected, and they need to contact a security consultant, their ISP, or a specified contact at the FBI. After that time, the DNS should go dead (route those IPs into a blackhole). That all should have been overwith by now. There's no justification to delay further for stupid people.
... send them some encrypted kiddie porn and tell them it's a new game if they can figure out how to crack it. Then call the cops and say this guy had something really vile showing on his phone screen.
It's the scale of the thing. Far far more people want to go than there are tickets/space. Google needs to hire out a football field plus its parking lot. Hell... BUILD a football field complete with server farms under the stands.
I would think Google would want to base the tickets on how active people are on Google+ and how INactive they are on Facebook (no doubt they have a way to track that down). Yeah, I'd even use Google+ for some swag.
The HDTV market has made "attractor wells" in the pricing curves. 1920x1080 panels are way cheaper than 1920x1200. That and many people do want an exact 16x9 monitor so it can view 16x9 video without black bars or lost pixels and at the correct aspect ratio.
The HDTV market drove down panel prices in certain specific sizes, like 1920x1080. Other sizes around those remained expensive because fewer manufacturers wanted to do those. So even 1920x1200 is a big jump in price. When UDTV comes out, then it will probably give us 4096x1728 (cinema 4K) and maybe one common scaled down size of that.
That doesn't necessarily mean final acceptance and payment tendered. Maybe that is the case. But in many contracts like this, there's a live test phase clause, too.
Improper caching could have happened if the URLs were not unique. But caching in this case is just so wrong. And rarely is it even right. Static data can simply be preloaded in a server as streamlined as a cache would be, and those get delivered at cache speeds. Dynamic data should not be cached except in the browser, and even that with a short expire (5 minutes max).
Slashdot Mirror
That does not make systems secure. It makes them less buggy. Not all security breaches are due to silly things like buffer overflows. Higher level issues like properly managing who has access to what are involved, too. Things like lost laptops that don't have everything (and I mean EVERYTHING), encrypted, are part of the problem. Security is not about just bug free code ... it's the process of how you do everything.
Now if only they could do that with a programming language that doesn't suck.
Do you know where your data is?
... since Congress could have put exceptions in the law for them, but did not.
There should have been a period of time to do the notifications with the DNS running "normally". At the end of that (no extension), change the DNS servers so they return an IP for ALL domains that directs everything to a single page that tells them that their computers and/or network is infected, and they need to contact a security consultant, their ISP, or a specified contact at the FBI. After that time, the DNS should go dead (route those IPs into a blackhole). That all should have been overwith by now. There's no justification to delay further for stupid people.
... send them some encrypted kiddie porn and tell them it's a new game if they can figure out how to crack it. Then call the cops and say this guy had something really vile showing on his phone screen.
It's the scale of the thing. Far far more people want to go than there are tickets/space. Google needs to hire out a football field plus its parking lot. Hell ... BUILD a football field complete with server farms under the stands.
Buy it in the name of a legitimate company prefixed with "designated employeee of".
OMG! That means there's going to be an influx of 488 people trying to join Google+ in the same month!
You and me ... we can start our own company ... hire smart people that hate the advertising model. Anonymous Cowards, Inc.
I would think Google would want to base the tickets on how active people are on Google+ and how INactive they are on Facebook (no doubt they have a way to track that down). Yeah, I'd even use Google+ for some swag.
So just go to a judge and have your name legally changed to "Anonymous Coward".
Apparently Google wants hackers to attend this year.
And don't forget "Anonymous Coward".
Let the queued buyers click an option to offer to pay the added processing cost.
Remember, the colonies revolted and don't have this problem.
So when will Slashdot be on IPv6? Inquiring minds and nefarious hackers want to know.
I just use SSH to make my VPN. See the -w option.
The HDTV market has made "attractor wells" in the pricing curves. 1920x1080 panels are way cheaper than 1920x1200. That and many people do want an exact 16x9 monitor so it can view 16x9 video without black bars or lost pixels and at the correct aspect ratio.
The HDTV market drove down panel prices in certain specific sizes, like 1920x1080. Other sizes around those remained expensive because fewer manufacturers wanted to do those. So even 1920x1200 is a big jump in price. When UDTV comes out, then it will probably give us 4096x1728 (cinema 4K) and maybe one common scaled down size of that.
Just because it has been around for a while does not make it the best way. It's simpler to just give the numbers, like in 1920x1200.
What's that big hole across the top front? I hope it's an SD/SDHC/SDXC slot.
All the URLs look alike because the login ID is in cookies, and the cache wasn't set to figure in the cookie state.
That doesn't necessarily mean final acceptance and payment tendered. Maybe that is the case. But in many contracts like this, there's a live test phase clause, too.
Improper caching could have happened if the URLs were not unique. But caching in this case is just so wrong. And rarely is it even right. Static data can simply be preloaded in a server as streamlined as a cache would be, and those get delivered at cache speeds. Dynamic data should not be cached except in the browser, and even that with a short expire (5 minutes max).
Slap together some web system pieces without considering what goes with what, and charge a naive socialist government $200 million for it.