Q: What's different about working with vinyl that's different from a CD?
A: The music is alive? For CD, you know the first Super Mario Brothers, he had a square nose. That's what your audio looks like in 16-bit.
And here is a fascinating presentation from Monty Montgomery from Redhat and xiph.org, creator of Ogg Vorbis, blowing that misconception regarding 16-bit out out of the water.
But before it required at least some skill with tools and an understanding of the design. In the future any moron with a 3D Printer and access to the internet could do it. Usually it's the morons we have to be most worried about when it comes to weapons.
I strongly agree that excess code can mean more bugs, I often code in one of the most terse lanugages in existence for that reason. However, in this case, clearly some required defensive code was absent.
If a particular sequence of events is discovered that leads to a bug in the kernal being exposed, by all means push for that kernal bug to be fixed. But in the interim and for added safety, you might also want to hamstring access to that bug in your own code (Chrome in this case). That is my whole point, security does not have to be in one direction only. There isn't a hard requirement that you trust the platform you run on implicitly. I agree that you can't second guess everything that goes to and from the kernal but it's very clearly misplaced trust in this instance.
If we're talking about a kernel call that may allow escalations of privileges and you are not yourself sanity checking what that what's coming from some box on the internet, then fucking yes, be suspicious. You know something about code but seem to know very little about security in the real world. You my friend are the most dangerous kind of programmer around.
You are mistaken. If Chrome allowed a bug in the OS to be exploited via Chrome, both are at fault. Please consider that no OS is secure. That doesn't mean that browser developers should just give up on security.
I do know this. The attack was via Chrome. It may have exploited a bug in Linux underneath, but so does any attack on Windows or MacOSX via browsers. Nice try at being at trolling but you'd be better off over at 4chan.
One consideration is deliverability. An ISP might be really good at handling the mechanics of email but what if that ISP is in China or Russia? If email is coming from a highly trusted source such as Google rather than a relative unknown such Shadycom then it is one of many factors in deciding whether your mail is spammy or not. Your mail might be entirely legitimate, it's just more possible that it won't be treated as such.
This whole issue of trust is one of the reasons that start-ups tend to use Amazon Simple Email Service or Mailchimp to send mails rather than creating their own mail server. At least in the beginning anyway...
Maybe more like "go and boil your bottom you son of a silly person" which is appropriate given that a North Korean nuclear strike against the US has as much chance as a "fart in your general direction".
Given my bandwidth usage, I'd have to pay about $1,000 a month to get what I have now for about $70. I'm not seeing what's "highly disruptive" about that.
When the debt collectors come to take away your computer. I think that would be highly disruptive.:)
If this story had been true it would have been rather ironic. Worlds most famous 'freedom of information' backing organisation finds safe harbour in the worlds most information repressed country.
Slashdot Mirror
As a Scotsman, bing is definitely in my dictionary.
We think of it as a big pile of detritus left over after excavating a mine. Somewhat apt maybe...
And here is a fascinating presentation from Monty Montgomery from Redhat and xiph.org, creator of Ogg Vorbis, blowing that misconception regarding 16-bit out out of the water.
Xiph.Org - Digital Show & Tell
I'm not desperate, just needy.
I didn't say I wasn't a moron. Would you trust me with a gun? I'm waiting to print off my first one so I can put a cap in yo' ass.
But before it required at least some skill with tools and an understanding of the design. In the future any moron with a 3D Printer and access to the internet could do it. Usually it's the morons we have to be most worried about when it comes to weapons.
However, some in the Jedi organization are not happy about it
I strongly agree that excess code can mean more bugs, I often code in one of the most terse lanugages in existence for that reason. However, in this case, clearly some required defensive code was absent.
If a particular sequence of events is discovered that leads to a bug in the kernal being exposed, by all means push for that kernal bug to be fixed. But in the interim and for added safety, you might also want to hamstring access to that bug in your own code (Chrome in this case). That is my whole point, security does not have to be in one direction only. There isn't a hard requirement that you trust the platform you run on implicitly. I agree that you can't second guess everything that goes to and from the kernal but it's very clearly misplaced trust in this instance.
If we're talking about a kernel call that may allow escalations of privileges and you are not yourself sanity checking what that what's coming from some box on the internet, then fucking yes, be suspicious. You know something about code but seem to know very little about security in the real world. You my friend are the most dangerous kind of programmer around.
You are mistaken. If Chrome allowed a bug in the OS to be exploited via Chrome, both are at fault. Please consider that no OS is secure. That doesn't mean that browser developers should just give up on security.
Are you saying they didn't also patch Chrome?
I do know this. The attack was via Chrome. It may have exploited a bug in Linux underneath, but so does any attack on Windows or MacOSX via browsers. Nice try at being at trolling but you'd be better off over at 4chan.
Wasn't it both? They're both a component in the same vector.
One consideration is deliverability. An ISP might be really good at handling the mechanics of email but what if that ISP is in China or Russia? If email is coming from a highly trusted source such as Google rather than a relative unknown such Shadycom then it is one of many factors in deciding whether your mail is spammy or not. Your mail might be entirely legitimate, it's just more possible that it won't be treated as such.
This whole issue of trust is one of the reasons that start-ups tend to use Amazon Simple Email Service or Mailchimp to send mails rather than creating their own mail server. At least in the beginning anyway...
Yes, 640k ought to be enough for anyone.
I suppose NASA can use this to make it look like the astronauts weren't on the grassy knoll. Oh wait, I'm getting my conspiracies mixed up...
Use headphones with whitenoise. Something like a waterfall
Wizard of Oz 2: Dorothy's Road Trip
Dorothy: Toto, I've a feeling we're not in Kansas City any more.
Toto: Dude, we totally still are...
17-18 months is about the time it takes before you absolutely have to reinstall windows again. :)
Maybe more like "go and boil your bottom you son of a silly person" which is appropriate given that a North Korean nuclear strike against the US has as much chance as a "fart in your general direction".
When the debt collectors come to take away your computer. I think that would be highly disruptive. :)
Who cares, it's good news for you AC!
The Pirate Party provides the bandwidth for Wikileaks.
If this story had been true it would have been rather ironic. Worlds most famous 'freedom of information' backing organisation finds safe harbour in the worlds most information repressed country.
Only if you include some par2 files...
You might want to get that looked at ma'am.