The one thing I don't like about a thing like that is that whoever is behind the scheme might try to aggregate the "ethics score" into one single value based on their decision matrix with their weight factors.
You will probably hate me for this, but I value people more than trees. To me, "low ecological impact" is least important to me while I care a lot about the labor conditions under which the product was manufactured.
And who would decide and then grade what is ethical and what is not?? What if the only thing a buyer is interested in is product quality and they care not the least about working conditions in El Salvador?
This question deserves both: to be modded up and an answer.
First of all, there are no widely adopted international standards for RFID but there is work on ISO 18000, so it all depends on whether your reader/forger supports a given tag's vendor protocol.
The next problem is that RFID systems can operate at different frequencies, the most common ones are 125KHz - 148KHz, high at 13.56 MHz, UHF 850-915MHz and even at 2.45 GHz in the ISM band.
The tags that will be used in retail at automated checkout counters all have a scheme for preventing tag-collision that occurs when tags respond simultaneously to the reader. In order to hide a $800 digital cam-corder the following would have to happen:
You bring the forger into the store and operate it where it is not in view of the many security cameras staring at you
You research the store for a low price article that matches within tolerance what the cam-corder weighs. What that tolerance is,will be open to your own research. Setting the forger to lowest sensitivity / lowest transmit power you read the RFID data of the low-price article. Make double sure the data you read is from the low-price article and not from one of the thousands of tags surrounding you.
The low-price article may have individual identifying RFID data that must NOT be scanned at the checkout counter, not even after you and maybe your helper have left the store (Remember the security cameras, they could potentially match up your face at the automatic checkout with the article!). Also, again if the RFID data uniquely identifies the article another customer could take it to the automatic checkout and the system could mark the article as already sold in its database meaning you can't purchase it in lieu of the cam-corder. You must disable / destroy the low-price article's RFID tag either physically or with the forger.
You set the forger to the lowest sensitivy / lowest transmit power to read out the RFID data of the cam-corder. Make sure you get the right RFID data because you will be surrounded by tons of RFID tags. (BTW, it may be safer to read out the RFID data of the cam-corder you want one day and maybe have someone else get it the next day, but if you do that then make sure you mark the box some way that you or your helper takes the right cam-corder to the checkout. This may be because each cam-corder may have unique RFID data).
You take the cam-corder to the checkout and flip the forger into forge-mode. The forger monitors the radio communication at the reader forcing the transmission of the low-price article's RFID data utilizing the vendors tag-collision protocol to quiet the cam-corders tag. After transmitting the low-price article RFID data the forger jams the reader making the automatic checkout believe this is the only article being presented for purchase.
Complete the purchase with cash or with credit/debit cards not linked to you.
Cool. I wonder how far along reactos, an effort to clone NT4 is with this:-) Incidentally this is a very cool project and they've completed about 70% of the kernel and most of the userspace is taken from the Wine Project.
Btw... You wanted to wait on mutexes with Linux... Well you can! Kernels >= 2.5.7 have the sys_futex call that wakes up everyone waiting on the value of a certain address to change.
BTW... if you really wanted to show off some really basic VMS features Linux does not (yet) have then how about NT-APCs (Asynchronous System Traps as they're called in VMS) which is code in userspace of the process that initiated the IO that is called when that IO operation has completed. I doubt a lot of apps use them, however.
There are probably a zillion facilities one OS has that another lacks. Take IBM MVS / OS/390/zOS jobs for example. A job in IBM's mainframe OS is a sequence of processes that run in sequence and parallel and the OS takes care of synchronizing them, connect them to the resources (datasets, network resources, etc.) they need and make sure that they run in the correct sequence and wait up on each other.
However there is one thing where the Linux-kernel is ahead and that's where it counts: It's a free highly featured enterprise-ready opensource production quality kernel under constant public review. No kernel-feature can make up for that
Now to get ahead of Microsoft in userspace, yes... I could even live with the OSS community adopting Microsoft DCOM. We already did in a way with Mozilla XPCOM.
Yes.. You're right. David Cutler's kernel is slightly more modern than the Linux/Unix design, but it has a few severe drawbacks:
The kernel behind Windows 2000/2003 is as solid as Linux.
The NT-Kernel is about as solid as the Linux kernel (most of the time it's accelerated 3D drivers that trash both systems). The real question today is, is it as solidly secure as Linux is?? I say it isn't because it has only received scant review outside of Microsoft.
The Win32 threading and synchronisation models are ridiculously powerful compared to *nix, which is precisely what makes it so hard to port a lot of Win32-based software to other platforms. The fact that you can't do a simple operation like "wait for a mutex to be released or a socket to become readable" deserves to be a joke about legacy operating systems, not a persistent reality. At least BSD's kqueue comes close.
Most apps don't need that in the first place and btw, waiting with select() call on a socket works just fine for me, I can poll and I can block on a socket so what more do I want:-). What makes porting Windows-apps extremely painful is mostly all the GUI stuff which has to be redone from scratch if it was written using native Windows calls.
There are many other places in which the *nix kernels show their age compared to the design of Win32 (not to mention MS's ability to maintain a consistent API over 10 years of product developments). 30 year old technology may be "mature", but its not always The Right Thing To Do for the future.
So let's see... guess what I agree with you that there are a lot of things in the NT-Kernel that would be cool to have in Linux.. (and a lot in the overall Linux/BSD/Unix codebase Microsoft stole without giving credit and violating licenses)... but we don't really need it to accomplish our mission.
The real battleground is now definitely in userspace and not anymore in kernelspace. If you ask me what we absolutely need is to adopt a standard in userspace like Microsoft did with COM, their Component Object Model which allows their applications to integrate with another.
We use kParts in KDE, Corba/Bonobo in Gnome, UNO in OOo, XPCOM in Mozilla but a Mozilla-XPCOM component can not be inserted into a kParts container like kMail nor a UNO OOo swriter container. Our components can't really talk to each other like theirs can. If we could offer the same kind of integration, Microsoft calls it OLE, where you could fire up OOo writer and edit an embedded gnumerics spreadsheet, right-click on it and send it on it's way using kmail... If we could do that then we would kick Microsoft's butt on the desktop just as bad as we kicked them out of the server arena.
Too bad that every major OSS project has to invent their own Component Architecture.
Okay. Let's make a deal then: The Government taxes us for the Good things(TM) and we'll tax it for the Bad Things(TM).
Jesus Christ, don't be such a knee-jerk troll!
Where are you on the bridge?? I'm a certified PTS and I'm an Operating SP IX.
Tell you what, $cientology sure is one hell of an evil org but comparing them to the USG is like comparing Lynndie England to Satan.
Why then, pray tell us, why are most of the images off limits to Joe citizen??
I personally wouldn't put a lie like a hoaxed moon-landing beyond the US Government (or any other for that matter). I can't say for sure whether the landing took place on a movie-set or 384,000 miles away. I've seen a lot of people, some of them saying they're image specialists and professional photographers photographers say on the net that the moon pics NASA released back in the 70s are doctored. Who knows, maybe they're just trying to appear important, maybe they're just trying to keep an urban myth alive for the fun of it... But who knows? Maybe the entire moon-landing IS a hoax, maybe it's just another one of the million lies the government tries to shove down our throats. It is also possible that they are only lying in part about the landing. Maybe those pictures were doctored to hide certain details but the landing took place. There is no way you or me could find out what is the truth and what is not, for you would have to trust their classified (and possibly doctored) archives and we all know that the most successfull liar believes his own lies.
While it may be as it may, one thing I do know for a fact: The US Goverment is one of the most secretive, paranoid and deceitful organizations on the planet. They are routined and accomplished liars and most of their lies fly because the greater the lie, the less people believe the US government would lie about it. I don't have to remind any of for example about the Iraqi WMDs that never materialized.
"If you believe they put a man on the moon
Man on the moon
If you believe there's nothing up their sleeve
Then nothing is cool" REM
According to some scientists Mars had a much thicker atmosphere when its magnetic field was still completely up. When Mars's magnetic dynamo died, solar winds carried most of its atmosphere away. The same thing would happen here if the magnetic field would just stop. You can check up on research on the interaction of Mars's magnetic field and it's atmosphere
here
What you want to be able to do, to pin down the identity of a user is not wanted and not appreciated by most people.
People don't like:
Answering marketing questions. If a site asks me twenty questions I can't just randomly click through then I'm not interested. I NEVER answer them truthfully in the first place.
Threats like "Your IP will be logged". To those of you that do stuff like that: FUCK YOU
Address verification (for example CC AVS): Yeah right, so you can send me junkmail.
Credit card: Sure, you can have my credit card number... After all you might like to decide to convert my trial into a full sale because I couldn't afford a lawyer to check out the small print on your site. To those of you that do stuff like that: FUCK YOU!!
Maybe they had a SAM at that site, the same way they protected the
G8 Summit in Genoa...
A 6.5-kilometer no-go zone has been established around Kananaskis Village and three anti-aircraft missile batteries set up, as a last line of defence should a plane evade the CF-18 fighters that are policing a 150-kilometer radius no-fly zone.
Interesting. I wonder to what evil uses a WARLOCK detector could be put to... BTW... a little anecdote from WWII. German aircraft were fitted with elektronik jamming devices as a countermeasure against british radar. This practice was discontinued after a few weeks when the Germans found out that the british were homing in on their jammers. I can imagine, Reichsmarschall Goering was very pissed but let's join a small band of Iraqi "Freedom fighters" in a not so distant future...
Abdul El Hassan: "Kull wahad! There are infidel near! Look at the warlock scanner!"
Hassan El Abdul: "Good! Today brothers paradise awaits us!"
Hmmm... looks like I need to take a closer look at the transmitter. There's something on it, I gotta get closer... What the hell is this?? Damm there is little space in here. Geez I hate working on these things. I wonder what would happen if one of those stupid temp dicks turned on the juice now...
BUZZZZZZZZZZZZZZZZZZZZZZZZZZZZ!! What the FUCK!!!! TURN IT OFF!! BUZZZZZZZZZZZZZZZZZZZ!! OH FUCK!! TURN IT OFF!!!!! TURN IT OFF!!! FUCK THIS HURTS!! BUZZZZZZZZZZZZZZZZZZZZZZZZZ!! ARGGGGHHHH!! BUZZZZZZZZZZ! ARRRGGGHH TURN IT OFF!!.
"Hey sorry dude, we thought you were already down. Hey! Nasty sunburn you got there, next time bring some sun lotion to work!".
Damm! I feel dizzy and nauseaus! Uh oh... I'm gonna throw up. UAAAAAAHHHRGH!! Got it all over my pants. Fuck. Uh oh.. I'm gonna pass out, oh shit...
Where am I?? Why is it dark in here? "Hey! Someone help! Where the hell am I???". "Calm down you're in a hospital" "I can't see! I can't see". "That's because of all the microwave radiation you got. The good news is that there's a 2% chance that you will regain some sort of limited viewing capability but since your eyeballs were literally cooked with microwaves.. tell you the truth, we just don't know right now."
A couple of months later: "Sorry Frank, I know this is really hard to take but you're not alone with this and we caught this one early. Male breast cancer happens to thousands of men each year and the survival rate is just as good as with female breast cancer. If you're lucky we can maybe get around a mastectomy but its still to early to say. What I'm a little more worried about is that lump on your liver I noticed on the other X-ray..." "Geez doc, I already have lung cancer and intestinal cancer, you removed my testicles, you took off both of my legs dammit what's next??". "Frank.. you are one of few TV-dinners that was heated in a microwave and lived to talk about it. What do you expect?"
Last time I checked a couple of days ago a
"T-Hotzone" pass cost EUR 8.00 an hour, that's $9.75 an hour. What's worse, once you've started using the "T-Hotzone" pass the clock doesn't stop ticking when you disconnect from the network.
BTW some select Burger Kings(one I know of in Ingolstadt) offer wireless internet for free, (food/beverage purchase required).
First please work through Mrs. Jones Math Primer. It is never too late to learn basic arithmetic skills.
2 ^(128 - 56) >> 1021. Maybe forward the above link to the Thought Leader too.
Second of all the Keyspace of 3DES is 168 bits (three 56bit keys) ->
2 ^ (168 - 128) > 2 ^ 128. In fact, 3DES's keyspace is 2^40 times as large as that of AES128 and we didn't even start talking initial vectors yet.
HOWEVER a cryptoalgorithm's theoretical security is not determined alone by the length of its key size. An algorithm with even a 1024-bit keyspace might have a weaknesses that allows a cryptanalyst to discover key material after a couple hundred to thousand plaintext/ciphertext pairs. Go read Bruce Schneiers book and read (read but don't post to) sci.crypt.
Thank God for "Thought Leadership". My, how would we be lost without strong "Thought Leadership". Why we would have to think things through for ourselves.
Sorry Mark, but all what you're feeding us is just ahem "Thought Leadership" (I actually like the way this pc term sounds, has a nice ring to it:-) ). You have nothing substantial to back up your claims but a bunch of "thought leading" PDFs.
Anyways, I'm not going to waste a terrible lot of time on this one but anyways...
A couple of things to think about
1. AES > 3DES security-wise. Who says so?? 3DES has been around for DECADES and nobody could put a dent in it. AES has been with us 4 years at best.
2. How are you going to prove to us that your client does not intentionally leak key bits? How are you going to prove the quality of the encryption keys your client and server generates (RNG!!!)??
You're right of course...
find_eligible_task() {
while(currentproc if (currentproc == MAXPROC)
restore_cpustate(currentproc);
aside from that the tasktable hasn't been zeroed out in the initialization routine. I'll fix that in ToyOS Version 0.00000000000000002. I was just a little too upset at that little cur when I released ToyOS Version 0.00000000000000001.
There you are. Open Source: Short release cycles and a community of developers all over the world verifying each other's code.
Regards
In my operating systems class I was learning how to implement stuff that Windows wouldn't have for another three years (yes, I implemented pre-emptive multi-tasking in '92 on x86 hardware, and it wasn't bloody well rocket science).
Heartsurgery is easy: All you need is a blunt knife. Doing something useful like saving someones life by laying a bypass is not.
Implementing preemptive Multitasking is easy. All you need is a loudmouthed CS student. Doing something useful with it like making a formerly cooperatively multitasking OS preemptive is not. (just think of all the device drivers, filesystem, network code that need to be changed).
It is not a matter of:
#define S_WAITING 1 #define S_READY 2
#define MAXPROC 4
struct task { int state; unsigned char cpustate[SCPUSTATE]; }
task1() { while (1) serout ("He mom! Check it out! I did this!\n"); }
task2() { while(1) serout ("You mean I can't use the UART when you are using it?\n"); }
There. Preemptive multitasking more or less. Build your own toy operating system around it. Filling in the assembly code for stuff like dis/enable_interrupts, init_task, save/restore cpu_state etc. I will leave it to the inclined CS student to do that.
Slashdot Mirror
The one thing I don't like about a thing like that is that whoever is behind the scheme might try to aggregate the "ethics score" into one single value based on their decision matrix with their weight factors.
You will probably hate me for this, but I value people more than trees. To me, "low ecological impact" is least important to me while I care a lot about the labor conditions under which the product was manufactured.
Would anyone really want to follow the advise of this 29 year old Baltimore Treehugger who calls himself "Stain" and says
SARS is the best thing that has happened to this planet since ebola virus, it's not qiute as kool, but we need less humans on this earth!!!!!!!!!!!!!!" on what products you can "ethically" buy?
And who would decide and then grade what is ethical and what is not?? What if the only thing a buyer is interested in is product quality and they care not the least about working conditions in El Salvador?
First of all, there are no widely adopted international standards for RFID but there is work on ISO 18000, so it all depends on whether your reader/forger supports a given tag's vendor protocol.
The next problem is that RFID systems can operate at different frequencies, the most common ones are 125KHz - 148KHz, high at 13.56 MHz, UHF 850-915MHz and even at 2.45 GHz in the ISM band.
The tags that will be used in retail at automated checkout counters all have a scheme for preventing tag-collision that occurs when tags respond simultaneously to the reader. In order to hide a $800 digital cam-corder the following would have to happen:
You bring the forger into the store and operate it where it is not in view of the many security cameras staring at you
You research the store for a low price article that matches within tolerance what the cam-corder weighs. What that tolerance is,will be open to your own research. Setting the forger to lowest sensitivity / lowest transmit power you read the RFID data of the low-price article. Make double sure the data you read is from the low-price article and not from one of the thousands of tags surrounding you.
The low-price article may have individual identifying RFID data that must NOT be scanned at the checkout counter, not even after you and maybe your helper have left the store (Remember the security cameras, they could potentially match up your face at the automatic checkout with the article!). Also, again if the RFID data uniquely identifies the article another customer could take it to the automatic checkout and the system could mark the article as already sold in its database meaning you can't purchase it in lieu of the cam-corder. You must disable / destroy the low-price article's RFID tag either physically or with the forger.
You set the forger to the lowest sensitivy / lowest transmit power to read out the RFID data of the cam-corder. Make sure you get the right RFID data because you will be surrounded by tons of RFID tags. (BTW, it may be safer to read out the RFID data of the cam-corder you want one day and maybe have someone else get it the next day, but if you do that then make sure you mark the box some way that you or your helper takes the right cam-corder to the checkout. This may be because each cam-corder may have unique RFID data).
You take the cam-corder to the checkout and flip the forger into forge-mode. The forger monitors the radio communication at the reader forcing the transmission of the low-price article's RFID data utilizing the vendors tag-collision protocol to quiet the cam-corders tag. After transmitting the low-price article RFID data the forger jams the reader making the automatic checkout believe this is the only article being presented for purchase.
Complete the purchase with cash or with credit/debit cards not linked to you.
Cool. I wonder how far along reactos, an effort to clone NT4 is with this :-) Incidentally this is a very cool project and they've completed about 70% of the kernel and most of the userspace is taken from the Wine Project.
/zOS jobs for example. A job in IBM's mainframe OS is a sequence of processes that run in sequence and parallel and the OS takes care of synchronizing them, connect them to the resources (datasets, network resources, etc.) they need and make sure that they run in the correct sequence and wait up on each other.
Btw... You wanted to wait on mutexes with Linux... Well you can! Kernels >= 2.5.7 have the sys_futex call that wakes up everyone waiting on the value of a certain address to change.
BTW... if you really wanted to show off some really basic VMS features Linux does not (yet) have then how about NT-APCs (Asynchronous System Traps as they're called in VMS) which is code in userspace of the process that initiated the IO that is called when that IO operation has completed. I doubt a lot of apps use them, however.
There are probably a zillion facilities one OS has that another lacks. Take IBM MVS / OS/390
However there is one thing where the Linux-kernel is ahead and that's where it counts: It's a free highly featured enterprise-ready opensource production quality kernel under constant public review. No kernel-feature can make up for that
Now to get ahead of Microsoft in userspace, yes... I could even live with the OSS community adopting Microsoft DCOM. We already did in a way with Mozilla XPCOM.
Yes.. You're right. David Cutler's kernel is slightly more modern than the Linux/Unix design, but it has a few severe drawbacks:
:-). What makes porting Windows-apps extremely painful is mostly all the GUI stuff which has to be redone from scratch if it was written using native Windows calls.
The kernel behind Windows 2000/2003 is as solid as Linux.
The NT-Kernel is about as solid as the Linux kernel (most of the time it's accelerated 3D drivers that trash both systems). The real question today is, is it as solidly secure as Linux is?? I say it isn't because it has only received scant review outside of Microsoft.
The Win32 threading and synchronisation models are ridiculously powerful compared to *nix, which is precisely what makes it so hard to port a lot of Win32-based software to other platforms. The fact that you can't do a simple operation like "wait for a mutex to be released or a socket to become readable" deserves to be a joke about legacy operating systems, not a persistent reality. At least BSD's kqueue comes close.
Most apps don't need that in the first place and btw, waiting with select() call on a socket works just fine for me, I can poll and I can block on a socket so what more do I want
There are many other places in which the *nix kernels show their age compared to the design of Win32 (not to mention MS's ability to maintain a consistent API over 10 years of product developments). 30 year old technology may be "mature", but its not always The Right Thing To Do for the future. So let's see... guess what I agree with you that there are a lot of things in the NT-Kernel that would be cool to have in Linux.. (and a lot in the overall Linux/BSD/Unix codebase Microsoft stole without giving credit and violating licenses)... but we don't really need it to accomplish our mission.
The real battleground is now definitely in userspace and not anymore in kernelspace. If you ask me what we absolutely need is to adopt a standard in userspace like Microsoft did with COM, their Component Object Model which allows their applications to integrate with another.
We use kParts in KDE, Corba/Bonobo in Gnome, UNO in OOo, XPCOM in Mozilla but a Mozilla-XPCOM component can not be inserted into a kParts container like kMail nor a UNO OOo swriter container. Our components can't really talk to each other like theirs can. If we could offer the same kind of integration, Microsoft calls it OLE, where you could fire up OOo writer and edit an embedded gnumerics spreadsheet, right-click on it and send it on it's way using kmail... If we could do that then we would kick Microsoft's butt on the desktop just as bad as we kicked them out of the server arena.
Too bad that every major OSS project has to invent their own Component Architecture.
I already did :-) :-) :-)
I just read: "The Antichrist in the Libray"...
To bad this article is about some book instead of a bunch of die-hard christians protesting Harry Potter.
Okay. Let's make a deal then: The Government taxes us for the Good things(TM) and we'll tax it for the Bad Things(TM). Jesus Christ, don't be such a knee-jerk troll!
Where are you on the bridge?? I'm a certified PTS and I'm an Operating SP IX. Tell you what, $cientology sure is one hell of an evil org but comparing them to the USG is like comparing Lynndie England to Satan.
Why then, pray tell us, why are most of the images off limits to Joe citizen??
I personally wouldn't put a lie like a hoaxed moon-landing beyond the US Government (or any other for that matter). I can't say for sure whether the landing took place on a movie-set or 384,000 miles away. I've seen a lot of people, some of them saying they're image specialists and professional photographers photographers say on the net that the moon pics NASA released back in the 70s are doctored. Who knows, maybe they're just trying to appear important, maybe they're just trying to keep an urban myth alive for the fun of it... But who knows? Maybe the entire moon-landing IS a hoax, maybe it's just another one of the million lies the government tries to shove down our throats. It is also possible that they are only lying in part about the landing. Maybe those pictures were doctored to hide certain details but the landing took place. There is no way you or me could find out what is the truth and what is not, for you would have to trust their classified (and possibly doctored) archives and we all know that the most successfull liar believes his own lies.
While it may be as it may, one thing I do know for a fact: The US Goverment is one of the most secretive, paranoid and deceitful organizations on the planet. They are routined and accomplished liars and most of their lies fly because the greater the lie, the less people believe the US government would lie about it. I don't have to remind any of for example about the Iraqi WMDs that never materialized.
"If you believe they put a man on the moon Man on the moon If you believe there's nothing up their sleeve Then nothing is cool" REM
According to some scientists Mars had a much thicker atmosphere when its magnetic field was still completely up. When Mars's magnetic dynamo died, solar winds carried most of its atmosphere away. The same thing would happen here if the magnetic field would just stop. You can check up on research on the interaction of Mars's magnetic field and it's atmosphere here
The post about Earth's magnetic field flipping sounds so much more credible.
What you want to be able to do, to pin down the identity of a user is not wanted and not appreciated by most people.
People don't like:
Answering marketing questions. If a site asks me twenty questions I can't just randomly click through then I'm not interested. I NEVER answer them truthfully in the first place.
Threats like "Your IP will be logged". To those of you that do stuff like that: FUCK YOU
Address verification (for example CC AVS): Yeah right, so you can send me junkmail.
Credit card: Sure, you can have my credit card number... After all you might like to decide to convert my trial into a full sale because I couldn't afford a lawyer to check out the small print on your site. To those of you that do stuff like that: FUCK YOU!!
You meant to say, "I for one accept our new free food overloads."
Maybe they had a SAM at that site, the same way they protected the G8 Summit in Genoa...
A 6.5-kilometer no-go zone has been established around Kananaskis Village and three anti-aircraft missile batteries set up, as a last line of defence should a plane evade the CF-18 fighters that are policing a 150-kilometer radius no-fly zone.
Interesting. I wonder to what evil uses a WARLOCK detector could be put to... BTW... a little anecdote from WWII. German aircraft were fitted with elektronik jamming devices as a countermeasure against british radar. This practice was discontinued after a few weeks when the Germans found out that the british were homing in on their jammers. I can imagine, Reichsmarschall Goering was very pissed but let's join a small band of Iraqi "Freedom fighters" in a not so distant future...
Abdul El Hassan: "Kull wahad! There are infidel near! Look at the warlock scanner!" Hassan El Abdul: "Good! Today brothers paradise awaits us!"
Hmmm... looks like I need to take a closer look at the transmitter. There's something on it, I gotta get closer... What the hell is this?? Damm there is little space in here. Geez I hate working on these things. I wonder what would happen if one of those stupid temp dicks turned on the juice now...
:-)
BUZZZZZZZZZZZZZZZZZZZZZZZZZZZZ!! What the FUCK!!!! TURN IT OFF!! BUZZZZZZZZZZZZZZZZZZZ!! OH FUCK!! TURN IT OFF!!!!! TURN IT OFF!!! FUCK THIS HURTS!! BUZZZZZZZZZZZZZZZZZZZZZZZZZ!! ARGGGGHHHH!! BUZZZZZZZZZZ! ARRRGGGHH TURN IT OFF!!.
"Hey sorry dude, we thought you were already down. Hey! Nasty sunburn you got there, next time bring some sun lotion to work!". Damm! I feel dizzy and nauseaus! Uh oh... I'm gonna throw up. UAAAAAAHHHRGH!! Got it all over my pants. Fuck. Uh oh.. I'm gonna pass out, oh shit...
Where am I?? Why is it dark in here? "Hey! Someone help! Where the hell am I???". "Calm down you're in a hospital" "I can't see! I can't see". "That's because of all the microwave radiation you got. The good news is that there's a 2% chance that you will regain some sort of limited viewing capability but since your eyeballs were literally cooked with microwaves.. tell you the truth, we just don't know right now."
A couple of months later: "Sorry Frank, I know this is really hard to take but you're not alone with this and we caught this one early. Male breast cancer happens to thousands of men each year and the survival rate is just as good as with female breast cancer. If you're lucky we can maybe get around a mastectomy but its still to early to say. What I'm a little more worried about is that lump on your liver I noticed on the other X-ray..." "Geez doc, I already have lung cancer and intestinal cancer, you removed my testicles, you took off both of my legs dammit what's next??". "Frank.. you are one of few TV-dinners that was heated in a microwave and lived to talk about it. What do you expect?"
Gory details enough for you??
Last time I checked a couple of days ago a "T-Hotzone" pass cost EUR 8.00 an hour, that's $9.75 an hour. What's worse, once you've started using the "T-Hotzone" pass the clock doesn't stop ticking when you disconnect from the network.
BTW some select Burger Kings(one I know of in Ingolstadt) offer wireless internet for free, (food/beverage purchase required).
Germans voted for Hitler, reluctantly.
First please work through Mrs. Jones Math Primer. It is never too late to learn basic arithmetic skills.
2 ^(128 - 56) >> 1021. Maybe forward the above link to the Thought Leader too.
Second of all the Keyspace of 3DES is 168 bits (three 56bit keys) ->
2 ^ (168 - 128) > 2 ^ 128. In fact, 3DES's keyspace is 2^40 times as large as that of AES128 and we didn't even start talking initial vectors yet.
HOWEVER a cryptoalgorithm's theoretical security is not determined alone by the length of its key size. An algorithm with even a 1024-bit keyspace might have a weaknesses that allows a cryptanalyst to discover key material after a couple hundred to thousand plaintext/ciphertext pairs. Go read Bruce Schneiers book and read (read but don't post to) sci.crypt.
http://.../thought_leadership/white_pa pers/pdf/security.pdf
Thank God for "Thought Leadership". My, how would we be lost without strong "Thought Leadership". Why we would have to think things through for ourselves.
Sorry Mark, but all what you're feeding us is just ahem "Thought Leadership" (I actually like the way this pc term sounds, has a nice ring to it:-) ). You have nothing substantial to back up your claims but a bunch of "thought leading" PDFs.
Anyways, I'm not going to waste a terrible lot of time on this one but anyways...
A couple of things to think about
1. AES > 3DES security-wise. Who says so?? 3DES has been around for DECADES and nobody could put a dent in it. AES has been with us 4 years at best.
2. How are you going to prove to us that your client does not intentionally leak key bits? How are you going to prove the quality of the encryption keys your client and server generates (RNG!!!)??
I'd rather provoke thoughts than "lead them".
If you really wanted to honor the man then this is how he would have written it:
X'52', X'49', X'50'
You're right of course... find_eligible_task() { while(currentproc if (currentproc == MAXPROC) restore_cpustate(currentproc); aside from that the tasktable hasn't been zeroed out in the initialization routine. I'll fix that in ToyOS Version 0.00000000000000002. I was just a little too upset at that little cur when I released ToyOS Version 0.00000000000000001. There you are. Open Source: Short release cycles and a community of developers all over the world verifying each other's code. Regards
there is a bug in find_eligible_task... did you spot it :-) ?
In my operating systems class I was learning how to implement stuff that Windows wouldn't have for another three years (yes, I implemented pre-emptive multi-tasking in '92 on x86 hardware, and it wasn't bloody well rocket science).
I MER_INTERRUPT, scheduler); /* idle */
Heartsurgery is easy: All you need is a blunt knife. Doing something useful like saving someones life by laying a bypass is not.
Implementing preemptive Multitasking is easy. All you need is a loudmouthed CS student. Doing something useful with it like making a formerly cooperatively multitasking OS preemptive is not. (just think of all the device drivers, filesystem, network code that need to be changed).
It is not a matter of:
#define S_WAITING 1
#define S_READY 2
#define MAXPROC 4
struct task {
int state;
unsigned char cpustate[SCPUSTATE];
}
struct task tasktable[MAXPROC];
int currentproc = 0;
disable_interrupts();
set_interrupt_vector(T
program_timer();
init_task(0, NULL);
init_task(1, task1);
init_task(2, task2);
enable_interrupts();
while(1) {
serout ("Idle hands read slashdot");
}
find_eligible_task() {
while(currentproc < maxproc && tasktable[currentproc].state != S_READY)
currentproc++;
if (currentproc == maxprc)
currentproc = 0;
}
scheduler() {
save_current_cpustate(tasktable);
find_eligible_task();
restore_cpustate[currentproc];
}
task1() {
while (1)
serout ("He mom! Check it out! I did this!\n");
}
task2() {
while(1)
serout ("You mean I can't use the UART when you are using it?\n");
}
There. Preemptive multitasking more or less. Build your own toy operating system around it. Filling in the assembly code for stuff like
dis/enable_interrupts, init_task, save/restore cpu_state etc. I will leave it to the inclined CS student to do that.