]
cc: (bcc: Vince
Mulhollon/Brookfield/Norlight)
01/06/2001 Fax to:
11:36 PM Subject: Bug#81396: root shell
fscked after
shell fscked after upgrade to woody
On Sat, Jan 06, 2001 at 08:25:54PM -0800, Aaron Lehmann wrote:
Debian has always exhibited this behavior for me. There's a simple
workaround: don't log in as root.
I don't know which is more distasteful: That you have telnet enabled, or
that you have enabled
Hi Adam,
On Sat, Jan 06, 2001 at 10:55:32PM -0700, Adam Conrad wrote:
Hate to state the obvious, but on a DEFAULT Debian install, if nothing is
changed, root's default path with be dictated by /root/.profile ... Maybe
the machine behaving fine still has this file, and the other has had it
On Sun, Jan 07, 2001 at 04:36:09PM +1100, Craig Sanders wrote:
why not?
the most you'd have to do is put up a single web page with links to
local copies of ssh clients for various platforms...and optionally
replace telnetd with a script (or tcp-wrapper's twist capability)
which printed a
On Sun, Jan 07, 2001 at 08:29:03AM +0200, Eray Ozkural wrote:
On Sat, Jan 06, 2001 at 10:55:32PM -0700, Adam Conrad wrote:
Hate to state the obvious, but on a DEFAULT Debian install, if nothing is
changed, root's default path with be dictated by /root/.profile ... Maybe
the machine behaving
On Sun, Jan 07, 2001 at 04:38:10AM +0200, Eray Ozkural (exa) wrote:
Hi Matt!!
I don't report a bug due to misconfiguration. Let's see if what you
see applies, though.
[ snip rude and silly reply ]
[ time passes ]
On Sun, Jan 07, 2001 at 08:29:03AM +0200, Eray Ozkural wrote:
Hi Adam,
On
On Sun, Jan 07, 2001 at 01:14:40AM -0600, Nathan E Norman wrote:
I apologize for prolonging this thread - it's quite annoying.
However, after reading this enlightened response I wonder if it's
possible for a user to close the (silly) bug he or she reported after
he or she solves the problem.
On Sun, Jan 07, 2001 at 01:57:11AM -0600, Gordon Sadler wrote:
Actually under /usr/doc/debian the doc-debian package provides a number
of files, including bug-main-mailcontrol.txt.
A message to [EMAIL PROTECTED] of this format:
close $(bugnumber)
thanks
will close a bug. Only
Processing commands for [EMAIL PROTECTED]:
close 81396
Bug#81396: root shell fscked after upgrade to woody
Bug closed, send any further explanations to Eray 'exa' Ozkural [EMAIL
PROTECTED]
thanks,
Stopping processing here.
Please contact me if you need assistance.
Darren Benham
On Sun, Jan 07, 2001 at 01:57:11AM -0600, Gordon Sadler wrote:
On Sun, Jan 07, 2001 at 01:14:40AM -0600, Nathan E Norman wrote:
I apologize for prolonging this thread - it's quite annoying.
However, after reading this enlightened response I wonder if it's
possible for a user to close the
On Sun, Jan 07, 2001 at 08:29:03AM +0200, Eray Ozkural wrote:
Thanks for the suggestion. That's it. Please close the bug. That file has
somehow gone and replacing it will solve the problem.
And of course moving .bash_profile out of the way. Thanks again.
Please don't complain why have you
On Sun, Jan 07, 2001 at 01:23:20AM -0600, Nathan E Norman wrote:
Golly, there _was_ a misconfiguration. Now that you've made your
disdain for Branden's sharp tongue well known, I hope you plan to
apologize to Matt Zimmerman for your rudeness.
I'm glad the problem has been resolved. I could
On Sun, Jan 07, 2001 at 09:01:40AM +0200, Eray Ozkural wrote:
On Sun, Jan 07, 2001 at 08:29:03AM +0200, Eray Ozkural wrote:
Thanks for the suggestion. That's it. Please close the bug. That file has
somehow gone and replacing it will solve the problem.
And of course moving .bash_profile
On Sun 07 Jan 2001, Eray Ozkural wrote:
About having telnet enabled: everybody on the campus knows how to use telnet
but would be very surprised I didn't let them connect easily from windows
clients. For me, using telnet is of course a bit insecure but when I'm
not able to use an ssh
On Sun, Jan 07, 2001 at 11:42:57PM +1100, Hamish Moffatt wrote:
On Sun, Jan 07, 2001 at 01:57:11AM -0600, Gordon Sadler wrote:
On Sun, Jan 07, 2001 at 01:14:40AM -0600, Nathan E Norman wrote:
I apologize for prolonging this thread - it's quite annoying.
However, after reading this
On Sun, Jan 07, 2001, Nathan E Norman wrote:
Yes, but also anyone, including the submitter, spammers, joe public
etc can email [EMAIL PROTECTED] to close a bug as well. The BTS doesn't
care.
So does this mean the submitter can close their own bug or not? I'm
not sure what you mean by
On Sun, Jan 07, 2001 at 01:09:12PM -0600, Nathan E Norman wrote:
So does this mean the submitter can close their own bug or not? I'm
not sure what you mean by the BTS doesn't care
Anyone can close a bug - the BTS doesn't actually check where the close
command comes from. The unenforced
On Sun, Jan 07, 2001 at 01:09:12PM -0600, Nathan E Norman wrote:
So does this mean the submitter can close their own bug or not? I'm
not sure what you mean by the BTS doesn't care
Yes, the BTS will allow the submitter to close their own bug that way.
So can anyone else. (AFAIK.)
Hamish
--
Paul Slootman [EMAIL PROTECTED] wrote:
On Sun 07 Jan 2001, Eray Ozkural wrote:
About having telnet enabled: everybody on the campus knows how to use telnet
but would be very surprised I didn't let them connect easily from windows
clients. For me, using telnet is of course a bit insecure but
On Sun 07 Jan 2001, Colin Watson wrote:
Paul Slootman [EMAIL PROTECTED] wrote:
Search google for putty, if you need an ssh client for windows.
http://www.chiark.greenend.org.uk/~sgtatham/putty/ (hmm, I appear to
have that memorized - I end up grabbing it any time I'm at a public
Colin Watson wrote:
http://www.chiark.greenend.org.uk/~sgtatham/putty/ (hmm, I appear to
have that memorized - I end up grabbing it any time I'm at a public
Windows-based Internet terminal).
way cool. a mud addict friend of mine always used putty, now i see why :)
you can even do x-win
Package: general
Version: N/A; reported 2001-01-06
Severity: important
After I upgraded from potato to woody on
an i386 machine, I observed a strange sympton
I login as root. It doesn't matter where, console, X or
from network...
When I check the environment, normal user environment is
present.
Hi,
Eray == Eray 'exa' Ozkural [EMAIL PROTECTED] writes:
Eray After I upgraded from potato to woody on
Eray an i386 machine, I observed a strange sympton
Eray I login as root. It doesn't matter where, console, X or
Eray from network...
Eray When I check the environment, normal user
Hi
Manoj Srivastava wrote:
There is not enough information in this report to actually do
anything about debugging the problem. You don't even mention what
shell you are using as /bin/sh; what you have in /etc/environemnt;
what you have in the configuration files for the rot user,
This is how it looks like
[EMAIL PROTECTED]:~$ telnet borg
Trying 139.179.21.143...
Connected to borg.cs.bilkent.edu.tr.
Escape character is '^]'.
Debian GNU/Linux woody borg.cs.bilkent.edu.tr
login: root
Password:
[EMAIL PROTECTED]:~# echo $PATH
Eray Ozkural (exa) (2001-01-07 00:04:14 +0200) :
How should I debug this?
One thing I did once was rename /bin/bash as bash-real, and write a
#!/bin/bash-real wrapper that logged everything (yeah, I did not know
of the set -x trick at that time). It might be dirty, but it might
just work.
On Sun, Jan 07, 2001 at 12:04:14AM +0200, Eray Ozkural (exa) wrote:
This is how it looks like
[EMAIL PROTECTED]:~$ telnet borg
Trying 139.179.21.143...
Connected to borg.cs.bilkent.edu.tr.
Escape character is '^]'.
Debian GNU/Linux woody borg.cs.bilkent.edu.tr
login: root
Password:
Hi Matt!!
I don't report a bug due to misconfiguration. Let's see if what you
see applies, though.
Matt Zimmerman wrote:
First, man su to find out where su(1) is getting its environment from.
Searching for 'environment' on that man page, you can find this:
The current environment
On Sun, Jan 07, 2001 at 12:04:14AM +0200, Eray Ozkural (exa) wrote:
[EMAIL PROTECTED]:~$ telnet borg
Trying 139.179.21.143...
Connected to borg.cs.bilkent.edu.tr.
Escape character is '^]'.
Debian GNU/Linux woody borg.cs.bilkent.edu.tr
login: root
Password:
[EMAIL PROTECTED]:~# echo $PATH
On Sun, Jan 07, 2001 at 04:38:10AM +0200, Eray Ozkural (exa) wrote:
Then, read /etc/login.defs. Note the values of the ENV_PATH and ENV_SUPATH
options. These are used by login(1) and su(1). Test login(1) and su(1) and
make sure they are doing what you expect. If they aren't, find out
On Sat, Jan 06, 2001 at 08:25:54PM -0800, Aaron Lehmann wrote:
Debian has always exhibited this behavior for me. There's a simple
workaround: don't log in as root.
I don't know which is more distasteful: That you have telnet enabled, or
that you have enabled remote root logins via telnet.
Eray Ozkural wrote:
About having telnet enabled: everybody on the campus knows how to use telnet
but would be very surprised I didn't let them connect easily from windows
clients. For me, using telnet is of course a bit insecure but when I'm
not able to use an ssh client... it's easier.
Well,
On Sun, Jan 07, 2001 at 04:38:10AM +0200, Eray Ozkural (exa) wrote:
We use telnet here because this is a diverse university network; we
can't force people to run ssh and any moron could go root on this
machine if he really wanted to.
why not?
the most you'd have to do is put up a single web
33 matches
Mail list logo
