April 2002 - openSUSE Security - openSUSE Mailing Lists

Re: [suse-security] ifconfig and promiscuos mode
by Michael Stern 12 Apr '02

12 Apr '02

> What other ways can I be sure that my box has not been > compromised? I have run adorefind, negative, chkrootkit, all negative. well md5 signatures would be okay if you can put the hard disk into another computer and have the signatures of the original files ... i guess. cheers!

2 1

Re: [suse-security] openssh client configuration files
by Joerg Ruhe 11 Apr '02

11 Apr '02

Hello Christopher, thanks for your answer > Make things easy for yourself. First return your ssh config file located > in your home directory back to the default settings. The default on my system was no ssh ssh config file in my home directory. When I delete this file naturly I don't have this problem, since ssh only reads the system-wide configuration file, but I need this file to apply special settings for an user. > Next ensure that the > "ListenAddress" in /etc/ssh/sshd_config is set to your correct IP. Also > set "PermitRootLogin" to no. > Give "rcsshd reload" and then "rcsshd restart" ago and let me know what > happens. Okay, "ListenAddress" was not set in my sshd_config and "PermitRootLogin" was set to without-password. I changed the settings to your sugestions, but nothing changed. Ssh still reads and applys the /etc/ssh/ssh_config before the file in my home/.ssh directory. Excuse me if made myself not totally clear in my first message ( or if I have a wrong understanding of your sugestions ). I don't have any problems with incoming ssh connections to that system, but with connections originating on that system. Joerg Ruhe Joerg.Ruhe(a)epost.de

1 0

Re: [suse-security] openssh client configuration files
by Roland Kuhn 11 Apr '02

11 Apr '02

On Thu, 11 Apr 2002, Joerg Ruhe wrote: > Hello Roland, > > [...] > > > > > > Here the options in the system-wide configuration file are applied first. > > > I have seen this on several differnt computers, all > > > with SuSE 7.3 and openssh 2.9.9p2 . > > > > From an algorithmic standpoint it would make sense to read the > > configuration files in reverse order, but this doesn't mean anything. Did > > you experience a setting in /etc/ssh/ssh_config overriding a user setting? > > Thanks for your answer. > > Thats exactly what happend. A setting in /etc/ssh/ssh_config overrides an > user setting ( I tried this with several options ). > > Does it work that way on your system ? > These are from my system: debug1: Reading configuration data /home/rkuhn/.ssh/config debug1: Applying options for * debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * I just verified that the settings from /home/rkuhn/.ssh/config override the ones from /etc/ssh/ssh_config. Ciao, Roland +---------------------------+-------------------------+ | TU Muenchen | | | Physik-Department E18 | Raum 3558 | | James-Franck-Str. | Telefon 089/289-12592 | | 85747 Garching | | +---------------------------+-------------------------+

2 1

Re: [suse-security] openssh client configuration files
by Roland Kuhn 11 Apr '02

11 Apr '02

Hello Joerg! On Wed, 10 Apr 2002, Joerg Ruhe wrote: > The man page and the o'reily book state the order in which configuration data > is obtained as : > 1. command line options, > 2. user's configuration file ($HOME/.ssh/config) > 3. system-wide configuration file (/etc/ssh/ssh_config) > > My trouble is, I'm observing a differnt behaviour ( as you can see in the > log below ): > OpenSSH_2.9.9p2, SSH protocols 1.5/2.0, OpenSSL 0x0090602f > debug1: Reading configuration data /etc/ssh/ssh_config > debug1: Applying options for * > debug1: Reading configuration data /home/ruhej/.ssh/config > debug1: Applying options for * > > Here the options in the system-wide configuration file are applied first. I > have seen this on several differnt computers, all > with SuSE 7.3 and openssh 2.9.9p2 . > >From an algorithmic standpoint it would make sense to read the configuration files in reverse order, but this doesn't mean anything. Did you experience a setting in /etc/ssh/ssh_config overriding a user setting? Ciao, Roland +---------------------------+-------------------------+ | TU Muenchen | | | Physik-Department E18 | Raum 3558 | | James-Franck-Str. | Telefon 089/289-12592 | | 85747 Garching | | +---------------------------+-------------------------+

3 3

SuSE 8.0
by Richard Ibbotson 11 Apr '02

11 Apr '02

