I sense a mix-up between DRM and open/standardization of format. DRM alone doesn't create the kinds of problems outlined in this post. Perhaps we should be more uncomfortable about the lack of inter-operability or portability between purchased eBooks and apps that can display them. I think that DRM would be fine if it was implemented in an open/universal system.
The question on my mind is - what is Zalewski's incentive in releasing this information directly to the public instead of first to mozilla, esp. just following a release...?
It can't be to gain trust/admiration by the open source community. It also can't be to gain trust by corporations either (releasing notice of a flaw just after a new release and without first contacting the company must scare the pants off of any corporation!)
Is it merely hubris? Or is there some corporate smear money being exchanged here?
Yes, true. Smart cards use a keystore that can be locked using a PIN, but we have yet to see if the cellphone software designers make proper use of this feature!
Hmm, try setting a password/pin number?
It's still no less secure than a credit card. The big question will be which way the liability falls. If it falls on the user (unlike with credit cards) then I'll just stick to paying with plastic for now.
I work for a web consulting firm, and we've had great experiences sending our clients to Kattare.
Kattare's shared server (well, shared machine, at least) accounts run anywhere from $9 to $54 per month, and they run Apache web server (to deliver static html files) and your own personal copy of Tomcat (via proxy through Apache) for the dynamic pages, they have excellent tech support, and they allow you to run Cocoon (the XML publishing pipeline), PostgreSQL, MySQL, etc.
As for mail service, they allow both POP3 and IMAP mail access (their standard email account is 30 MB disk space) - great for people who are on the go and want to keep most of their mail in a centralized (IMAP) server.
The shared hosting pricing and relative reliability are great for small companies, nonprofits, or even a personal account. They run linux everywhere (with ssh access, etc), they are incredibly prompt when you have a request. Sometimes they have downtime, but they're very quick to recognize fix problems when they arise.
I don't have any personal experience with Kattare's dedicated servers, but I have confidence they would do as good of a job with those as they do with the shared machine hosting. They're a dream to work with, especially if you're big on linux/open source software. In any event, if you're looking for a provider, take a look at their site - you'll probably like what you see.
Slashdot Mirror
I sense a mix-up between DRM and open/standardization of format. DRM alone doesn't create the kinds of problems outlined in this post. Perhaps we should be more uncomfortable about the lack of inter-operability or portability between purchased eBooks and apps that can display them. I think that DRM would be fine if it was implemented in an open/universal system.
The question on my mind is - what is Zalewski's incentive in releasing this information directly to the public instead of first to mozilla, esp. just following a release...? It can't be to gain trust/admiration by the open source community. It also can't be to gain trust by corporations either (releasing notice of a flaw just after a new release and without first contacting the company must scare the pants off of any corporation!) Is it merely hubris? Or is there some corporate smear money being exchanged here?
If you ask me, port knockers are all a bunch of fart knockers.
Yes, true. Smart cards use a keystore that can be locked using a PIN, but we have yet to see if the cellphone software designers make proper use of this feature!
Hmm, try setting a password/pin number? It's still no less secure than a credit card. The big question will be which way the liability falls. If it falls on the user (unlike with credit cards) then I'll just stick to paying with plastic for now.
Wouldn't anyone (e.g. a competing firm) that wants access to the modified code have the right to sue for it?
I work for a web consulting firm, and we've had great experiences sending our clients to Kattare.
Kattare's shared server (well, shared machine, at least) accounts run anywhere from $9 to $54 per month, and they run Apache web server (to deliver static html files) and your own personal copy of Tomcat (via proxy through Apache) for the dynamic pages, they have excellent tech support, and they allow you to run Cocoon (the XML publishing pipeline), PostgreSQL, MySQL, etc.
As for mail service, they allow both POP3 and IMAP mail access (their standard email account is 30 MB disk space) - great for people who are on the go and want to keep most of their mail in a centralized (IMAP) server.
The shared hosting pricing and relative reliability are great for small companies, nonprofits, or even a personal account. They run linux everywhere (with ssh access, etc), they are incredibly prompt when you have a request. Sometimes they have downtime, but they're very quick to recognize fix problems when they arise.
I don't have any personal experience with Kattare's dedicated servers, but I have confidence they would do as good of a job with those as they do with the shared machine hosting. They're a dream to work with, especially if you're big on linux/open source software. In any event, if you're looking for a provider, take a look at their site - you'll probably like what you see.