Oron Peled wrote:
On Sun, 23 Feb 2003 00:52:22 +0200 (IST)
Matan Ziv-Av [EMAIL PROTECTED] wrote:
On Sat, 22 Feb 2003, Oron Peled wrote:
Another related issue. I hope nobody don't use '.' in your path
as root -- this is suicidal in terms of security.
Only on systems which (might) have
On Sat, Feb 22, 2003, Oron Peled wrote about Re: Problem with Pth or make or what?:
Obviously! This also point to a bad habbit:
Daniel you have '.' in your path!!!
It's not necessarily a bad habbit... Once upon a time, this was considered
good practice for non-root users.
But calling
On Sun, Feb 23, 2003, Shlomi Fish wrote about Re: Problem with Pth or make or what?:
Another related issue. I hope nobody don't use '.' in your path
as root -- this is suicidal in terms of security.
Only on systems which (might) have malicious users. Not relevant for
home computers.
It
Oron Peled wrote:
On Fri, 21 Feb 2003 17:03:42 +0200
Shaul Karl [EMAIL PROTECTED] wrote:
On Fri, Feb 21, 2003 at 03:14:44PM +0200, Daniel Feiglin wrote:
You get a clean compile/link, but running test does nothing!
A name space collision with bash's internal command?
Obviously! This also
Oh, silly me!
It was indeed a name space thing. Enter ./test and it all works.
Yuk.
Thanks all. I suppose I'd better pthread_join(...) or finish up as the
list zombie ...
Daniel
Daniel Feiglin wrote:
Has anyone come across this:
1. Environment: SuSE 8.1 as is, kernel 2.4.19 and gcc 3.2
2.
Oh, silly me!
It was indeed a name space thing. Enter ./test and it all works.
Yuk.
Thanks all. I suppose I'd better pthread_join(...) or finish up as the
list zombie ...
Daniel
Daniel Feiglin wrote:
Has anyone come across this:
1. Environment: SuSE 8.1 as is, kernel 2.4.19 and gcc 3.2
2.
Nadav Har'El wrote:
On Sat, Feb 22, 2003, Oron Peled wrote about Re: Problem with Pth or make or what?:
Obviously! This also point to a bad habbit:
Daniel you have '.' in your path!!!
It's not necessarily a bad habbit... Once upon a time, this was considered
good practice for non-root
On 2003-02-23, Daniel Feiglin wrote:
This point also occurred to me - but then most newbies would be using a
GUI like Gnome or KDE, so the issue would rarely if ever arise. It is
really a commandline thing.
If they use a GUI, they have no reason in the world to have '.' in thier
path - it's
-Original Message-
From: Beni Cherniavsky
Sent: Sunday, February 23, 2003 2:02 PM
Subject: Re: Problem with Pth or make or what?
Aside from security, it can also confuse scripts when you run
them in a
directory containing a program named the same as some system
program the
Beni Cherniavsky [EMAIL PROTECTED] writes:
Aside from security, it can also confuse scripts when you run them in a
directory containing a program named the same as some system program the
script uses.
That will be a problem with the script. In scripts, it is a good idea
to use absolute paths
On 2003-02-23, [EMAIL PROTECTED] wrote:
-Original Message-
From: Beni Cherniavsky
Sent: Sunday, February 23, 2003 2:02 PM
Subject: Re: Problem with Pth or make or what?
Aside from security, it can also confuse scripts when you run
them in a
directory containing a program
-Original Message-
From: Beni Cherniavsky
Sent: Sunday, February 23, 2003 2:54 PM
Cc: [EMAIL PROTECTED]
Subject: RE: Problem with Pth or make or what?
Good advice. Indeed a quick grep of scripts in /usr/bin
shows most reset
the path. I was refering to my own ~/bin scripts and
On Sun, 2003-02-23 at 14:54, Beni Cherniavsky wrote:
On a second thought, having '.' in the *end* of the path is almost safe.
Still, if you want to be completely safe, you shouldn't do even that --
I bet you sometimes type e.g. ls-l or l s-l, and these typos can be
taken advantage of just as
On 2003-02-23, Alex Shnitman wrote:
On Sun, 2003-02-23 at 14:54, Beni Cherniavsky wrote:
On a second thought, having '.' in the *end* of the path is almost safe.
Still, if you want to be completely safe, you shouldn't do even that --
I bet you sometimes type e.g. ls-l or l s-l, and these
On 2003-02-23, [EMAIL PROTECTED] wrote:
-Original Message-
From: Beni Cherniavsky
Sent: Sunday, February 23, 2003 2:54 PM
Cc: [EMAIL PROTECTED]
Subject: RE: Problem with Pth or make or what?
Good advice. Indeed a quick grep of scripts in /usr/bin shows most
reset the
On Sat, 22 Feb 2003, Oron Peled wrote:
Another related issue. I hope nobody don't use '.' in your path
as root -- this is suicidal in terms of security.
Only on systems which (might) have malicious users. Not relevant for
home computers.
--
Matan Ziv-Av. [EMAIL
On Sun, 23 Feb 2003, Matan Ziv-Av wrote:
On Sat, 22 Feb 2003, Oron Peled wrote:
Another related issue. I hope nobody don't use '.' in your path
as root -- this is suicidal in terms of security.
Only on systems which (might) have malicious users. Not relevant for
home computers.
It is
On Fri, Feb 21, 2003 at 03:14:44PM +0200, Daniel Feiglin wrote:
3. gcc -Wall -g -otest test_httpd.c test_common.c -lpth
You get a clean compile/link, but running test does nothing!
A name space collision with bash's internal command?
$ test
$ type test
test is a shell builtin
$
But
18 matches
Mail list logo
