Re: protecting perl script source

From: frank @ absoluta.org ( Frank Ned ) (@)
Date: 01/24/03

  • Next message: John Hanna: "Re: protecting perl script source" 
    Date: Fri, 24 Jan 2003 16:44:56 -0200
From: "frank @ absoluta.org ( Frank Ned )" <frank@absoluta.org>
To: John Hanna <jhanna@cproject.com>

    www.perl2exe.com

    John Hanna wrote:
    >
    > Hi. Let's assume someone wrote a perl script that figured out how to make a
    > lot of money on the stock market, but that they wanted to protect the script
    > because if others began using it, it would dimish its returns. The new
    > millionaire would want to protect her creation, but it has to run on a
    > computer with access to the internet. She puts it on a box which she tries
    > to keep patched, it's behind a firewall, and only root has access to the
    > scripts. The scripts need to run unattended, and the system needs to boot
    > unattended. She fears two things: a remote root vulnerability, and that
    > someone would physically walk off with the box.
    >
    > My impression is that under these conditions, besides vigilance, limiting
    > running processes, working on physical security, keeping up on patches,
    > possibly some sort of IDS -- there really isn't anything she can do to
    > protect the source. If it's booting unattended, and running scripts
    > unattended there's no sort of crypto strategy that could protect either
    > against an intruder with root access or physical access to the hard drive.
    >
    > What do you think?
    > John

    Relevant Pages

    • Re: Runtime Protection
      ... I'm interested in knowing if the info in scripts is vulnerable and also ... a "runtime" data file is simply the same data files as FileMaker, ... The best way to protect them is to FIRST create a user and password ...
      (comp.databases.filemaker)
    • protecting perl script source
      ... lot of money on the stock market, but that they wanted to protect the script ... to keep patched, it's behind a firewall, and only root has access to the ... The scripts need to run unattended, and the system needs to boot ... unattended there's no sort of crypto strategy that could protect either ...
      (SecProg)
    • Re: Restrict FileSystemObject to its virtual dir
      ... > I'd like to protect each site from interference of other sites scripts ... > Is there a way to restrict FSO to it's virtual directory? ... Tom Kaminski IIS MVP ... http://www.iistoolshed.com/ - tools, scripts, and utilities for running IIS ...
      (microsoft.public.inetserver.iis.security)
    • Re: Restrict FileSystemObject to its virtual dir
      ... > I'd like to protect each site from interference of other sites scripts ... > Is there a way to restrict FSO to it's virtual directory? ... Tom Kaminski IIS MVP ... http://www.iistoolshed.com/ - tools, scripts, and utilities for running IIS ...
      (microsoft.public.inetserver.iis)
    • SUMMARY and apology Re: Some bash/tty questions
      ... Some people tend to create complex login scripts ... If you don't allow direct login to root, but rather su to root, then so ... Hi, not to bash down on bash, but perhaps you should try zsh, it has the shared history thing built in. ...
      (SunManagers)