Hi Will harden_suse.rpm be available for the next release of SuSE 8.0 or shall I have to download it as source code from the appropriate web page ? As far as I can see each new release of SuSE software requires that a new version of harden_suse.rpm is used. Is this correct ? Thanks -- Richard www.sheflug.co.uk

1 0

Openssh - how do you disable "PasswordAuthentication" for a speci fic user
by Steven Thompson 11 Apr '02

11 Apr '02

Hi All Q1. How do you disable "PasswordAuthentication" for a specific user, as I only want to allow PublicKeyAuthentication. Q2. Is it possible to user1@host1 user1@host2 as config setting for the "AllowUsers". (ie one account, but 2 valid hosts to login from). Q3. What options are available to limit a user to their home directory with out having to apply the chroot patch to Openssh. (i.e. they can't "cd .." backwards into the directory tree, but they can "cd .." forward in their home directory" Thanks in advance Steven

2 1

ifconfig and promiscuos mode
by Oswaldo Castro 11 Apr '02

11 Apr '02

Hi List, I started a tcpdump session and ran the ifconfig command to see if it returns the string "PROMISC" in the command's output. There's nothing there showing me this mode of operation. I know that tcpdump puts the interface to promiscuos mode (by default) and I am almost sure that the tcpdump was not hacked (this is a very fresh installation). Is there a problem with ifconfig from the SuSE distro ? Which are the other ways ? I will be glad for any kind of information Oswaldo Castro

4 5

ssh lock out
by Alexander Pacheco 10 Apr '02

10 Apr '02

Hi, I had the following message to the suse-security mailing list. Is there anybody who can help me? I do not want to remotely log into my home system as root. It locks if I login with my use name. Thanks for the help Alex Hi, I have a Suse 7.3 with Susefirewall activated at home which I can access from workplace using ssh. My problem is my home PC locks up if I connect using my user name and try to change directory but not when I login as root. I get the same problem when I do ssh localhost on my PC. Could anybody give me a solution to this. Thanks for your help Alex -- ************************************************************* * Alexander Pacheco * * 2323, NPB, Tel: Office (352)-392-3010 * * P.O. box 118435 Home (352)-336-4036 * * University of Florida, * * Gainesville, Fl 32611-8435. * * pacheco(a)qtp.ufl.edu alexp(a)ufl.edu * * http://www.qtp.ufl.edu/~pacheco * *************************************************************

6 6

IMP 2.2.8
by Martin Sckopke 10 Apr '02

10 Apr '02

Hi all, this was on bugtraq on Saturday: > The Horde team announces the availability of IMP 2.2.8, which prevents > some potential cross-site scripting (CSS) attacks. Site administrators > should consider upgrading to IMP 3 (our first recommendation), but if this > is not possible, IMP 2.2.8 should be used to prevent these potential > attacks. Will there be an IMP 2.2.8 for SuSE-EMail-Server II ? Will there be an IMP 3.x.x for SuSE-EMail-Server II ? Will IMP 3.x.x run with SuSE-EMail-Server II? Thanks for your help, Martin

1 0

openssh client configuration files
by Joerg Ruhe 10 Apr '02

10 Apr '02

Hello list, I'm new to ssh and I'm trying to set up an openssh server and some clients. I have a problem with the order in which openssh reads and applys the client configuration files (openssh 2.9.9p2 SuSE 7.3 ). The man page and the o'reily book state the order in which configuration data is obtained as : 1. command line options, 2. user's configuration file ($HOME/.ssh/config) 3. system-wide configuration file (/etc/ssh/ssh_config) and for each parameter the first obtained value will be used. For me that means, that if I set an parameter in my $HOME/.ssh/config and agin in /etc/ssh/ssh_config the value from the $HOME/.ssh/config will be used. My trouble is, I'm observing a differnt behaviour ( as you can see in the log below ): OpenSSH_2.9.9p2, SSH protocols 1.5/2.0, OpenSSL 0x0090602f debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Reading configuration data /home/ruhej/.ssh/config debug1: Applying options for * Here the options in the system-wide configuration file are applied first. I have seen this on several differnt computers, all with SuSE 7.3 and openssh 2.9.9p2 . Unfortuanly I'm not able to compare this behavior with an earlier version of openssh and suse. If I do an ssh -F config-file everything works, as in my understanding it should work, the given config-file is read an nothing else. I would be glad, if somebody could help me with this problem ( or tell me what I did wrong ). Thanks Joerg Ruhe Joerg.Ruhe(a)epost.de

1 0