As a US HSBC customer, the security that I see is different than the article describes.
The login process is fairly typical (username, password only), but in mid-July 2006, they changed the process so that they are entered on separate pages. I do not understand how this improves security, because the username is echoed back on the password-entry page. There are no additional interactive anti-replay attack features--the username/password form seems to have been simply split to two pages.
The biggest security feature that I have casually identified is that on the Online Bill Payment page, it is necessary to do a second authentication using a Java-based on-screen keyboard (which must be clicked with a mouse). This avoids a simple keystroke logger but is not beyond other attacks (for instance, it would be somewhat easier to shoulder-surf).
I wonder whether Microsoft changing their policy to charge for security updates might be a sufficient impetus for their EULA's denial of liability to be thrown out through legislation.
In a previous job at a datacenter where we ran Red Hat Enterprise Linux, I frequently got the comment that there seemed to be a lot more Linux patches than Windows patches. All of the updates for optional software (I tried to do minimal installs and/or remove optional things, but the dependencies sometimes made this awkward) simply made the systems seem more needy than the Windows systems.
Many of the vulnerabilities were of low risk to us, but it was rare for the system owners to say that even with this low risk that it was acceptable to hold off on applying the patches.
Last time I looked (because of this kind of issue), my TiVo only lets me adjust the stop time, but it is from Series 1. Did they change this in Series 2?
I didn't see if the purchases from the online music store were truly one-time. In other words, if your iPod and hard drive both get formatted, do you have to buy the songs again?
Having that kind of record-keeping would help make the $0.99/track cost seem more worthwhile to me.
Mr. Bray makes a point about the longevity of XML based documents (where he says that tying up documents in a binary format is foolish), but this is a point that (La)TeX users have been arguing for years.
Will XML really solve this problem? Hopefully the OpenOffice format will help, but if Microsoft maintains its marketshare (and keeps its XML generation limited or even proprietary), are we really better off?
Ken Reek's Pointers on C is a very complete reference. I strongly recommend it if something more full than K&R is desired (as do many of the amazon.com reviewers).
I am perplexed by how you say that it has ``multimedia performance right up there with Linux.'' BeOS was designed from the ground up with multimedia performance in mind, whereas Linux uses the multimedia-unfriendly X11 interface for much of its multimedia presentation. I have been amazed many times over by the way that Be takes advantage of processors for doing multimedia streaming.
Slashdot Mirror
As a US HSBC customer, the security that I see is different than the article describes.
The login process is fairly typical (username, password only), but in mid-July 2006, they changed the process so that they are entered on separate pages. I do not understand how this improves security, because the username is echoed back on the password-entry page. There are no additional interactive anti-replay attack features--the username/password form seems to have been simply split to two pages.
The biggest security feature that I have casually identified is that on the Online Bill Payment page, it is necessary to do a second authentication using a Java-based on-screen keyboard (which must be clicked with a mouse). This avoids a simple keystroke logger but is not beyond other attacks (for instance, it would be somewhat easier to shoulder-surf).
It's interesting that you mention this, because my FreeBSD passwd file came with the following stock entries:
root:*:0:0:Charlie &:/root:/bin/csh
toor:*:0:0:Bourne-again Superuser:/root:
but yet it doesn't seem to be a problem.
I wonder whether Microsoft changing their policy to charge for security updates might be a sufficient impetus for their EULA's denial of liability to be thrown out through legislation.
They are already doing this with the CAP code system.
They can have it when they take it out of my cold dead hands.
Since cell phone cameras don't usually seem to well in low-light situations, this could really help prevent drunk dialing!
In a previous job at a datacenter where we ran Red Hat Enterprise Linux, I frequently got the comment that there seemed to be a lot more Linux patches than Windows patches. All of the updates for optional software (I tried to do minimal installs and/or remove optional things, but the dependencies sometimes made this awkward) simply made the systems seem more needy than the Windows systems.
Many of the vulnerabilities were of low risk to us, but it was rare for the system owners to say that even with this low risk that it was acceptable to hold off on applying the patches.
Last time I looked (because of this kind of issue), my TiVo only lets me adjust the stop time, but it is from Series 1. Did they change this in Series 2?
So Toy Story 3 will be direct-to-video?
What are you going to do about it, Dad?
Too bad the answer wasn't "Hold out for you to produce a movie that's worth protecting."
Or even more appropriate, Clifford Stoll's High Tech Heretic: Reflections of a Computer Contrarian discusses the tradeoffs involved in integrating technology into the classroom (while still recognizing its value).
A $250/year/computer lease payment (plus administrative costs) could almost certainly be spent better.
However, if the Bills ever make another Super Bowl, you can bet I'll have it recorded.
Haven't you suffered enough?
Are you saying that the music industry's greediness is hurting their bottom line?
I didn't see if the purchases from the online music store were truly one-time. In other words, if your iPod and hard drive both get formatted, do you have to buy the songs again?
Having that kind of record-keeping would help make the $0.99/track cost seem more worthwhile to me.
Mr. Bray makes a point about the longevity of XML based documents (where he says that tying up documents in a binary format is foolish), but this is a point that (La)TeX users have been arguing for years.
Will XML really solve this problem? Hopefully the OpenOffice format will help, but if Microsoft maintains its marketshare (and keeps its XML generation limited or even proprietary), are we really better off?
I'll just stick with LaTeX.
Thanks for pointing that out! There will be a reairing of it at midnight ET and a few more through the week.
The article has a related blurb (registration required) at the bottom that says that a 19" iMac will be available in 3Q.
If the 17" iMac caused the death of the 15", it would follow that the 19" would kill the 17".
According to the specs (linked from Fossil's PDA page), the battery does last only 4 days with use, but is rechargable Li-Ion.
Gee, that's so much more typing than you need...
for (@weird_syntax) { print }
Ken Reek's Pointers on C is a very complete reference. I strongly recommend it if something more full than K&R is desired (as do many of the amazon.com reviewers).
I am perplexed by how you say that it has ``multimedia performance right up there with Linux.'' BeOS was designed from the ground up with multimedia performance in mind, whereas Linux uses the multimedia-unfriendly X11 interface for much of its multimedia presentation. I have been amazed many times over by the way that Be takes advantage of processors for doing multimedia streaming.