Re: Protecting Source code of a perl script
From: Ben Morrow (usenet_at_morrow.me.uk)
Date: 11/24/03
- Next message: Dan Anderson: "Re: Newbie question - calling perl from html"
- Previous message: Ben Morrow: "Re: Image::Magick memory leak question"
- In reply to: ctcgag_at_hotmail.com: "Re: Protecting Source code of a perl script"
- Next in thread: Rafael Garcia-Suarez: "Re: Protecting Source code of a perl script"
- Reply: Rafael Garcia-Suarez: "Re: Protecting Source code of a perl script"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Mon, 24 Nov 2003 15:19:47 +0000 (UTC)
ctcgag@hotmail.com wrote:
> "Eric J. Roode" <REMOVEsdnCAPS@comcast.net> wrote:
> > That analogy is not quite on. The parts need not be transparent, but the
> > design of the lock should be published. Would you trust a lock from a
> > manufacturer who refused to tell you how it worked, but simply said,
> > "Trust me. It's super-duper secure. Nobody can pick this lock!" ?
>
> Well, if *I* was that manufacturer, sure, I would trust myself. And isn't
> that what's going on here?
If it is, then you should not. Not unless you are a computer security expert.
The main point here, which you seem not to be getting, is that is it
*just as easy* (pretty much) to find exploitable holes in code if you
don't have the source, but impossible to fix them.
Ben
--
Although few may originate a policy, we are all able to judge it.
- Pericles of Athens, c.430 B.C.
ben@morrow.me.uk
- Next message: Dan Anderson: "Re: Newbie question - calling perl from html"
- Previous message: Ben Morrow: "Re: Image::Magick memory leak question"
- In reply to: ctcgag_at_hotmail.com: "Re: Protecting Source code of a perl script"
- Next in thread: Rafael Garcia-Suarez: "Re: Protecting Source code of a perl script"
- Reply: Rafael Garcia-Suarez: "Re: Protecting Source code of a perl script"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|