Main Page | Report this Page
Linux Forum Index  »  Linux - Suse Forum  »  Path in 11.1...
Page 1 of 1    

Path in 11.1...

Author Message
Ulick Magee...
Posted: Sun Oct 25, 2009 2:12 pm
Guest
Here's my $PATH - 11.1 64-bit:

/opt/kde3/bin:/home/[username]/bin:/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/X11R6/bin:/usr/games:/usr/lib/mit/bin:/usr/lib/mit/sbin:.:/usr/sbin:/usr/sbin


/usr/sbin is in there twice and . is in there too.

I always thought that . was not supposed to be included in the path for
security reasons.

Can't find any script in /etc/rc.d/* or /etc/init.d/* which adds . to
the path, and it's not in my ~/.bashrc, where else should I look?

I'm pretty sure that . was not in the path by default in 11.0.


Just checked on another user account and it has . in the path, but
/usr/sbin is only there once.



--

Ulick Magee

Free software and free formats for free information for free people.
Open Office for Windows/OSX/Linux: http://www.openoffice.org
openSUSE Linux: http://en.opensuse.org
 
Paul J Gans...
Posted: Sun Oct 25, 2009 3:17 pm
Guest
Ulick Magee <ulickatmaildotcom at (no spam) feckoff.invalid> wrote:

Quote:
Here's my $PATH - 11.1 64-bit:

/opt/kde3/bin:/home/[username]/bin:/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/X11R6/bin:/usr/games:/usr/lib/mit/bin:/usr/lib/mit/sbin:.:/usr/sbin:/usr/sbin


Quote:
/usr/sbin is in there twice and . is in there too.

I always thought that . was not supposed to be included in the path for
security reasons.

Can't find any script in /etc/rc.d/* or /etc/init.d/* which adds . to
the path, and it's not in my ~/.bashrc, where else should I look?

I'm pretty sure that . was not in the path by default in 11.0.


Quote:
Just checked on another user account and it has . in the path, but
/usr/sbin is only there once.

I'm on a 64bit 11.1 system right now. I do NOT have "." in
my path, nor do I have "/usr/sbin". That is resevered for
root.

I suspect that somebody has changed your path, and unless
you log on as root, not in a good way.

--
--- Paul J. Gans
 
Paul J Gans...
Posted: Mon Oct 26, 2009 7:44 am
Guest
J G Miller <miller at (no spam) yoyo.org> wrote:
Quote:
On Mon, 26 Oct 2009 01:17:01 +0000, Paul J Gans wrote:

I suspect that somebody has changed your path, and unless you log on as
root, not in a good way.

Am I getting mixed up with something else, or is there a setting in Yast
which says "add . to user path"? One could also check directly in the
relevant file in /etc/sysconfig.

Now that you mention it, I believe that there is (or was) such a
setting during installation.

Quote:
Furthermore, checks should be made for the PATH variable (if using bash)
in the user's .bashrc and .profile files, as well as in the system
/etc/profile and etc/bashrc, and in the files under /etc/profile.d which
are sometimes added for configuring the enironment of specific
applications.

--
--- Paul J. Gans
 
Paul J Gans...
Posted: Mon Oct 26, 2009 7:45 am
Guest
Ulick Magee <ulickatmaildotcom at (no spam) feckoff.invalid> wrote:
Quote:
DenverD wrote:
AH! try this:

YaST > Security & Users > Local Security > click "Next" to
Miscellaneous Settings and find "Current Directory in root's Path" and
"Current Directory in Path of Regular Users" and UNcheck the box

OK. Current directory in root's path is NOT ticked.
Current directory in user's path IS ticked.

I've unticked it and it writes to the file /etc/sysconfig/suseconfig :


Quote:
# Do you want to have "." in the path for normal users?
# Defaults to "yes" since this has been the case for years.
#
CWD_IN_USER_PATH="no"



Quote:
So it's claiming that this has been the default for years...???? When I
started playing around with compiling madwifi in 10.3 I definitely had
to use ./ to run scripts, so . wasn't in the path then. Can't remember
for 11.0.


Quote:
Also, File Permissions are set to Easy - I think my 10.3 and 11.0
installs had that also. Should I worry about this? This is a laptop that
only I use, with no holes in the firewall, no remote administration
enabled, etc.



Quote:
i wonder, which of the four possible Security Settings (Home
Workstation, Networked Workstation, Network Server or Custom Settings)
was selected when you first arrived in the Local Security
Configuration dialog??

You mean, during install? Can't remember but it was probably Home
Workstation. I don't run any servers or shares so have no need to select
anything more than that.


Quote:
and, i wonder if those two boxes (or either) is checked as the
default....hope not (but, on initial setup i clicked 'Custom' so i do
not know)

That would be interesting to know for sure.
I would have expected that a change like adding . to the path if a
certain install option is chosen, would be mentioned in the release
notes. Help in YaST says that having the . in the path is highly
dangerous, so I'd be surprised if it is the default. I can't remember if
I ticked this option manually at some point.


