OpenEuphoria

2. Re: Linux broken + security risk

• Posted by Matt Lewis <matthewwalkerlewis at gmail.com> Jun 03, 2005
• 1034 views

Neil Fraser wrote:
> 
> Installed a brand new installation of Euphoria 2.5 on Debian (Sarge).
> All attempts to execute Euphoria generate the following:
> 
> /usr/local/euphoria/bin# ./exu
> Error opening terminal: xterm.
> 
> Exactly how to I debug this?  The previous version of Euphoria worked
> properly.
> 
> 
> Also, over a year ago I sent a private mail to the developers pointing out
> that their default Linux install leaves many of the files world-writable,
> files which are later executed.  This is a major security risk.  The response
> was "Thanks, I'll try to keep that in mind for the next release".
> 
> Guess they forgot.  Maybe a more public posting will help.
> 


In your .bashrc put in this line:

export TERM=ansi

Matt Lewis

4. Re: Linux broken + security risk

• Posted by Neil Fraser <euphoria at neil.fraser.name> Jun 03, 2005
• 995 views

Matt Lewis wrote:
> In your .bashrc put in this line:
> export TERM=ansi

Thanks.  That works.

Robert Craig wrote:
> Thanks, I'll try to keep that in mind for the next release.  

I'll be watching.  


Now if only there was a way to specify where the library files are
without using environment variables.  Apache doesn't have a clue
when executing a Euphoria CGI, so I've had to edit every file in
the library to say things like:

include /usr/local/euphoria/include/sort.e
include /usr/local/euphoria/include/misc.e

Most applications either use a configuration file at a known location
(e.g. euphoria.cfg in the same directory as exu) or else they build
the library paths into the executable when the source code is
configured prior to compiling (not an option here if Euphoria comes
precompiled).

6. Re: Linux broken + security risk

• Posted by Jason Gade <jaygade at gmail.com> Jun 04, 2005
• 1016 views

Neil Fraser wrote:
> posted by: Neil Fraser <euphoria at neil.fraser.name>
> 
> Matt Lewis wrote:
> 
>>In your .bashrc put in this line:
>>export TERM=ansi
> 
> 
> Thanks.  That works.
> 
> Robert Craig wrote:
> 
>>Thanks, I'll try to keep that in mind for the next release.  
> 
> 
> I'll be watching.  
> 
> 
> Now if only there was a way to specify where the library files are
> without using environment variables.  Apache doesn't have a clue
> when executing a Euphoria CGI, so I've had to edit every file in
> the library to say things like:
> }}}
<eucode>
> include /usr/local/euphoria/include/sort.e
> include /usr/local/euphoria/include/misc.e
> </eucode>
{{{

> Most applications either use a configuration file at a known location
> (e.g. euphoria.cfg in the same directory as exu) or else they build
> the library paths into the executable when the source code is
> configured prior to compiling (not an option here if Euphoria comes
> precompiled).

Most GUI programs use a config file, but I think that most language 
interpreters/compilers still use environment variables.  Actually, I 
think a lot of programs use both, and that might be a good idea.

Of course, I don't have any idea about CGI programs.

-- 
==============================
Too many freaks, not enough circuses.
j.