This is "news for nerds", not "I can't believe it's not gmail".
I had set my Slashdot options tuned down until I had a nice clean low-graphics high-content interface with a minimum of surprising keystroke stealing. Every update to Slashdot has made it mankier and flakier. How about a Slashdot lite classic mode that backs things up to about 2002 or so?
Instead of the key being stored in the low bits of N random data files and X registry keys, it's stored in something like the unused bits of N+X opcodes in the executable, or the order of M library routines, or something similar. They still have to keep all the same code in place to make sure you haven't patched the executable or patched the code that extracts the key to authenticate with the server, so it will still freak out if you're using some display tweak that patches the kernel, and you'll still be boned if your account is compromised, and you'll still have to buy the White Album again when they get tired of maintaining the authentication servers for the old versions of the game,... all the same problems that any other DRM scheme has.
All they're doing is embedding the cryptographic token in the executable code instead of a hidden magic file or key.
I can think of half a dozen approaches they could be using, but they all end up in the same place... the program starts up, examines its code in memory, extracts some kind of loader-independent key (eg, a checksum of specific code segments) that gets exchanged with the server to validate the account.
They will still need the same background anti-cheating software (so-called rootkits), because eventually people will figure out the token and patch the extraction code, and they'll be back where they started.
They said that the rough surface of the palladium on the electrode focuses the energy into small pits, where it can be transferred to a single electron. The high-energy electron can then shoot into the nucleus of a nearby deuterium atom and combine with a proton to release a neutron and a neutrino (European Physical Journal C, DOI: 10.1140/epjc/s2006-02479-8).
"Electrons and protons don't have trouble attracting," Widom told New Scientist, and he says the explanation conforms to the Standard Model of particle physics. He speculates that this theory could explain instances of exploding laptop batteries, and could be harnessed as an energy source - something Larsen's company hopes to commercialise.
Nuclear laptop battery explosions? And that wasn't in the Slashdot summary? You're slipping!
Oh no doubt there's people who really really like Apple's hardware, or who buy it for the logo, but most people are more interested in software that actually doesn't suck.
The record companies should experiment with sponsoring free, legal download sites in good faith. These sites would feature:
1) works of expired copyright 2) works from amateurs, fledgling professionals, and "past market prime" professionals 3) promotional works from professional artists, including items such as concert tapes 4) promotional works from the record industry, which would compensate the artists for giving away certain material 5) works from professionals who believe in sharing everything 6) works from specialized pros (like many classical musicians) who couldn't make money from selling records anyway
Kirk McKusick spent a lot of time working out the right order to write metadata and file data in FFS and the resulting file system, FFS with Soft Updates, gets high performance and high reliability... even after a crash.
The real solution is going to be when the OS (which knows what that data really means, which is file and which is metadata and which is cache and backing store) and not the flash controller does all the wear leveling and block erasing, bypassing the flash controller as much as possible. Which is going to require new APIs and interfaces.
Aha, I just tested this on my Mac and it's apparently gotten bit by a change in termcap/terminfo in the past 25 or so years... padding used to be handled by a number at the beginning of a capability, and now it's handled by a '$' inline sequence. The lameness filter is refusing to let me post the patch. Hey, it's source code, you goons. Sheesh.
Ah, a classic hack... variations of this date back to the '70s. I wrote one around 1980, and I'm sure I wasn't the first. A few years back I was googling around and came across it:
This is a fixed version. There was one bug in the original... the timer to slow the update down didn't work, but since a high speed display back then was 9600 baud I'd never noticed.
Slashdot Mirror
You want a "chick magnet", you get a Porsche or a trendy exotic pet, not a laptop. Sheesh.
This is "news for nerds", not "I can't believe it's not gmail".
I had set my Slashdot options tuned down until I had a nice clean low-graphics high-content interface with a minimum of surprising keystroke stealing. Every update to Slashdot has made it mankier and flakier. How about a Slashdot lite classic mode that backs things up to about 2002 or so?
Attacking Microsoft on its own ground is rarely a good strategy, otherwise we'd all be using fvwm95.
Does slashdot ever correct obviously wrong stories like this?
If it wasn't the RIAA, I'd say something like "Unbelievable!".
"That word, you keep using that word. I don't think it means what you think it means."
"Considering the severity..." of having moderately concentrated *ibuprofen*?
Jesus Christ on a crutch... someone needs to whack those people with a clue stick.
Instead of the key being stored in the low bits of N random data files and X registry keys, it's stored in something like the unused bits of N+X opcodes in the executable, or the order of M library routines, or something similar. They still have to keep all the same code in place to make sure you haven't patched the executable or patched the code that extracts the key to authenticate with the server, so it will still freak out if you're using some display tweak that patches the kernel, and you'll still be boned if your account is compromised, and you'll still have to buy the White Album again when they get tired of maintaining the authentication servers for the old versions of the game, ... all the same problems that any other DRM scheme has.
What's the advantage?
All they're doing is embedding the cryptographic token in the executable code instead of a hidden magic file or key.
I can think of half a dozen approaches they could be using, but they all end up in the same place... the program starts up, examines its code in memory, extracts some kind of loader-independent key (eg, a checksum of specific code segments) that gets exchanged with the server to validate the account.
They will still need the same background anti-cheating software (so-called rootkits), because eventually people will figure out the token and patch the extraction code, and they'll be back where they started.
maybe the astronauts will cut off the beginning and just call it the Bert module
The next module has to be "Ernie".
Are they seriously basing all their conclusions on the presence of one neutron track?
No.
One is a small number, true, but honestly...?
Nuclear laptop battery explosions? And that wasn't in the Slashdot summary? You're slipping!
You guys believed O when he said his administration would be the transparent and free of conflict of interest?
Compared to Bush and Cheney? He'd have to be from North Korea to beat that record of secrecy and corruption.
I have been using my handheld as a universal remote for the last 8 years. Slashdot is catching up.
More seriously, until smartphones get down to $60 or so, they're not going to be really cost effective "universal remotes".
Oh no doubt there's people who really really like Apple's hardware, or who buy it for the logo, but most people are more interested in software that actually doesn't suck.
Full detail and pictures are available from the sponsor, TippingPoint, who acquired all of the exploits through their Zero Day Initiative program.
I see no details here.
The record companies should experiment with sponsoring free, legal download sites in good faith. These sites would feature:
1) works of expired copyright
2) works from amateurs, fledgling professionals, and "past market prime" professionals
3) promotional works from professional artists, including items such as concert tapes
4) promotional works from the record industry, which would compensate the artists for giving away certain material
5) works from professionals who believe in sharing everything
6) works from specialized pros (like many classical musicians) who couldn't make money from selling records anyway
That already happened (just a few examples):
1. http://www.trachtman.org/rollscans/RollListing.php
2. http://garageband.com/
3. http://3hive.com/
4. http://www.apple.com/itunes/freesingle
5. http://last.fm/
6. http://www.classiccat.net/
You're just encouraging them.
So long as it's still got ActiveX in there, I gotta consider it "not acceptable".
Kirk McKusick spent a lot of time working out the right order to write metadata and file data in FFS and the resulting file system, FFS with Soft Updates, gets high performance and high reliability... even after a crash.
The real solution is going to be when the OS (which knows what that data really means, which is file and which is metadata and which is cache and backing store) and not the flash controller does all the wear leveling and block erasing, bypassing the flash controller as much as possible. Which is going to require new APIs and interfaces.
No, no, firefox is part of the precipitate too.
I don't think that's part of the solution.
In fact, if you put a boat in a goat, pretty soon you're going to have a bunch of precipitate to deal with.
You're free to port it to work under mass:werk termlib but I'm not feeling adventurous enough for that.
Aha, I just tested this on my Mac and it's apparently gotten bit by a change in termcap/terminfo in the past 25 or so years... padding used to be handled by a number at the beginning of a capability, and now it's handled by a '$' inline sequence. The lameness filter is refusing to let me post the patch. Hey, it's source code, you goons. Sheesh.
Ah, a classic hack... variations of this date back to the '70s. I wrote one around 1980, and I'm sure I wasn't the first. A few years back I was googling around and came across it:
rot.
This is a fixed version. There was one bug in the original... the timer to slow the update down didn't work, but since a high speed display back then was 9600 baud I'd never noticed.