From: Buddy Brannan <davros@ycardz.com>
To: blinux-list@redhat.com
Subject: Re: Digital Talking Book Standard
Date: Mon, 19 Nov 2001 11:31:36 -0600 [thread overview]
Message-ID: <20011119113136.B8371@dalek.dhs.org> (raw)
In-Reply-To: <3.0.6.32.20011119110639.00a9f100@mail.doorpi.net>
On Mon, Nov 19, 2001 at 11:06:39AM -0600, Brent Harding wrote:
> I don't think the drm will work in the long run. It has to be proprietary
> to not allow hacking, anyone who has the source code can hack a program to
> undo what the original did.
Anything (proprietary or not) can be hacked, given enough time and
skill. This has to be the worst argument for proprietary software I've
seen. As I've seen written somewhere...security by obscurity is no
security at all. What does a proprietary security system have that a
free one doesn't have? Well, let's see. No checks against sloppy
programming. Look at the deal with Adobe's Ebook format; that Russian
fellow found a way to get into it, gave a talk about it, and was
arrested, jailed, and is now on trial for copyright infringement. Did
he actually infringe anyone's copyright? Did he actually steal
anyone's work? No, he pointed out a security flaw and told someone how
it could be exploited. Rather than being glad of the feedback so the
problem could be fixed, Adobe sent the feds after him! That isn't
security. Now if these guys had used a free standard, any security
holes could be found and addressed. It's a much better deal for
everyone. And eventually (I say eventually because human beings are
pretty stupid about things sometimes), people who should already know
better but don't will see that free software really is good for all of
us. I firmly believe that that is where our future lies.
--
Buddy Brannan, KB5ELV | From the pines down to the projects,
Email: davros@ycardz.com | Life pushes up through the cracks.
Phone: (972) 276-6360 | And it's only going forward,
ICQ: 36621210 | And it's never going back.--Small Potatoes
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
Martin G. McCormick
` Saqib Shaikh
` Peter Toneby
` Janina Sajka
` Peter Toneby
` Nicolas Pitre
` Peter Toneby
` Lloyd G. Rasmussen
` Nicolas Pitre
` Nicolas Pitre
` Peter Toneby
` Janina Sajka
` Nicolas Pitre
` Janina Sajka
` Nicolas Pitre
` Brent Harding
` Nicolas Pitre
[not found] ` <Pine.LNX.4.33.0111191409370.3206-100000@toccata.grg.afb.ne t>
` Brent Harding
[not found] ` <Pine.LNX.4.33.0111191147560.2815-100000@toccata.grg.afb.ne t>
` Brent Harding
` Nicolas Pitre
` Joel Zimba
` Brent Harding
` Brent Harding
` Nicolas Pitre
` philwh
` Janina Sajka
` Brent Harding
` Buddy Brannan [this message]
` Brent Harding
[not found] ` <Pine.LNX.4.33.0111191114500.2815-100000@toccata.grg.afb.ne t>
` Brent Harding
` Luke Davis
` cbowman
` ssh A. R. Vener
` ssh cbowman
` ssh Luke Davis
` ssh Andor Demarteau
` ssh Luke Davis
` ssh Fredrik Larsson
` ssh Luke Davis
` ssh Fredrik Larsson
` ssh cbowman
` ssh A. R. Vener
` ssh A. R. Vener
` ssh Luke Davis
` Digital Talking Book Standard Brent Harding
` cbowman
` Luke Davis
` cbowman
` Janina Sajka
` Pratik Patel
` Brent Harding
-- strict thread matches above, loose matches on Subject: below --
Janina Sajka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20011119113136.B8371@dalek.dhs.org \
--to=davros@ycardz.com \
--cc=blinux-list@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).