openSUSE Security December 1999

security@lists.opensuse.org

81 participants
70 discussions

SSH Authentication
by Joao Reis 18 Nov '02

18 Nov '02

Hi! I implemented a ssh conection from the outside to my intranet. This ssh requires a username and a password. In terms of security what is more secure: require authentication (username and password) or having the public key of each user that connects to our intranet in the authorized public key lists (in this case there is no need for username and password)? In the second case there is no need of authentication and only the users wich have the public keys in the list are allowed to enter in my intranet. This second solution is a good solution or that brings other security problems ? Thanks. -- Farewell. "Keep your friends close, but your enemies closer." "Do or do not. There is no try" - Yoda João Reis -------------------------------------------------------

2 1

multi-services server securing
by Gediminas Grigas 16 Aug '00

16 Aug '00

Hello there, I feel erroneusly (?) secure after .host.denyed in.telnetd and in.sshd from everywhere except one pc, which is denying all exept keyboard. I belive that if i can keep hosts.deny and hosts.allow files safe, and from time to time patch most actual security holes i`ll be conditionaly safe. Em i wrong? Probably I do. I just cant imaginate how system can be cracked in lower stage, so that is my problem. I heard that inetd is very insecure, and some peoples using tcpd (or soundlike). I run harden_suse, but was forced to answer 8/10 to no, as my server should provide a lot of public services, and have world writible directories as well. And thats right - this script was developed not for systems like mine one. However i`ll run SuSE-firewall-3.0 script, to make my system even stronger. But thats all. I dont know what can i do else. I should keep folowing services open: httpd; smptd; pop3d; ftpd; snmpd; named; inetd; sshd; nscd. So if you know how to keep them at minimal risk, or know some holes at those, i would be very gratefull for any info and/or tips. I dont ask to do work for me - link to good manual would be nice too. By the way i have SuSE 6.3 (2.2.13). Thanks in advice. Sincerely Yours, Gediminas Grigas mailto:gedas@kryptis.lt

5 5

Firewall Performance
by Thomas Michael Wanka 31 Dec '99

31 Dec '99

Hi all, I need to know how much a firewall based an ipchains (no extra software) decreases system performance. I have a server running Linux with two subnets, 1 with all the workstations (currently all MS OS) are connected to, 2 the old 10base2 network with the printer and the PC running NetBSD connected to the Internet. This router has firewalling functionality installed, but if there is not too much performance loss, I thought it was a good Idea to have packet filtering and port blocking active on the server too. Any suggestions and recommendations? Thanks in advance mike

1 0

Firewall Performance
by Thomas Michael Wanka 31 Dec '99

31 Dec '99

1 0

Firewall Performance
by Thomas Michael Wanka 31 Dec '99

31 Dec '99

1 0

Firewall Performance
by Thomas Michael Wanka 31 Dec '99

31 Dec '99

1 0

suse-firewall
by Tummis＠t-online.de 30 Dec '99

30 Dec '99

Hi, I installed the suse_firewallscript two weeks ago and it works fine. But i get a dynamic IP from my Provider and so i cannot a static-IP in my rcfirewall. This is a part of my bootmassage snip starting Firewall Initialization: ppp0: error fetching interface information: Device not found ppp0: error fetching interface information: Device not found Warning: faulty interface information for ppp0. No interfaces active! exiting ... failed Master Resource Control: Failed services in runlevel 2: firewall_setup I don`t like this. What can i do? Thanks Klaus -- "Klaus Tumczak"<tummis(a)t-online.de> Linux User#155359 (http://counter.li.org/) Machine#68483 (http://counter.li.org/)

3 2

Apache: ".htaccess" files readable
by Bernd Jedamzik 29 Dec '99

29 Dec '99

Apache 1.3.6 (SuSE 6.2) Hello, the folloging lines in "httpd.conf" should "prevent .htaccess files from being viewed by Web clients" as the comment says: |<Files .htaccess> |Order allow,deny |Deny from all |</Files> But it IS viewable for people having PASSED the login-window in the Web client. (For failed login, it works ok.) I have a line "AllowOverride All" in the "http.conf"; the ".htaccess" file contains the following: |deny from all |AuthType Basic |AuthUserFile /usr/local/httpd/htpasswd.users |AuthName "Intranet" |require valid-user |satisfy any Is it a bug in design? How can I prevent the ".htaccess" file from being viewable to people passed the login? Thanks Bernd

1 0

Re: [suse-security] suse-firewall
by Dan Am 28 Dec '99

28 Dec '99

Look earlier. The interface has not come up and is thus not found. At least ethX-interfaces come up aalready in runstate 1. Maybe that helps. dan -----Ursprüngliche Nachricht----- Von: Klaus Tumczak <Tummis(a)t-online.de> An: suse-security(a)suse.com <suse-security(a)suse.com> Datum: Dienstag, 28. Dezember 1999 03:32 Betreff: [suse-security] suse-firewall >Hi, >I installed the suse_firewallscript two weeks ago and it works fine. >But i get a dynamic IP from my Provider and so i cannot a static-IP in >my rcfirewall. >This is a part of my bootmassage > >snip >starting Firewall Initialization: ppp0: error fetching interface information: Device not found >ppp0: error fetching interface information: Device not found >Warning: faulty interface information for ppp0. > >No interfaces active! exiting ... > failed >Master Resource Control: >Failed services in runlevel 2: firewall_setup > >I don`t like this. What can i do? >Thanks >Klaus > >-- >"Klaus Tumczak"<tummis(a)t-online.de> >Linux User#155359 (http://counter.li.org/) >Machine#68483 (http://counter.li.org/) > >-- >To unsubscribe, e-mail: suse-security-unsubscribe(a)suse.com >For additional commands, e-mail: suse-security-help(a)suse.com >

