What is she on? How is this not an issue? If the data had been properly encrypted, it could have been lost with no danger of the data falling into the wrong hands. Ameritrade decided the data was not worth encrypting, and then lost it.
Even if they couldn't be bothered to encrypt the data, they then shouldn't have shipped it the way they did. They should have shipped the data in a briefcase handcuffed to a trusted courier.
This is most definitely a failure, and a significant one at that. I am saddened that Ameritrade doesn't have the decency to own up to their mistakes. In Canada, they could be charged under the PIPED Act.
Hauppauge always seemed to have better drivers? Bwah ha ha. That's laughable. I had one of Hauppauge's earlier cards, the high-end card before the -250 and -350, and the drivers were TERRIBLE. I don't think they ever released Microsoft-certified drivers. In any case, they regularly caused my computer to lock up and even when they worked, they didn't work very well. Now, I suppose it is possible that the drivers from other companies were even worse, but Hauppauge was skirting consumer-protection laws as it was.
ArsTechnica has some information on this, and on how to use third-party drivers, which can make things much more reliable. I cannot immediately find the article, however.
Well, it used to be true but not so much any more. You'd need a super powerful electromagnet to have any chance of erasing the data securely. I mean, an order of magnitude or more powerful than anything your local radio shack will sell you.
A company is legally responsible for copyright infringement committed by their employees in the course of their employment. In this case, therefore, the company would NOT be completely innocent. Or, in fact, innocent at all.
Of course, this hinges somewhat on the fact that it was not a contractor who copied the code but rather, an employee. Or, in fact, a cofounder of the company. I'm not sure if or how things would be different if it was a contractor who produced the work. In any case, though, the company is not allowed to continue distributing the application as they have continued to do, so they'd be at least partially liable.
Re:So When Piracy Causes The End Of Freedom....
on
Canada Says No To DMCA
·
· Score: 2, Insightful
Right, but the cops weren't there because of the pot. Changing the marijuana legislation as a result of this makes as much sense as invading Egypt because of this.
I have of course tested the replication in MySQL to make sure it is doing what I think it is. Working with MySQL's master-master replication involved designing my application from the ground up to support multipart keys, so this solution is a LONG way away from just dropping in the replication and expecting it to work. It does have some advantages such as not requiring a hundred percent reliable network connection between the two MySQL servers. It can survive brief outages without issue.
There are significant problems, mind you. Reestablishing the replication can be much more work than should be necessary, though the problems are not with the data integrity (for replication... I'm aware MySQL isn't perfect in this regard in general).
Master-master replication uses MyISAM tables so it is NOT RAM-based. You are probably thinking of MySQL's cluster type and I have very little experience of that. I also haven't looked at PgPool but CERTAINLY will do so now.
I haven't written a case study of MySQL's master-master replication but may very well do so. Send me your email address and I'll make sure you receive a copy of my writeup if I ever get around to it.
My apologies, I figured you were just posting misinformation deliberately. Looks like it was an honest mistake.
I, too, have a host of reasons to dislike MySQL. Unfortunately, I cannot switch to PostGreSQL because MySQL supports master-master replication (albeit not well) but PostGreSQL does not.
FUD. MyISAM certainly can handle a database of larger than 2 gigs. It can even handle _tables_ larger than 2 gigs. "As you can see, MySQL remembers the create options exactly as specified. And it chose a representation capable of holding 91 GB of data." (p.38, High Performance MySQL: Optimization [sic], Backups, Replication & Load Balancing, by Jeremy D. Zawodny & Derek J. Balling, published by O'Reillly, April 2004.
No, by releasing it under the terms of the GPL, his employer is specifically allowing said patents to be licensed for everyone's free use. See 7 and 8 of the GPL. The employer may have patents to the code (stupid, but possible), but they have legally granted everyone a royalty-free license to use those patents.
I'd love for boost to be in the standard library, but I'm not sure that complaining to the gcc folks is the way to get this done. Surely if we want this in the standard library, it should be included as part of the next version of the ISO C++ standard?
That's very strange as SCO has repeatedly claimed that the BSDs infringed on their intellectual property as well. So why would you ditch Linux and go with BSD if you were concerned about SCO?
But heck, SCO also claimed that Microsoft Windows infringed as well and threatened to go after Microsoft's customers (this was after Microsoft invested in them), so you really couldn't be safe no matter what you did.
I sent an email to the CherryOS team asking for their source code (and noting that their EULA was not valid). All I've got back so far is an automated response, but they promise to reply within 48 hours.
It is NOT fully binary compatible with Linux. I cannot get VMWare 4.5 to run in FreeBSD, for example. Crazy counterexample? Perhaps, but VMWare was a critical application for me and as a result, I had to go back to Linux.
I had some other problems as well. valgrind had problems but my understanding is that these have been resolved now and may not have been anything to do with FreeBSD in the first place.
Re:Maybe something I'll look into
on
SLI Primer
·
· Score: 1
I ran an Intel 400 Mhz CPU and a 466 Mhz CPU on an Abit BP6 motherboard. Yes, that's right, different speed CPUs.
Worked fine, once I patched the operating system to stop using the TSC (time-stamp counter). Windows apparently didn't use the TSC back then.
Better hardware support and much better gaming support. If you don't plan on adding new hardware to your computer and do not use it for gaming, 2k provides essentially nothing valuable.
Yes. Basically, it is now impossible to hook up a Windows 95 machine to the Internet (at least, and use Internet Explorer) while maintaining due dilligence for security fixes and the like. Thus, if you hook up Windows 95 to the Internet and your computer is infected and sends out spam or infects another computer, you are entirely legally responsible.
This is not the case with an operating system which still receives security updates, provided you deploy the security updates in a reasonable timeframe. It is also obviously not the case if you do not hook up Windows 95 to the Internet, or if you hook it up behind a firewall, provide antivirus protection, and use a supported browser such as Firefox.
Many people in the industry believe that SCO was essentially paid by Microsoft to attack open-source. Nevertheless, SCO has threatened to sue Microsoft and to sue anyone who uses Microsoft Windows in their business. Do you feel that SCO's attacks are something we should be seriously concerned about, as Microsoft customers and as users of open-source software? Obviously, Microsoft's recent moves toward indemnification would not cover most users in a lawsuit SCO due to EULA restrictions, lack of complete idemnification, etc. etc.
You'll have to upgrade soon, Windows 2000 hits end of life in June. Though you do get another five years of extended support, and this may be sufficient for you.
Hear hear. Their software is bad enough that I'm not sure I'd want to buy from them again, despite generally glowing reviews with their hardware under Linux.
Slashdot Mirror
What is she on? How is this not an issue? If the data had been properly encrypted, it could have been lost with no danger of the data falling into the wrong hands. Ameritrade decided the data was not worth encrypting, and then lost it.
Even if they couldn't be bothered to encrypt the data, they then shouldn't have shipped it the way they did. They should have shipped the data in a
briefcase handcuffed to a trusted courier.
This is most definitely a failure, and a significant one at that. I am saddened that Ameritrade doesn't have the decency to own up to their mistakes. In Canada, they could be charged under the PIPED Act.
Have you tried more recently? Have you had any luck with other brands?
Hauppauge always seemed to have better drivers? Bwah ha ha. That's laughable. I had one of Hauppauge's earlier cards, the high-end card before the -250 and -350, and the drivers were TERRIBLE. I don't think they ever released Microsoft-certified drivers. In any case, they regularly caused my computer to lock up and even when they worked, they didn't work very well. Now, I suppose it is possible that the drivers from other companies were even worse, but Hauppauge was skirting consumer-protection laws as it was.
ArsTechnica has some information on this, and on how to use third-party drivers, which can make things much more reliable. I cannot immediately find the article, however.
Well, it used to be true but not so much any more. You'd need a super powerful electromagnet to have any chance of erasing the data securely. I mean, an order of magnitude or more powerful than anything your local radio shack will sell you.
Still does.
A company is legally responsible for copyright infringement committed by their employees in the course of their employment. In this case, therefore, the company would NOT be completely innocent. Or, in fact, innocent at all.
Of course, this hinges somewhat on the fact that it was not a contractor who copied the code but rather, an employee. Or, in fact, a cofounder of the company. I'm not sure if or how things would be different if it was a contractor who produced the work. In any case, though, the company is not allowed to continue distributing the application as they have continued to do, so they'd be at least partially liable.
Right, but the cops weren't there because of the pot. Changing the marijuana legislation as a result of this makes as much sense as invading Egypt because of this.
I have of course tested the replication in MySQL to make sure it is doing what I think it is. Working with MySQL's master-master replication involved designing my application from the ground up to support multipart keys, so this solution is a LONG way away from just dropping in the replication and expecting it to work. It does have some advantages such as not requiring a hundred percent reliable network connection between the two MySQL servers. It can survive brief outages without issue.
There are significant problems, mind you. Reestablishing the replication can be much more work than should be necessary, though the problems are not with the data integrity (for replication... I'm aware MySQL isn't perfect in this regard in general).
Master-master replication uses MyISAM tables so it is NOT RAM-based. You are probably thinking of MySQL's cluster type and I have very little experience of that. I also haven't looked at PgPool but CERTAINLY will do so now.
I haven't written a case study of MySQL's master-master replication but may very well do so. Send me your email address and I'll make sure you receive a copy of my writeup if I ever get around to it.
My apologies, I figured you were just posting misinformation deliberately. Looks like it was an honest mistake.
I, too, have a host of reasons to dislike MySQL. Unfortunately, I cannot switch to PostGreSQL because MySQL supports master-master replication (albeit not well) but PostGreSQL does not.
FUD. MyISAM certainly can handle a database of larger than 2 gigs. It can even handle _tables_ larger than 2 gigs. "As you can see, MySQL remembers the create options exactly as specified. And it chose a representation capable of holding 91 GB of data." (p.38, High Performance MySQL: Optimization [sic], Backups, Replication & Load Balancing, by Jeremy D. Zawodny & Derek J. Balling, published by O'Reillly, April 2004.
No, by releasing it under the terms of the GPL, his employer is specifically allowing said patents to be licensed for everyone's free use. See 7 and 8 of the GPL. The employer may have patents to the code (stupid, but possible), but they have legally granted everyone a royalty-free license to use those patents.
I'd love for boost to be in the standard library, but I'm not sure that complaining to the gcc folks is the way to get this done. Surely if we want this in the standard library, it should be included as part of the next version of the ISO C++ standard?
That's very strange as SCO has repeatedly claimed that the BSDs infringed on their intellectual property as well. So why would you ditch Linux and go with BSD if you were concerned about SCO?
But heck, SCO also claimed that Microsoft Windows infringed as well and threatened to go after Microsoft's customers (this was after Microsoft invested in them), so you really couldn't be safe no matter what you did.
I sent an email to the CherryOS team asking for their source code (and noting that their EULA was not valid). All I've got back so far is an automated response, but they promise to reply within 48 hours.
It is NOT fully binary compatible with Linux. I cannot get VMWare 4.5 to run in FreeBSD, for example. Crazy counterexample? Perhaps, but VMWare was a critical application for me and as a result, I had to go back to Linux.
I had some other problems as well. valgrind had problems but my understanding is that these have been resolved now and may not have been anything to do with FreeBSD in the first place.
I ran an Intel 400 Mhz CPU and a 466 Mhz CPU on an Abit BP6 motherboard. Yes, that's right, different speed CPUs.
Worked fine, once I patched the operating system to stop using the TSC (time-stamp counter). Windows apparently didn't use the TSC back then.
Right... because it only takes five seconds to drive to the appropriate Blockbuster store and return it.
Better hardware support and much better gaming support. If you don't plan on adding new hardware to your computer and do not use it for gaming, 2k provides essentially nothing valuable.
Yes. Basically, it is now impossible to hook up a Windows 95 machine to the Internet (at least, and use Internet Explorer) while maintaining due dilligence for security fixes and the like. Thus, if you hook up Windows 95 to the Internet and your computer is infected and sends out spam or infects another computer, you are entirely legally responsible.
This is not the case with an operating system which still receives security updates, provided you deploy the security updates in a reasonable timeframe. It is also obviously not the case if you do not hook up Windows 95 to the Internet, or if you hook it up behind a firewall, provide antivirus protection, and use a supported browser such as Firefox.
Many people in the industry believe that SCO was essentially paid by Microsoft to attack open-source. Nevertheless, SCO has threatened to sue Microsoft and to sue anyone who uses Microsoft Windows in their business. Do you feel that SCO's attacks are something we should be seriously concerned about, as Microsoft customers and as users of open-source software? Obviously, Microsoft's recent moves toward indemnification would not cover most users in a lawsuit SCO due to EULA restrictions, lack of complete idemnification, etc. etc.
You'll have to upgrade soon, Windows 2000 hits end of life in June. Though you do get another five years of extended support, and this may be sufficient for you.
So, you believe that EULAs are completely unenforceable?
I'm not sure the extra overhead would be worth it. That'd be a heck of a lot of synchronisation to prevent conflicts.
OpenBSD. At least, they only require a security patch approximately once every eight years.
Hear hear. Their software is bad enough that I'm not sure I'd want to buy from them again, despite generally glowing reviews with their hardware under Linux.