...The people airing this kind of TV have a responsibility; inspiration. Star Trek has inspired us, and particularly Enterprise, with its superb theme song that tells so much about our struggle to move space travel forward and closer to the public...
And another...
Re:If... (Score:5, Insightful)
by *weasel (174362) Alter Relationship on Wednesday July 16, @01:17PM (#6453327)
IE will continue to be developed and extended by MS army of coders. they're just going to lock the browser major version to the OS and not supply a standalone download. if you're thinking that IE is on feature freeze, you're greatly mistaken.
aside from that, new features and standards are only added by web developers when the critical mass of the target market has access to them. I doubt any 2nd party browser can pick up critical mass to get significant developer support - let alone in the span of time between MS OS releases.
MS just isn't offering IE as a free standalone download. No doubt it's to escape legal backfire from their declaration that it's an integral part of the OS (if it really is - then you can't offer a free download as they do.)
i'm not going to dismiss the possibility that something else might eclipse IE - but i am willing to dismiss the possibility that it'll happen as a result of lack of development and extension by MS.
Re:If... (Score:4, Interesting)
by halo8 (445515) on Wednesday July 16, @01:16PM (#6453315)
your a fool
your a fool to belive that M$ is just sitting back and waiting 2-3 years to release IE 7, right now they have an update ready to go for IE 6.5, and should some "new technologies" come out before the next OS, rest assured that M$ will release a patch with most of the other stuff they were plannig on releasing anywayse.
IE 6.5? Ready to go? Man, we are in 2005 and almost 90% of the internet still uses IE 6.0.
But I guess that would be better than what you guys did there. Bush? 4 more years? Tsc. The world is ruled by the wrong country...
You guys say so much about religious fundamentalism... but you guys re-elected a fundamentalist! What a pity, for the world. Well, you did elect The Terminator. So, I think, we could only expect that coming.
What's next? Stallone for President? What a shame...
Note that as far as I remember, stenography by definition is supposed to make it impossible to prove that there is data hidden there - one step further than normal encryption. It's not so much as about hiding the data as being able to deny its existance. One reason for this is if you have encrypted data on your disk, then courts can demand the password for it. Stenography allows you to insist there is no hidden data.
Overview: Hydan finds sets of equivalent instructions in the binary, and uses that redundancy to embed data. The larger the set of equivalent instructions, the more bits can be embedded. For example, if instructions {a, b, c, d} are all equivalent, then we can embed two bits of information when any of those instructions are encountered.
Embedding: Hydan goes through the application sequentially, and whenever it finds an instruction that it has equivalents to, it substitutes in the instruction that represents the bit(s) of data hydan is currently embedding. A simple example: "add %eax, 50" is equivalent to "sub %eax, -50". So this set is {"add %reg, $imm", "sub %reg, $imm"}. Whenever an instruction of the form "add %reg, $imm" is encountered, hydan can embed one bit of the message. If the bit is 0, it leaves it as an add instruction. Else it substitutes it to "sub %reg, -$imm". (and vice versa)
Decoding: When it is time to extract the embedded message, every "add %reg, $imm" is taken to mean bit 0, and every sub instruction encodes the bit 1, and the embedded message is reconstructed that way.
Encryption: Hydan first prompts the user for a passphrase before embedding or decoding the contents of the application. In the case of embedding, hydan prepends the length of the message to the message, encrypts that with blowfish in cbc mode, and embeds the result into the application. When decoding, hydan extracts all the possible bits from the application (since it does not know how long the message is a-priori; that information is encrypted). Hydan then decrypts the message properly since it is in CBC mode and need not know the total length first. The lenght is then used to truncate the message to size.
Instructions: For a complete list of the sets of equivalent instructions, please refer to hdn_insns.c.
- Attacks ---------
There are three classes of attacks that are applicable to hydan: overwriting, detection, and extraction. The overwriting attack refers to the ability to overwrite the message embedded in the application, whether its presence was detected or not. An attacker should also not be able to detect the presence of a message in the application, nor decrypt it.
The overwriting attack: hydan currently has no means to protect against this type of attack. Since hydan embeds the message sequentially, starting from the top of the application, an attacker could re-run hydan with a bogus text and embed that on top of the original message. The intended recipient of the application would thus be unable to retrieve the original message. One way this could be solved is to add an error correcting code to the encoding of the message, and distribute the message throughout the application in a passphrase specific manner. This way only parts of the original message would be overwritten, and the original may still be reconstructed. Of course, there is nothing that can be done if the attacker insists on overwriting with a message size that is the maximum embeddable in the given application. However, the computation required to overwrite each application on a large scale might be prohibitive enough to discourage this as a routine behaviour, at an ISP for example.
Detection: Binaries produced by hydan should not exhibit obvious patterns. At the most superficial level, this is accomplished by not embedding any marker or other easily recognizable token. At best, the embedded data looks random (which is why it is bf encrypted). At the assembly level however, the current version of hydan makes no attempt at mimicing the original distribution of instructions in the application, and is thus vulnerable to statistical analysis. Indeed, although all the instructions are equivalent, some may appear more frequent
I don't agree with you. My company develops all our cross-platform applications (Linux, *BSDs, OS X and Windows) using wxWidgets and everything works fine.
Far better than QT, if you ask me. No metacompilers, no emulated look and feel and (thank god) no licencing issues.
One compact flash card holds the operating system in a protected write mode, while the other stores a real-time flight log - a 'black box' that can be examined to diagnose problems, even if the vehicle crashes.
This would be very useful to thousands of Windows users world-wide:-D
Ahh! I was missing the joy of accessing slashdot.org and read a FUD SCO story... Feels like the old times:)
Seriously, these guys are nuts. oldSCO was part of the TISC comittee, so Darryl: Kiss bubye to this lawsuit. Nobody will buy your (aham, MS's) company.
Slashdot Mirror
Well, since it was all staged up in Hollywood, I guess every fucking production to date.
From TFA:
...The people airing this kind of TV have a responsibility; inspiration. Star Trek has inspired us, and particularly Enterprise, with its superb theme song that tells so much about our struggle to move space travel forward and closer to the public...
Well. Now I get that theme song thing!
Duh!
http://www.google.com/apis/
And another... Re:If... (Score:5, Insightful) by *weasel (174362) Alter Relationship on Wednesday July 16, @01:17PM (#6453327) IE will continue to be developed and extended by MS army of coders. they're just going to lock the browser major version to the OS and not supply a standalone download. if you're thinking that IE is on feature freeze, you're greatly mistaken.
aside from that, new features and standards are only added by web developers when the critical mass of the target market has access to them. I doubt any 2nd party browser can pick up critical mass to get significant developer support - let alone in the span of time between MS OS releases.
MS just isn't offering IE as a free standalone download. No doubt it's to escape legal backfire from their declaration that it's an integral part of the OS (if it really is - then you can't offer a free download as they do.)
i'm not going to dismiss the possibility that something else might eclipse IE - but i am willing to dismiss the possibility that it'll happen as a result of lack of development and extension by MS.
huahuahuahuahauhauhauha!
From the linked slashdot story:
;)
Re:If... (Score:4, Interesting)
by halo8 (445515) on Wednesday July 16, @01:16PM (#6453315)
your a fool
your a fool to belive that M$ is just sitting back and waiting 2-3 years to release IE 7, right now they have an update ready to go for IE 6.5, and should some "new technologies" come out before the next OS, rest assured that M$ will release a patch with most of the other stuff they were plannig on releasing anywayse.
IE 6.5? Ready to go? Man, we are in 2005 and almost 90% of the internet still uses IE 6.0.
Who's the fool now?
Are you sure? AFAIK, my BIOS is from Phoenix. I will take a look again.
I wonder if it works with my Compaq R3000z. :(
And this click is the sound of my Wil Wheaton bookmark moving from my Picard folder into my Jar Jar Binks Folder :P
;)
Just kidding!
Where did I troll? You americans DID make a mistake. And you will regret it. I just loooove this moderators.
In soviet Russia, Bush re-elects YOU!
But I guess that would be better than what you guys did there. Bush? 4 more years? Tsc. The world is ruled by the wrong country...
You guys say so much about religious fundamentalism... but you guys re-elected a fundamentalist! What a pity, for the world. Well, you did elect The Terminator. So, I think, we could only expect that coming.
What's next? Stallone for President? What a shame...
SHAME ON YOU AMERICA! SHAME ON YOU!
aaaaaarggghhh!!!
I hate the IT design
I hate the IT Design
Hey! This is slashdot! We can mkae all kndis of tipsos around heer!
http://ihatetheitdesign.slashdot.org/article.pl?si d=04/08/13/1317236&tid=103&tid=117&tid=185&tid =98
Note that as far as I remember, stenography by definition is supposed to make it impossible to prove that there is data hidden there - one step further than normal encryption. It's not so much as about hiding the data as being able to deny its existance.
One reason for this is if you have encrypted data on your disk, then courts can demand the password for it. Stenography allows you to insist there is no hidden data.
Since a lot of people is asking, here it goes:
- How it works
--------------
Overview: Hydan finds sets of equivalent instructions in the binary,
and uses that redundancy to embed data. The larger the set of
equivalent instructions, the more bits can be embedded. For example,
if instructions {a, b, c, d} are all equivalent, then we can embed two
bits of information when any of those instructions are encountered.
Embedding: Hydan goes through the application sequentially, and
whenever it finds an instruction that it has equivalents to, it
substitutes in the instruction that represents the bit(s) of data
hydan is currently embedding. A simple example: "add %eax, 50" is
equivalent to "sub %eax, -50". So this set is {"add %reg, $imm", "sub
%reg, $imm"}. Whenever an instruction of the form "add %reg, $imm" is
encountered, hydan can embed one bit of the message. If the bit is 0,
it leaves it as an add instruction. Else it substitutes it to "sub
%reg, -$imm". (and vice versa)
Decoding: When it is time to extract the embedded message, every
"add %reg, $imm" is taken to mean bit 0, and every sub instruction
encodes the bit 1, and the embedded message is reconstructed that way.
Encryption: Hydan first prompts the user for a passphrase before
embedding or decoding the contents of the application. In the case of
embedding, hydan prepends the length of the message to the message,
encrypts that with blowfish in cbc mode, and embeds the result into
the application. When decoding, hydan extracts all the possible bits
from the application (since it does not know how long the message is
a-priori; that information is encrypted). Hydan then decrypts the
message properly since it is in CBC mode and need not know the total
length first. The lenght is then used to truncate the message to
size.
Instructions: For a complete list of the sets of equivalent
instructions, please refer to hdn_insns.c.
- Attacks
---------
There are three classes of attacks that are applicable to hydan:
overwriting, detection, and extraction. The overwriting attack refers
to the ability to overwrite the message embedded in the application,
whether its presence was detected or not. An attacker should also not
be able to detect the presence of a message in the application, nor
decrypt it.
The overwriting attack: hydan currently has no means to protect
against this type of attack. Since hydan embeds the message
sequentially, starting from the top of the application, an attacker
could re-run hydan with a bogus text and embed that on top of the
original message. The intended recipient of the application would
thus be unable to retrieve the original message. One way this could
be solved is to add an error correcting code to the encoding of the
message, and distribute the message throughout the application in a
passphrase specific manner. This way only parts of the original
message would be overwritten, and the original may still be
reconstructed. Of course, there is nothing that can be done if the
attacker insists on overwriting with a message size that is the
maximum embeddable in the given application. However, the computation
required to overwrite each application on a large scale might be
prohibitive enough to discourage this as a routine behaviour, at an
ISP for example.
Detection: Binaries produced by hydan should not exhibit obvious
patterns. At the most superficial level, this is accomplished by not
embedding any marker or other easily recognizable token. At best, the
embedded data looks random (which is why it is bf encrypted). At the
assembly level however, the current version of hydan makes no attempt
at mimicing the original distribution of instructions in the
application, and is thus vulnerable to statistical analysis. Indeed,
although all the instructions are equivalent, some may appear more
frequent
I don't agree with you. My company develops all our cross-platform applications (Linux, *BSDs, OS X and Windows) using wxWidgets and everything works fine.
Far better than QT, if you ask me. No metacompilers, no emulated look and feel and (thank god) no licencing issues.
One compact flash card holds the operating system in a protected write mode, while the other stores a real-time flight log - a 'black box' that can be examined to diagnose problems, even if the vehicle crashes.
:-D
This would be very useful to thousands of Windows users world-wide
Ahh! I was missing the joy of accessing slashdot.org and read a FUD SCO story... Feels like the old times :)
Seriously, these guys are nuts. oldSCO was part of the TISC comittee, so Darryl: Kiss bubye to this lawsuit. Nobody will buy your (aham, MS's) company.
Great stuff. But, is it reliable? This technology is becoming mainstream too quickly.
Does anyone have more data on this?
You forgot the "clippy" jokes... Or... "In Soviet Russia, Microsoft EI-EI-EIOffice you!" or something like. agh. Slashdot is soooo predictable.
hmmm... no.
a beowulf cluster of these!
Don't let those guys (plairfair's and FairTunes' authors) turn WMA into an industry standard.
Information wants to be free... yeah. Give me your credit card numbers then...