1 0

logging problem with wvdial.dod
by Robert C. Paulsen, Jr. 27 Dec '99

27 Dec '99

Hello, I now have the new fierwals package set up and working in combination with the wvdial.dod script from SuSE's web site. Please see another of my messages to this list that points to the changes I needed to make to wvdial.dod to get it working. I am still having one problem with the firewals script. I get *many* mesages like the following in /var/log/messages. There must be some mismatch between my Samba configuration and my rc.firewall configuration. I would appreciate it if someone would take a look at my smb.conf and rc.firewall which I have placed on my web site: http://paulsen.home.texas.net/smb.conf http://paulsen.home.texas.net/rc.firewall Here is a sample of the log messages: Dec 27 07:44:27 home kernel: Packet log: input DENY eth0 PROTO=17 192.168.0.1:137 192.168.0.255:137 L=78 S=0x00 I=46162 F=0x0000 T=64 (#5) Dec 27 07:44:29 home kernel: Packet log: input DENY eth0 PROTO=17 192.168.0.1:137 192.168.0.255:137 L=78 S=0x00 I=46163 F=0x0000 T=64 (#5) Dec 27 07:44:30 home kernel: Packet log: input DENY eth0 PROTO=17 192.168.0.1:137 192.168.0.255:137 L=78 S=0x00 I=46164 F=0x0000 T=64 (#5) Dec 27 07:44:31 home kernel: Packet log: input DENY eth0 PROTO=17 192.168.0.1:137 192.168.0.255:137 L=78 S=0x00 I=46165 F=0x0000 T=64 (#5) Dec 27 07:44:43 home kernel: Packet log: input DENY eth0 PROTO=17 192.168.0.1:138 192.168.0.255:138 L=215 S=0x00 I=46168 F=0x0000 T=64 (#5) Dec 27 07:44:45 home kernel: Packet log: input DENY eth0 PROTO=17 192.168.0.1:138 192.168.0.255:138 L=215 S=0x00 I=46169 F=0x0000 T=64 (#5) Dec 27 07:44:47 home kernel: Packet log: input DENY eth0 PROTO=17 192.168.0.1:138 192.168.0.255:138 L=215 S=0x00 I=46170 F=0x0000 T=64 (#5) Dec 27 07:44:49 home kernel: Packet log: input DENY eth0 PROTO=17 192.168.0.1:138 192.168.0.255:138 L=215 S=0x00 I=46173 F=0x0000 T=64 (#5) Dec 27 07:44:51 home kernel: Packet log: input DENY eth0 PROTO=17 192.168.0.1:138 192.168.0.255:138 L=215 S=0x00 I=46174 F=0x0000 T=64 (#5) Dec 27 07:44:51 home kernel: Packet log: input DENY eth0 PROTO=17 192.168.0.1:137 192.168.0.255:137 L=96 S=0x00 I=46175 F=0x0000 T=64 (#5) Dec 27 07:44:53 home kernel: Packet log: input DENY eth0 PROTO=17 192.168.0.1:137 192.168.0.255:137 L=96 S=0x00 I=46176 F=0x0000 T=64 (#5) Dec 27 07:44:54 home kernel: Packet log: input DENY eth0 PROTO=17 192.168.0.1:137 192.168.0.255:137 L=96 S=0x00 I=46177 F=0x0000 T=64 (#5) Dec 27 07:44:55 home kernel: Packet log: input DENY eth0 PROTO=17 192.168.0.1:137 192.168.0.255:137 L=96 S=0x00 I=46178 F=0x0000 T=64 (#5) Dec 27 07:44:56 home kernel: Packet log: input DENY eth0 PROTO=17 192.168.0.1:137 192.168.0.255:137 L=96 S=0x00 I=46179 F=0x0000 T=64 (#5) Dec 27 07:44:58 home kernel: Packet log: input DENY eth0 PROTO=17 192.168.0.1:137 192.168.0.255:137 L=96 S=0x00 I=46180 F=0x0000 T=64 (#5) -- ____________________________________________________________________ Robert Paulsen http://paulsen.home.texas.net

2 1

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

1996

openSUSE Security December 1999