I don't think it has been the default for many years.
It may have been the default once a long time ago. I
seem to remember that. But I've been typing "./a.out"
for a long time now to get a test binary to run.

--
--- Paul J. Gans
 
Ulick Magee...
Posted: Mon Oct 26, 2009 8:58 am
Guest
DenverD wrote:
Quote:
Ulick Magee wrote:
DenverD wrote:

So it's claiming that this has been the default for years...???? When I
started playing around with compiling madwifi in 10.3 I definitely had
to use ./ to run scripts, so . wasn't in the path then. Can't remember
for 11.0.

i do NOT remember that being the default "for years", or even months!!

Me neither. This is strange.


Quote:
Also, File Permissions are set to Easy - I think my 10.3 and 11.0
installs had that also. Should I worry about this? This is a laptop that
only I use, with no holes in the firewall, no remote administration
enabled, etc.

mine are easy....i figure if they can get close enough (in the
machine) they are smart enough to do as they will no matter what else
is done..

OK.

Quote:
i wonder, which of the four possible Security Settings (Home
Workstation, Networked Workstation, Network Server or Custom Settings)
was selected when you first arrived in the Local Security
Configuration dialog??
You mean, during install? Can't remember but it was probably Home
Workstation. I don't run any servers or shares so have no need to select
anything more than that.

no, i meant when you first saw that page, today....when i saw mine it
said Custom (but, i remember doing that a long time ago)

Mine says Custom also.


Quote:
but, yours is 'fixed' now, which is as it should be..

Thanks!



--

Ulick Magee

Free software and free formats for free information for free people.
Open Office for Windows/OSX/Linux: http://www.openoffice.org
openSUSE Linux: http://en.opensuse.org
 
David Bolt...
Posted: Mon Oct 26, 2009 8:06 pm
Guest
On Monday 26 Oct 2009 13:32, Ulick Magee played with alphabet spaghetti
and left this residue on the plate:

Quote:
# Do you want to have "." in the path for normal users?
# Defaults to "yes" since this has been the case for years.
#
CWD_IN_USER_PATH="no"



So it's claiming that this has been the default for years...????

It was there in SuSE 9.3. It _may_ have been there in SuSE 9.1 and I've
turned it off, but I don't recall doing so, and it certainly isn't in
my 9.1 $PATH.

Quote:
When I
started playing around with compiling madwifi in 10.3 I definitely had
to use ./ to run scripts, so . wasn't in the path then. Can't remember
for 11.0.

It's not there in any $PATH on my systems except the SuSE 9.3. My
openSUSE 10.3 to 11.1 systems don't have it, and nor does my 9.1
system. It could be that it _was_ there for years, and then it was
removed within the last few years but that text was never updated to
match the current conditions.


Regards,
David Bolt

--
Team Acorn: www.distributed.net OGR-NG at (no spam) ~100Mnodes RC5-72 at (no spam) ~1Mkeys/s
openSUSE 10.3 32b | openSUSE 11.0 32b | |
openSUSE 10.3 64b | openSUSE 11.0 64b | openSUSE 11.1 64b | openSUSE 11.2rc1
RISC OS 4.02 | RISC OS 3.11 | openSUSE 11.1 PPC | TOS 4.02
 
stan...
Posted: Wed Oct 28, 2009 3:56 pm
Guest
Ulick Magee wrote:
Quote:
DenverD wrote:
AH! try this:

YaST > Security & Users > Local Security > click "Next" to
Miscellaneous Settings and find "Current Directory in root's Path" and
"Current Directory in Path of Regular Users" and UNcheck the box

OK. Current directory in root's path is NOT ticked.
Current directory in user's path IS ticked.

I've unticked it and it writes to the file /etc/sysconfig/suseconfig :

# Do you want to have "." in the path for normal users?
# Defaults to "yes" since this has been the case for years.
#
CWD_IN_USER_PATH="no"

So it's claiming that this has been the default for years...???? When I
started playing around with compiling madwifi in 10.3 I definitely had
to use ./ to run scripts, so . wasn't in the path then. Can't remember
for 11.0.

I have a 11.0 running here and it does NOT include . in the user or
root path by default.

<snip>

Quote:
and, i wonder if those two boxes (or either) is checked as the
default....hope not (but, on initial setup i clicked 'Custom' so i do
not know)

That would be interesting to know for sure.
I would have expected that a change like adding . to the path if a
certain install option is chosen, would be mentioned in the release
notes. Help in YaST says that having the . in the path is highly
dangerous, so I'd be surprised if it is the default. I can't remember if
I ticked this option manually at some point.

I also did a custom install for the 11.0 so I can't say what might
happen otherwise.

I really find this unimaginable for any distro to do something like
this. Novel seems to have some desire to turn their distro into the
second best Windows around. The rush to drop kde4 on me just so I
could enjoy a more Vista like experience was unpleasant and unwelcome.

I don't need or want my system to mimic windows and I certainly don't
want to copy poor and unsafe design choices from an inferior system.

Stan
 
 
Page 1 of 1    
All times are GMT - 5 Hours
The time now is Mon Nov 30, 2009 1:37 pm