But will it work on all OS'es? As far as triple DES encryption is concerned: this could also be done in software, using a simple java applet for instance.
Some smart-card proponents says that doing the encryption in software (rather than on the card) would leave the system open to viruses and trojans, which could draw money from your account/reveal personal details. However, if you think about it, this argument doesn't stand. Even if you have a card reader, with a card that does encryption in hardware, you are still vulnerable to Virii/Trojans, the only difference would be that the Virus/Trojan would attack the clear stream from the keyboard to the card reader instead. And unless you do everything using a small keypad directly attached to the card reader, this vulnerability will stay.
Access to legacy apps which do not yet exist on your chosen desktop platform?
App needs to run on remote computer, because it controls hardware attached to that computer. Granted, today you could use a small webserver on the computer where the hardware sits, and use HTTP for client/server communication, but what if the hardware is closed and legacy, and only ships with an closed-source X app running on SCO?
> The irony is that compression, which is supposed to make the link effectively faster, actually increases the latency for sending short messages.
That would be true if you used a protocol-independant compressor such as ssh. However, the X-compressors (mlview-dxpc, lbx and to a lesser extent, classical dxpc) all know about this issue, and compress "intelligently": they try to cache session states, and satisfy some requests locally from the proxy, thus cutting out round trips. The problem so far has been that dxpc was not very efficient at this, but according to their blurb, mlview-dxpc is much more sophisticated in this regard.
The short summary. Yes, it is possible using various techniques (flexible/segmented sections of monorail beam, beam replacement, etc.).
The page also explains that the "monorails can't switch" myth was due to a particularly bad and bulky implementation at Wuppertal, and that the myth has since been perpetuated by various shady sources such as Microsoft Encarta.
> The Roman Catholic Church to my knowledge doesn't have any secret doctrines.
And what about the Fatima Secrets? Granted, the third secret has been finally revealed to the world recently, but many people think that what has been revealed is far too trivial to be the actual secret...
Constructive criticism? Actually, what granny seems to be doing here is to describe Linux as it used to be 6 years ago (that's a mighty long time in software engineering!), and blindly assume that it hasn't improved one bit. So far, most of the problems described have been addressed one way or another (who still installs from floppy? Who still needs to calculate how much cylinders into his swap partition?), and the rare that may still be current (readability of doc) are so vague as to hardly merit the word "constructive". Does she also criticize Ford just because her Edsel broke down on her when she still was young and beautiful?
> I am using QT 2.2.4 here and it supports accented characters perfectly. Maybe you should check your configs but don't blame QT.
Could your post your config please? I used the qt-2.2.4 rpm that came with the kde 2.1 download for Redhat 6.x . What config files do I need to change to make dead keys work?
> See:éóáû Got it?
Proves nothing. Could have been typed in from another version of qt, or from a non-qt app (such as... netscape)
...will it support dead keys (accented characters, where you first press the accent, then the letter)? So far, this has been on and off for a while. 2.2.2 botched it, 2.2.3 fixed it, 2.2.4 botched it again... Somewhat hard to type French text, if the accents don't work properly.
The Red Hat install was not out of the box. Before performing the test, they made sure to make it slower by tweaking an assorted set of parameters. Samba widelinks and Apache reverse name lookups for the logfile come to mind.
> The clerk/whoever says "$100", pointing to their sticker. *IN PLAIN VIEW*, you pull out a sticker that says "$50" and carefully affix it to the item and say "How about that?"
Or more realistically: somehow the item you bought happens to have no tag at all. And the cashier asks you "do you remember how much it was?". And instead of replying with the correct price, or "sorry, I dunno", you make up a slightly lower one. Don't laugh, there are supermarkets around here which often have those kinds of missing tag problems, and where the clerk first ask the customer before calling out for a "price check"...
Although this is very stupid on the store's part, I doubt though whether it would be legal to lie to the cashier: clearly, the cashier is not proposing a price negotiation, but rather attempting to save his and the customer's time.
> It was really funny, his party didn't win, thank god, but it would have been great to see him run away from that promise.
Which would have been sad for democracy... Hey, the guy wanted to give you as a people more power, and what do you do? You ridicule him for it! "Proving" that the public should not be trusted with serious matters, and that important decisions are best taken in smoke-filled rooms with just politicians and lobbyists present.
Public ridicule should be reserved for laws such as the DMCA, or the British guily-until-proven-innocent key disclosure law, or the new Aussi anti-forwarding laws, but not for laws that give you a voice.
Actually, it doesn't even take a form with a GET request. Rather than use a cookie, many sites now encode a unique user id in the URL,
Well, the point was that cookies allow banner ad sites to snarf form data without the webmaster's consent. That is, Joe Webmaster just knows that www.EvilBanner.com shows banner ads, and that he gets a couple of shiny coins from them at the end of the month, but he completely ignores what else EvilBanner.com does behind his back. I know a guy who was very surprised when I pointed out to him that the valueclick banner on his site was dishing out cookies left and right!
Including identifying info in the URL itself kinda defeats this objective of sneakiness, as it needs active collaboration of the webmaster.
Iframes will probably allow cookies for a short amount of time after browsers fix a similar problem for images
... I also heard someone tell me that some linkexchange ads were at some point in order to allow linkexchange to update the entire banner code whenever they needed to
Actually, the main reason for the script src seems to be the same as for iframes: allow the ad to set cookies, where a simple image couldn't. Just try it in netscape: In Edit->Preferences->Advanced, check the box labeled "Only accept cookies originating from the same server as the page being viewed", and watch how it still lets pass cookies attached to all kinds of includes, such as scriptsrc, iframe etc. Seems only cookies from offsite images are blocked.
Now suppose you place an order on one of these sites and leave your e-mail address and other personal information. The site sells your e-mail address and other personal info to "WebBugsAreEvil.com". I now have your personal information and your cookie, but the cookie ID is not yet associated with your personal information because these were collected by two different servers. I need to do one more thing to put them together.
I do a mass mail out with all the new e-mail addresses. The e-mails are HTML-enabled e-mails. Embedded at the bottom of the e-mail is this web bug:
Actually this extra step of sending a web-bug infested spam is not even needed in most cases. It's enough if the surfer enters his e-mail address into any form on the web which uses the GET method, and which leads to a page having a web bug/banner ad from WebBugsAreEvil.com. The site serving the form does not actually need to be in cahoots with WebBugsAreEvil, apart from the obvious contract for serving its banners. Indeed, with the GET method, form data (containing your E-mail address) will be part of the URL, and thus will be sent to WebBugsAreEvil in the Referer header field. Much more discreet and reliable than sending a webbugged spam, and much more far-reaching too: using the same method, WebBugsAreEvil can collect all kinds of interesting info: First name, last name, home address, all kinds of demographic info such as age, yearly income, hobbies (if user ever participated in a survey having such a form), credit card number (if merchant was foolish enough to have his order form submitted via GET rather than POST). N.B. Even https doesn't protect against this, as this is data that is "intentionnally" sent to WebBugsAreEvil, rather than intercepted...
> The signal first has to travel up to the sat from your house
Depends on the kind of service you have. Many satellite service plans use a "return channel by land line", meaning that any upstream packets (from you to the "Internet") travel via landline (modem, isdn, etc.) and the satellite is only used for downstream packets (from the Internet to you). Makes sense, since most people have higher needs in downloading anyways. Advantage: cuts latency in half. Disadvantage: kills any "flat-rate" like advantage, you still need to pay your phone bill.
> It then has to travel down to a microwave dish in europe, again with more signal losses.
Actually, while the largest satellite operator worldwide is indeed located in Europe, ground stations are spread around the world. And, strangely enough, most signal losses are actually not due to atmospheric conditions, but rather to the fact that the average Microsoft PC cannot keep up with the high transfer rates from satellite, and so has to occasionnally drop a packet or two!
> The round trip in simple distance is probably greater than your 28.2k modem,and hence latency is greater
Indeed, at geostationary altitude, space roundtrip is at 2*36000, which gives you 240msec ping time at least.
Make that 480msec if you use the satellite for upstream too. Add on top of that to that any landline latency ping time.
> If you need any more discouragement to get satellite internet- the bird is probably owned by microsoft.
If you live in Malaysia, your satellite will indeed be (partly) owned by Microsoft. But don't worry, the omnipresent penguins have taken care of that: the platform (groundstation software) runs mostly on Linux!
> Guess you weren't around in the 80's... 5 1/4" diskettes are usually formatted to have 40 tracks, numbered 0-39. But the disk drives can usually seek to track 40 or 41 without a problem.
This still works today, with 3 1/2 floppies. Normally floppies are formatted to 80 tracks (numbered 0 to 79). However, on most drives you can seek to tracks 80, 81 and 82, allowing you to hide data there. In linux, it's just a matter of typing setfdprm/dev/fd0 cyl=83 to have access to the full number of 83 tracks...
These are small, so are perfect for your portable MP3 player that you wear while jogging. A CD-Rom reader would not only be worrysome to carry around while doing sports, it would also skip whenever you shake it a little bit too much.
But what if they tuck it on the main contract (along with the clauses about compensation, your title, etc) : i.e. without signing it, you would not be employed...
> So who knows what's next, considering the IFPI is probably keeping a list of IP's used by Napster users.
This sounds pretty scary. What happens if your ISP uses dynamic IP's, as most ISP's do? Don't assume police would know about dynamic IP's, this is Belgium after all, that we're talking about.
Case in point, in the olden days, if you, as a foreigner, couldn't/wouldn't pay a speeding fine (which could amount to more than $3000) in Belgium, you could get banned from ever entering Belgium again with your car. Infractions against this ban where punished with instant confiscation of the car.
Only trouble: in Belgium, you would keep your license plates when you bought a new car, whereas in all neigboring countries, the license plates stayed with the car. You guessed it: people buying used cars in those neighboring countries then not only needed to worry about getting not a lemon, but also whether it was safe to take that car to Belgium...
Some smart-card proponents says that doing the encryption in software (rather than on the card) would leave the system open to viruses and trojans, which could draw money from your account/reveal personal details. However, if you think about it, this argument doesn't stand. Even if you have a card reader, with a card that does encryption in hardware, you are still vulnerable to Virii/Trojans, the only difference would be that the Virus/Trojan would attack the clear stream from the keyboard to the card reader instead. And unless you do everything using a small keypad directly attached to the card reader, this vulnerability will stay.
<img src="http://www.amazon.com/cgi/oneclick.cgi?book=d ianetics&confirm=no&details=usecookie">
That would be true if you used a protocol-independant compressor such as ssh. However, the X-compressors (mlview-dxpc, lbx and to a lesser extent, classical dxpc) all know about this issue, and compress "intelligently": they try to cache session states, and satisfy some requests locally from the proxy, thus cutting out round trips. The problem so far has been that dxpc was not very efficient at this, but according to their blurb, mlview-dxpc is much more sophisticated in this regard.
The short summary. Yes, it is possible using various techniques (flexible/segmented sections of monorail beam, beam replacement, etc.).
The page also explains that the "monorails can't switch" myth was due to a particularly bad and bulky implementation at Wuppertal, and that the myth has since been perpetuated by various shady sources such as Microsoft Encarta.
But be sure to copy their DB to FreeDB first... or else it would be a karma packback for the community too.
And what about the Fatima Secrets? Granted, the third secret has been finally revealed to the world recently, but many people think that what has been revealed is far too trivial to be the actual secret...
Constructive criticism? Actually, what granny seems to be doing here is to describe Linux as it used to be 6 years ago (that's a mighty long time in software engineering!), and blindly assume that it hasn't improved one bit. So far, most of the problems described have been addressed one way or another (who still installs from floppy? Who still needs to calculate how much cylinders into his swap partition?), and the rare that may still be current (readability of doc) are so vague as to hardly merit the word "constructive". Does she also criticize Ford just because her Edsel broke down on her when she still was young and beautiful?
"It's an annoyance. It's a thorn."
Indeed.
Could your post your config please? I used the qt-2.2.4 rpm that came with the kde 2.1 download for Redhat 6.x . What config files do I need to change to make dead keys work?
> See:éóáû Got it?
Proves nothing. Could have been typed in from another version of qt, or from a non-qt app (such as ... netscape)
Thanks,
...will it support dead keys (accented characters, where you first press the accent, then the letter)? So far, this has been on and off for a while. 2.2.2 botched it, 2.2.3 fixed it, 2.2.4 botched it again... Somewhat hard to type French text, if the accents don't work properly.
The Red Hat install was not out of the box. Before performing the test, they made sure to make it slower by tweaking an assorted set of parameters. Samba widelinks and Apache reverse name lookups for the logfile come to mind.
Nope, that's POST. The PUT method is indeed used for Web publishing, and normally alters the page.
The method about which you are thinking is POST.
Or more realistically: somehow the item you bought happens to have no tag at all. And the cashier asks you "do you remember how much it was?". And instead of replying with the correct price, or "sorry, I dunno", you make up a slightly lower one. Don't laugh, there are supermarkets around here which often have those kinds of missing tag problems, and where the clerk first ask the customer before calling out for a "price check"...
Although this is very stupid on the store's part, I doubt though whether it would be legal to lie to the cashier: clearly, the cashier is not proposing a price negotiation, but rather attempting to save his and the customer's time.
... Cowboy Neal!
Which would have been sad for democracy... Hey, the guy wanted to give you as a people more power, and what do you do? You ridicule him for it! "Proving" that the public should not be trusted with serious matters, and that important decisions are best taken in smoke-filled rooms with just politicians and lobbyists present.
Public ridicule should be reserved for laws such as the DMCA, or the British guily-until-proven-innocent key disclosure law, or the new Aussi anti-forwarding laws, but not for laws that give you a voice.
Well, the point was that cookies allow banner ad sites to snarf form data without the webmaster's consent. That is, Joe Webmaster just knows that www.EvilBanner.com shows banner ads, and that he gets a couple of shiny coins from them at the end of the month, but he completely ignores what else EvilBanner.com does behind his back. I know a guy who was very surprised when I pointed out to him that the valueclick banner on his site was dishing out cookies left and right!
Including identifying info in the URL itself kinda defeats this objective of sneakiness, as it needs active collaboration of the webmaster.
I also heard someone tell me that some linkexchange ads were at some point in order to allow linkexchange to update the entire banner code whenever they needed to
Actually, the main reason for the script src seems to be the same as for iframes: allow the ad to set cookies, where a simple image couldn't. Just try it in netscape: In Edit->Preferences->Advanced, check the box labeled "Only accept cookies originating from the same server as the page being viewed", and watch how it still lets pass cookies attached to all kinds of includes, such as scriptsrc, iframe etc. Seems only cookies from offsite images are blocked.
I do a mass mail out with all the new e-mail addresses. The e-mails are HTML-enabled e-mails. Embedded at the bottom of the e-mail is this web bug:
Actually this extra step of sending a web-bug infested spam is not even needed in most cases. It's enough if the surfer enters his e-mail address into any form on the web which uses the GET method, and which leads to a page having a web bug/banner ad from WebBugsAreEvil.com. The site serving the form does not actually need to be in cahoots with WebBugsAreEvil, apart from the obvious contract for serving its banners. Indeed, with the GET method, form data (containing your E-mail address) will be part of the URL, and thus will be sent to WebBugsAreEvil in the Referer header field. Much more discreet and reliable than sending a webbugged spam, and much more far-reaching too: using the same method, WebBugsAreEvil can collect all kinds of interesting info: First name, last name, home address, all kinds of demographic info such as age, yearly income, hobbies (if user ever participated in a survey having such a form), credit card number (if merchant was foolish enough to have his order form submitted via GET rather than POST). N.B. Even https doesn't protect against this, as this is data that is "intentionnally" sent to WebBugsAreEvil, rather than intercepted...
They could still sue for trademark infringements, for naming the files after songs which they were not
Depends on the kind of service you have. Many satellite service plans use a "return channel by land line", meaning that any upstream packets (from you to the "Internet") travel via landline (modem, isdn, etc.) and the satellite is only used for downstream packets (from the Internet to you). Makes sense, since most people have higher needs in downloading anyways. Advantage: cuts latency in half. Disadvantage: kills any "flat-rate" like advantage, you still need to pay your phone bill.
> It then has to travel down to a microwave dish in europe, again with more signal losses.
Actually, while the largest satellite operator worldwide is indeed located in Europe, ground stations are spread around the world. And, strangely enough, most signal losses are actually not due to atmospheric conditions, but rather to the fact that the average Microsoft PC cannot keep up with the high transfer rates from satellite, and so has to occasionnally drop a packet or two!
> The round trip in simple distance is probably greater than your 28.2k modem,and hence latency is greater
Indeed, at geostationary altitude, space roundtrip is at 2*36000, which gives you 240msec ping time at least. Make that 480msec if you use the satellite for upstream too. Add on top of that to that any landline latency ping time.
> If you need any more discouragement to get satellite internet- the bird is probably owned by microsoft.
If you live in Malaysia, your satellite will indeed be (partly) owned by Microsoft. But don't worry, the omnipresent penguins have taken care of that: the platform (groundstation software) runs mostly on Linux!
This still works today, with 3 1/2 floppies. Normally floppies are formatted to 80 tracks (numbered 0 to 79). However, on most drives you can seek to tracks 80, 81 and 82, allowing you to hide data there. In linux, it's just a matter of typing setfdprm /dev/fd0 cyl=83 to have access to the full number of 83 tracks...
These are small, so are perfect for your portable MP3 player that you wear while jogging. A CD-Rom reader would not only be worrysome to carry around while doing sports, it would also skip whenever you shake it a little bit too much.
But what if they tuck it on the main contract (along with the clauses about compensation, your title, etc) : i.e. without signing it, you would not be employed...
This sounds pretty scary. What happens if your ISP uses dynamic IP's, as most ISP's do? Don't assume police would know about dynamic IP's, this is Belgium after all, that we're talking about.
Case in point, in the olden days, if you, as a foreigner, couldn't/wouldn't pay a speeding fine (which could amount to more than $3000) in Belgium, you could get banned from ever entering Belgium again with your car. Infractions against this ban where punished with instant confiscation of the car.
Only trouble: in Belgium, you would keep your license plates when you bought a new car, whereas in all neigboring countries, the license plates stayed with the car. You guessed it: people buying used cars in those neighboring countries then not only needed to worry about getting not a lemon, but also whether it was safe to take that car to Belgium...