I was trying to come up with a way to essentially obfuscate the mp3, while still leaving it as a valid mp3. Rearranging the frames (even just swapping every other frame) could yield a valid, although scrambled, mp3.
You could use PGP to encrypt the mp3, sure, but whose key will you use? It would also no longer be an MP3, even if you stuck an mp3 header on the front.
Freenet is interesting, but I have no compelling reasons to use it myself. Same with the new napster.
This is not an md5, this is spectral analysis "fingerprint" of the song. Thus they can identify the song no matter what the encoding (within reason, of course, but you wouldn't want to listen to a song so badly encoded that it can no longer be recognized anyway).
See http://musicbrainz.org/ for some software that uses the same technology to help you tag your MP3s.
I'm sure someone will come up with some software that, say, rearranges the MP3 frames of a song, foiling the fingerprinting but allowing the song to be restored on the other end..
How? Do they have solid-state antennas that can dynamically and instantly aim themselves 360 degrees horizontally, and however many degrees vertically? I wouldn't want to wait for an antenna in my car to find the station every time I turn a corner or go up a hill.
FWIW, I've had a Radeon 9700 Pro since December '02 and I love it. Used to be an nVidia guy, but I haven't looked back since. I was a bit worried about ATI's drivers, but the Catalyst series have been great.
This really has nothing to do with anything, but I sat through a meeting once (don't tell me this is routine, once was bad enough) where the presenter showed a powerpoint slide with one point per slide, and just read the slides, clicking through, complete with obligatory fades and random squeaky/laughing/clapping noises. It really was horrendous.
My understanding of this is that the Zion army or whatever went up to attack the diggers, but an EMP went off early and disabled most of the Zion guys before they could attack... so the diggers slaughtered the army that was sent out, not Zion itself.
I figured you weren't serious, but it's still worrying that they could arrange everything so that even the traces handling the secure data are inaccessible. It'd be neat doing a man-in-the-middle attack on your own motherboard, though.:)
I dunno, those are going to be awfully small wires, and motherboards have multiple layers... what's to stop them from putting the "secure" traces inside the board?
I emailed the webmaster of the site requesting a BitTorrent link, hopefully they provide one. Anyone else able to put one up? The servers are going to be totally swamped.
As far as I know,/dev/random gathers real entropy data from events occuring around the system - incoming network activity, keyboard strokes, mouse movement, etc.../dev/urandom, however, is a traditional prng, and not actually random. This allows it to be much faster, but/dev/random would supposedly be truly random.
You'd use/dev/random for generating random data for, say, generating a key.. but/dev/urandom would suffice (and be far, far faster) for wiping data off a drive (cat/dev/urandom >/dev/hda).
I was under the impression that the problem with a system like you described, is that after a geiger counter detects one event, there's a short period of time during which it's unable to detect another. That limits the entropy of the events and the speed at which you can pull random data from it.
I don't think earplugs would block it. It sounds like the sound is transmitted using hypersonic frequencies, and only becomes audible once it hits something, like.. your head. From there, bone transmission takes over, and plugging your ears won't do a thing.
The flip side of the native-resolution thing is that, despite non-native resolutions looking less than optimal, the native resolution looks amazing. A pixel on a CRT is an amorphous blob that blends into the pixels nearby, whereas a pixel on an LCD is a physical object with physical edges, making for extremely sharp and well-defined images.
Slashdot Mirror
I was trying to come up with a way to essentially obfuscate the mp3, while still leaving it as a valid mp3. Rearranging the frames (even just swapping every other frame) could yield a valid, although scrambled, mp3.
You could use PGP to encrypt the mp3, sure, but whose key will you use? It would also no longer be an MP3, even if you stuck an mp3 header on the front.
Freenet is interesting, but I have no compelling reasons to use it myself. Same with the new napster.
This is not an md5, this is spectral analysis "fingerprint" of the song. Thus they can identify the song no matter what the encoding (within reason, of course, but you wouldn't want to listen to a song so badly encoded that it can no longer be recognized anyway).
See http://musicbrainz.org/ for some software that uses the same technology to help you tag your MP3s.
I'm sure someone will come up with some software that, say, rearranges the MP3 frames of a song, foiling the fingerprinting but allowing the song to be restored on the other end..
Yeah, but who eats matresses, anyway?
Ten centimeters? Seriously? That's almost useless.
How? Do they have solid-state antennas that can dynamically and instantly aim themselves 360 degrees horizontally, and however many degrees vertically? I wouldn't want to wait for an antenna in my car to find the station every time I turn a corner or go up a hill.
Do you want to have to aim your cell phone? Reorient your radio every time you change stations? What about in your car?
FWIW, I've had a Radeon 9700 Pro since December '02 and I love it. Used to be an nVidia guy, but I haven't looked back since. I was a bit worried about ATI's drivers, but the Catalyst series have been great.
If you're behind a NAT router or other firewall, you should forward tcp ports 6881-6889. It makes a night-and-day difference.
They're referring to IE6 SP1 as a version number, like Mozilla 1.4 RC1. They aren't referring to the service pack itself.
And yes, they will abandon older versions of Windows. Do they still support Windows 3.1?
This really has nothing to do with anything, but I sat through a meeting once (don't tell me this is routine, once was bad enough) where the presenter showed a powerpoint slide with one point per slide, and just read the slides, clicking through, complete with obligatory fades and random squeaky/laughing/clapping noises. It really was horrendous.
My understanding of this is that the Zion army or whatever went up to attack the diggers, but an EMP went off early and disabled most of the Zion guys before they could attack... so the diggers slaughtered the army that was sent out, not Zion itself.
I figured you weren't serious, but it's still worrying that they could arrange everything so that even the traces handling the secure data are inaccessible. It'd be neat doing a man-in-the-middle attack on your own motherboard, though. :)
I dunno, those are going to be awfully small wires, and motherboards have multiple layers... what's to stop them from putting the "secure" traces inside the board?
They had to depend on the Catholic Church to "interpret" it for them.
And now DVDs are encrypted, illegal to decrypt, and have to be "interpreted" by a licensed player... and that's just the beginning.
The... emergency chimney? Like, in case a fire just happens to spring up under the carefully-placed emergency chimney? :)
Those are probably 140HP Honda Civics with coffee can exhausts and 3' high spoilers..
I emailed the webmaster of the site requesting a BitTorrent link, hopefully they provide one. Anyone else able to put one up? The servers are going to be totally swamped.
I doubt Coca-Cola would bring a lawsuit against you if you analyzed the product in a lab.
As far as I know, /dev/random gathers real entropy data from events occuring around the system - incoming network activity, keyboard strokes, mouse movement, etc... /dev/urandom, however, is a traditional prng, and not actually random. This allows it to be much faster, but /dev/random would supposedly be truly random.
/dev/random for generating random data for, say, generating a key.. but /dev/urandom would suffice (and be far, far faster) for wiping data off a drive (cat /dev/urandom > /dev/hda).
You'd use
I was under the impression that the problem with a system like you described, is that after a geiger counter detects one event, there's a short period of time during which it's unable to detect another. That limits the entropy of the events and the speed at which you can pull random data from it.
Just a thought.
They actually take the time to type google.com.
Or... install the google toolbar. I couldn't be without it, it's too damn useful.
You slip your primary MX records through them, leaving backups for direct access.
...
Lock your mailserver against direct access (only accept mail via MX routing)
So which is it?
I don't think earplugs would block it. It sounds like the sound is transmitted using hypersonic frequencies, and only becomes audible once it hits something, like.. your head. From there, bone transmission takes over, and plugging your ears won't do a thing.
The flip side of the native-resolution thing is that, despite non-native resolutions looking less than optimal, the native resolution looks amazing. A pixel on a CRT is an amorphous blob that blends into the pixels nearby, whereas a pixel on an LCD is a physical object with physical edges, making for extremely sharp and well-defined images.
"It's pretty unlikely any such exploit attempt will get legs."
Worms don't have legs anyway, do they?