he personal information, Microsoft said, will be stored in a secure, encrypted database.
Its said that if you think encryption is the solution to your problem you don't understand your problem. Where are they going to put the access keys? How will they authenticate users? What does encryption have to do with any of this, anyway? I think they have bigger challenges, like actually enforcing access control.
We have been told that the thief was apprehended by LAPD and the FBI with the help of a member of the online press that had been offered the stolen property.
Why the heck was the FBI involved? Oh yeah, someone with money.
Is it just me is this really just pissing and moaning by a jilted developer? As I see it, the main problem he has is that Sun ignored his code and all his effort and then rubbed salt in the wound by announcing they were going to write a solver program themselves.
I know he put a lot of effort into it and he had but it wasn't working that great anyway. Was it even accurate? Not to disparage his competence but is he complaining about the LGPL license or being ignored?
It's a little bit more subtle than that. Here is a simple example: there could be a section of the file that is supposed to be 100 bytes long, null terminated. The program could read it in but some joker put 200 bytes and a null there instead and the program dutifly reads all 200 bytes into a 100 byte buffer. If the size isn't checked you could overflow the stack, overwrite the return pointer, and cause the function that read the bytes return execution into some bits of code that are storred in the buffer. Think of it as hijacking the execution process.
Most media readers don't actually execute the media.
Well, except for the embedded URL feature in Windows media... and Flash ActionScript... and...
You may want to consider something besides full text searching (Google and company) as this usually starts to degrade fairly quickly with the size of the documents. So far I have not seen anything that actually comes close to human index documents. There are several tools that help users tie documents into a pre-build taxonomy or thesaurus so you get consistency, accuracy, and a *well designed* solution, not random machine learning grouped results. They usually cost money, though so be prepared.
I think that Lucine has a taxonomy module that is in beta mode so that really helps. Automated categorization is still quite terrible so you will need to sit a few users down and have them tag the data. You will be much happier with the result, honestly.
Unless of course calls are free and unlimited. I for one wouldn't mind dialing then getting a cup of coffee while an auto insurance jingle played if it would mean free long distance.
Slashdot Mirror
Only if she does it right.
But I saw a screen shot! Its gotta be true.
he personal information, Microsoft said, will be stored in a secure, encrypted database.
Its said that if you think encryption is the solution to your problem you don't understand your problem. Where are they going to put the access keys? How will they authenticate users? What does encryption have to do with any of this, anyway? I think they have bigger challenges, like actually enforcing access control.
What, read the article? I'm confused. Isn't this /. ?
Why does crap like this make it to the front page of Slashdot?
Because there is only one page...
"encryption bypass" ?
That basically turns the entire thing into a physiological magic trick.
I noticed that as well. They hem and haw but never say it is open source. When they put the kid in the straight jacket they forgot the gag!
I'm just wondering why they would care. Aren't they busy fighting child porn?
Why the heck was the FBI involved? Oh yeah, someone with money.
Is it just me is this really just pissing and moaning by a jilted developer? As I see it, the main problem he has is that Sun ignored his code and all his effort and then rubbed salt in the wound by announcing they were going to write a solver program themselves.
I know he put a lot of effort into it and he had but it wasn't working that great anyway. Was it even accurate? Not to disparage his competence but is he complaining about the LGPL license or being ignored?
It's a little bit more subtle than that. Here is a simple example: there could be a section of the file that is supposed to be 100 bytes long, null terminated. The program could read it in but some joker put 200 bytes and a null there instead and the program dutifly reads all 200 bytes into a 100 byte buffer. If the size isn't checked you could overflow the stack, overwrite the return pointer, and cause the function that read the bytes return execution into some bits of code that are storred in the buffer. Think of it as hijacking the execution process.
Most media readers don't actually execute the media.
Well, except for the embedded URL feature in Windows media... and Flash ActionScript... and...
Oh dear.
You may want to consider something besides full text searching (Google and company) as this usually starts to degrade fairly quickly with the size of the documents. So far I have not seen anything that actually comes close to human index documents. There are several tools that help users tie documents into a pre-build taxonomy or thesaurus so you get consistency, accuracy, and a *well designed* solution, not random machine learning grouped results. They usually cost money, though so be prepared. I think that Lucine has a taxonomy module that is in beta mode so that really helps. Automated categorization is still quite terrible so you will need to sit a few users down and have them tag the data. You will be much happier with the result, honestly.
So if I wanted to vote for Estonia's Res Publica party I would just txt I VT 4 RPub PLZ FTW to 18 00 U2 CAN VOTE?
Publish more, think less. It's what everyone else does.
Unless of course calls are free and unlimited. I for one wouldn't mind dialing then getting a cup of coffee while an auto insurance jingle played if it would mean free long distance.
So the coolaid people actually had it right, they were just off by a few years.